Skip to content
fx-blog
agentic-fx field notes

Build software with AI agents on five pillars.

Intelligence, memory, judgment, verification and value: the bar we hold every AI-built tool to, with the code and the numbers to prove it.

73 posts9 categories5 pillars
afx install --bundle dev✓ gate G1 passed, evidence kept
  • IntelligenceThink before you build
  • MemoryNever repeat a mistake
  • JudgmentAsk, don’t invent
  • VerificationProve it with checks
  • ValueWorth the cost

Manage the Team: Goals, Trust and Delivery

Eleven goals nobody remembers, and a red result found in week 12, cost a lead the team's focus and the boss's trust. Set a few measurable results with one owner each, send a five-line update weekly, and report red early with a plan.

4 min readIntermediate

One-to-Ones That Matter, and Handling Conflict

Skip one-to-ones and you hear about trouble when someone stops coming to standup. Hold them weekly with their agenda first; when two people clash, talk to each privately, then together, and end on a shared rule, not a winner.

4 min readIntermediate

Hire and Grow Your Crew

Hiring on gut feel picks whoever talks best. Decide what the job needs before you meet anyone, ask every candidate the same questions, score each answer alone before the debrief, then start your hire on a 30-60-90 plan with a buddy.

4 min readIntermediate

From Best Engineer to First-Time Lead

A new lead who keeps the hardest ticket becomes the bottleneck and codes at night to catch up. Your output is now what the team ships: unblock first, review within a day, and hand the work you love to someone who can own it.

4 min readIntermediate

Say No Without Making Enemies, and Keep Your Energy

Saying yes to everyone costs your evenings, then promises you quietly break. Trade instead of refusing: say what would move and let the priority owner choose. Guard a long focus block, and take exhaustion and cynicism seriously.

5 min readIntermediate

Feedback Both Ways: Asking For It and Giving It

"Any feedback?" gets "looks fine" while others decide your work is hard to follow. Ask for one specific thing to change, take it without defending, and give feedback as situation, behaviour and impact, soon and in private.

4 min readIntermediate

Working With a Difficult Boss Without Losing Yourself

Arguing a cut estimate loses twice: the argument, then the date. Name the kind of difficult boss you have, find the pressure behind the demand, answer with options that trade scope for time, and recap in writing. Abuse is different: report it.

4 min readIntermediate

Pass Probation on Purpose

Waiting for the probation verdict means learning at week 12 what was expected at week 2. Ask what passing means and write it down, keep a brag doc every Friday, and ask what worries your lead at the midpoint.

4 min readBeginner

Senior QA: Depth Everywhere Is Depth Nowhere

A senior QA engineer who tests everything equally leaves the risky areas thin. Score each area by impact times likelihood, test the top deepest, tell the PM in writing what gets only a smoke pass, and make every production escape leave a regression test behind.

4 min readIntermediate
Load more posts20 posts per page, newest first
Newsletter

Get the next post by email

One email per new post, reviewed by hand before it is sent. Pick the whole site or only the categories you follow. Unsubscribe in one click.

+ 6 more