5 posts tagged with "Development"

There's still a lot of guff floating about out there about whether the AI bubble is going to burst[^1] , whether AI coding is "good enough yet" (see my previous comments on my previous comments on vibe coding), and whether AI is the silver bullet solution to your problem.

I saw a great post by a former R/GA colleague on LinkedIn today which said that "if you think a specific new technology is the solution to your problem then you probably don't understand the problem enough", and I am minded to agree.

Given some of my previous comments about vibe coding, I found myself taking a different track and questioning some assumptions (and biases) over the last week and wanted to capture a bit more nuance around the topic.

Once upon a time I was paid to write code in exchange for coins, and I wasn't bad at it.

Then I got paid to lead and manage people who write code in exchange for coins, and it turned out that I wasn't bad at that either.

These days I am paid to lead and manage people who lead and manage people who write code in exchange for coins, so I guess that:

1. I'm pretty good at tech and people,
2. My job is becoming more and more fractal, and
3. I only really write code for myself these days

Given that I'm attempting to start writing stuff / blogging again, I thought I would share a couple of the daft personal projects that I have put together in recent years.

I have been thinking a lot about AI recently — probably because every other post on LinkedIn is some kind of regurgitated AI think-piece, and every unsolicited email at work seems to revolve around AI strategy — and what it means for our current working practices.

Today I (probably) invented a new technology term: Homepathic estimation