dave_sid

What do you mean some reason? He wrote the book Refactoring that caused everyone to start refactoring. That’s quite a big reason. He literally wrote the book on it.

How do you feel about MC Hammer?

Didn’t he invent refactoring? Something that every developer in the world uses every day? Don’t think he’s a bullshitter.

Probably. And probably hard for them to believe too.

Google ads are a con. Meta ads are a con. If someone tells you you’re just not doing it right yet, they’re probably trying to sell you something.

Shopify should deal with their hijacked accounts first. A high percentage of sponsored Google search sponsored results lead to scams on hijacked sites.

I wish developers could just walk out the door en masse tomorrow and let orgs replace them all with AI as has been touted for so long, then see what happens. It gets boring trying to explain that developers don’t just write code. “What do they do then?” I can almost hear a manager saying in a smug tone. If you have to ask, you’ll never knowww… ♬ ♬ ♬ ♬

Same here. Got the same machine and feel the same as you about it.

Exactly. I think this is it. Clearly separate what must be perfect and well understood (security, business logic), from bits that you are happy to throw some code at and see if they work. And don’t let the latter get its hands on the former. I think going back to OOP principles and SRP/separation of concerns can make this work. Just some conscious planning needed rather than handing over the reins entirely.

I think c is the only way it can sustainably work. The idea of b, that software is running and nobody there knows how it works, doesn’t seem like a good foundation for a business to run on.

I have found what works well is to modularise the code as much as possible and get an agent to work within a very limited scope. Break everything down well using SRP with well defined interfaces and let the agent work on small problems. Then when it shits the bed, there’s a smaller blast radius and you can strip back and try again.

I think seasoned developers, over time, learn how to work a code base and design components with well defined interfaces, where the implementation is isolated in small well contained classes. SRP etc. more junior programmers can work on those smaller components/services in isolation.

For me this also seems to be a productive way to work along side an agent. Break up functionally into well defined chunks, and let the agent work on each small problem. Take more of a lead in the architecture I suppose.

Donald?

It will soon be easy is all content will be AI-generated content. Or it will just implode at that point.

Coding is just a small part of a modern software engineers job. And some may think it isn’t the hardest part.

“The best code is the code you didn’t have to write” - a wise coder