This stuff is so new and wild west at the moment that in our company everyone is using it completely differently. 20% of the devs have 30x output and are doing everything with Claude, 10% won't touch it, the rest are in some weird in between where they use it for some things and not other things which it is perfect for. We have managers that suggest just going back to doing it by hand when there are outages, which is the most laughable thing in the world to me now. It is incredible to watch this miracle tech hit so fast and have everyone's understanding of it be so different across the board.

▲

clivedup a day ago | parent | next [-]

Yeah, it's an exciting time.

And jarring. When interacting with colleagues in teams that I haven't worked with, there's an uncomfortable "where are they on AI...", which will decide whether I have to dial down my usage, or whether we can both let it rip.

In mere months.

▲

white_dragon88 a day ago | parent | prev | next [-]

[dead]

▲

mrbombastic a day ago | parent | prev | next [-]

it is very funny to me that on a story about a major outage at one of the companies pushing the "software is solved" narrative the suggestion to slow down and do things more carefully is laughable, I think we officially need to retire calling ourselves engineers.

▲

mr_roboto a day ago | parent | next [-]

Did they stop being mathematicians when calculators were invented? Architects when cad software came along? They produced way more while having to do a lot less. AI is a tool that empowers me to do the same job at an easy 30x speedup and this is just getting started. I've produced more in the last year than I have in the last 20. I'm more of an engineer with these tools than I ever have been.

▲

mrbombastic a day ago | parent | next [-]

did mathematicians get pressured to stop reviewing their work? skip verification because it was slowing down shipping? do things outside their job description (cough design, product management) and stop collaborating with their colleagues because "velocity" demanded it? If you are doing the same job as yesterday with the same safeguards 30x faster good for you, keep calling yourself an engineer. If you are like me and a lot of others out there pushing slop out the door with more and more incidents weekly and forgetting what good software dev looks like, stop pretending.

	▲	mr_roboto a day ago \| parent [-]
		It probably depends on the job. There is huge variance across the industry as far as what people are working on. I don't work with top talent and I'm very happy with the results compared to human coworkers. I've found the secret is detailed architecture plans in advance. These models are in their infancy and if you aren't happy with the output yet I'd wager they catch up to your needs faster than expected.

▲

zahlman a day ago | parent | prev [-]

> Did they stop being mathematicians when calculators were invented?

After learning to use a calculator, did it promptly become laughable to do arithmetic by hand (or even in your head) if yours broke or otherwise became unavailable?

	▲	mr_roboto a day ago \| parent [-]
		On any scale that matters, absolutely. You think a physicist or accountant is going to start hand crunching their 800 equation spreadsheet when their laptop dies, laughably absurd. You think I am going to spend several hours writing a couple hundred lines of code when I'm now normally doing several thousand per day, laughably absurd.

▲

gramstrong 20 hours ago | parent | prev [-]

Software developers shouldn't have ever called themselves engineers to being with.

▲

cyclopeanutopia a day ago | parent | prev [-]

[dead]