Adam Fordyce

Article · 3 min read

Ready, Fire, Aim...

In platform engineering, I’ve learned that firing before I’ve aimed leads to wasted time and effort. One of my bad habits is jumping into solutions in my head as soon as a problem appears. I have to stop myself from overcommitting or getting sidetracked when facing complex technical challenges.

Skills used

The challenges I typically work on are related to addressing known system defects. A recent example involved a core Kubernetes CNI component. Other examples include exploring mechanisms to gain deeper insights into DNS traffic on enterprise systems. Some problems are less glamorous and may relate to automating tedious tasks when integrating with third-party systems, such as transforming data between incompatible formats or wrapping a set of common steps together.

I’ve always been a tinkerer. I don’t think I’m the master of any single concept, but I can usually grasp enough to contribute meaningfully. This habit serves me well, but it also feeds my impulse to code before I’ve fully understood the problem.

Over time, I’ve tried to develop a strategy to manage that urge - to slow down and ‘aim’ before I ‘fire’:

  1. Write code with purpose - I still tinker, but I focus on writing pseudocode with plenty of TODOs instead of rushing into full implementations. If my idea has lasting value, I can revisit it later and flesh it out properly.
  2. Collaborate early - Sketching ideas and sharing them with colleagues sparks new insights and helps me avoid blind spots.
  3. Assess the complexity - there’s almost always a simpler way to solve a problem. It might not be the most exciting approach or involve the latest tech. Still, simpler solutions are easier for others to understand and usually glide through release checkpoints with less friction.

This approach prevents hours of wasted effort and keeps my solutions maintainable.

Last month, this approach helped me produce a new Kubernetes add-on, written in Golang, tested in a development cluster, and deployed using Helm to several large Kubernetes clusters. I shared the solution with colleagues, refined the implementation and got team support. The outcome resolved an ongoing problem that was preventing hosted applications from functioning correctly.

I don’t always follow this perfectly. I still spend too much time coding and not enough time collaborating or simplifying. But even if I stick to my own ‘Ready, Aim, Fire’ approach part of the time, I notice the difference. It helps me add real value without burning cycles on dead-end solutions.