2 Comments
User's avatar
James Jones's avatar

I can’t tell you how much this warms my heart to read.

I’ve long thought (in AI years) that AI-enabled development is as much about setting up the guardrails around its delivery as it is about having deep understanding or confidence in the code it creates.

And you’re spot on; having operated someone else’s software for most of my career, I’m very comfortable not knowing line by line what I’m fighting, working, caressing, loving, hating, or supporting.

And finally, perhaps more controversially, given the Ops and Sec teams’ comfort and experience with the “black box,” I think leaders with that background are better placed to lead into the future. Those with purely development backgrounds who can’t get over that hump of comprehension are going to find it challenging to lead engineering teams effectively going forward.

Expand full comment
Daniel Walters's avatar

Glad it resonates. I've gone pretty deep into AI-coding over the last 18 months but it occurred to me that it was an Ops/DevOps/DevSecOps person who had inspired me.

Also my career has spanned engineering, product and ops and I've found it exercises skills across all three areas.

Deep software engineering and architecture knowledge will be important but in this early period it might be the ops talent that go farther sooner.

Expand full comment