Slow is smooth, smooth is fast

Reduce unplanned tech work to improve tech quality, speed, reliability...

Whether you’re working solo or leading a team, the result is the same: you’ll build a system that meets today’s needs and still evolves gracefully for tomorrow.

Download your guide here now: www.subscribepage.com/evolve-your-...

- Recognise uncertainty and build your system so you can refactor without fear.
- Make architecture a continuous activity, not a one-time milestone.

Continue on your journey to great architecture by downloading our 'how-to' guide.

In this guide, you’ll learn how to:
- Start simple and iterate to avoid the “big upfront design” trap.
- Keep modules clean, abstract, and testable so you can adapt when reality changes.

...

If you want to build software that can keep up with your users and your ideas, check out my FREE 'how-to' guide here ➡️ www.subscribepage.com/evolve-your-...

If you are adopting AI just because it's trendy, pause and ask yourself: "What specific problem are we trying to solve?". Use AI to increase your understanding and become a better engineer. Do not let it replace the intellectual work required to build high-quality software.

6/6

How should we use AI? The true win is augmentation. We should use AI as a creative partner:

1. Generate Ideas
2. Explore Options
3. Improve Design

5/6

The passing tests give us a nice dopamine hit, but we've missed the opportunity to clarify our understanding of the system and its design.

4/6

The danger I see is the widespread temptation to outsource this fundamental responsibility to an LLM. If we simply ask the AI to generate tests for our existing code, we risk testing the bugs in and falling into the trap of "sleepwalking through greens".

3/6

So, is testing still a developer's job? The answer is unequivocally yes. Data from high-performing orgs confirms that devs are responsible for test automation. Because testing is the CRUCIAL mechanism for providing early, frequent feedback.

2/6