Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI handles incidents, engineers lose touch with their systems

sylvainkalache.com

Post reply on HN
Print view View original

21–30 of 375 posts

Re: AI handles incidents, engineers lose touch with their systems

#21

Post by shakna »

throw839948499 wrote: post #17
bob1029 wrote: post #6

A natural evolution of engineers losing touch with the customers and users. I'm noticing some of the concern play out regarding AI weakening the capabilities of software people. I gave the team an exact solution on a silver platter and they still failed to identify how to go about it after 3 days slamming it into Claude. The resolution is literally 1 line of code that could be arrived at in about 30 minutes of patien…

If the solution is so simple, why claude did not found it? At this point we can assume, it is better than 90% of engineers (including me). After three decades of outsourcing to lowest bidder, I do not buy that humans are somehow better! > patient, old school troubleshooting I usually see similar arguments around systems with major red flags (no docs, poor CI, decade ago no CVS...). And engineers with private stash of…

Claude regular spits out six helper functions instead of... A twenty line for loop. It overengineers most things.

Overabstracting, deduplicating things that don't need to be. Building metaclasses because it saw a single orchestrator in the whole codebase.

If it is a better engineer than you... You need practice.

Re: AI handles incidents, engineers lose touch with their systems

#22

Post by bob1029 »

throw839948499 wrote: post #17
bob1029 wrote: post #6

A natural evolution of engineers losing touch with the customers and users. I'm noticing some of the concern play out regarding AI weakening the capabilities of software people. I gave the team an exact solution on a silver platter and they still failed to identify how to go about it after 3 days slamming it into Claude. The resolution is literally 1 line of code that could be arrived at in about 30 minutes of patien…

If the solution is so simple, why claude did not found it? At this point we can assume, it is better than 90% of engineers (including me). After three decades of outsourcing to lowest bidder, I do not buy that humans are somehow better! > patient, old school troubleshooting I usually see similar arguments around systems with major red flags (no docs, poor CI, decade ago no CVS...). And engineers with private stash of…

That final 10% is the hard part. 90% is easy.

Re: AI handles incidents, engineers lose touch with their systems

#23

Post by Sharlin »

throw839948499 wrote: post #17
bob1029 wrote: post #6

A natural evolution of engineers losing touch with the customers and users. I'm noticing some of the concern play out regarding AI weakening the capabilities of software people. I gave the team an exact solution on a silver platter and they still failed to identify how to go about it after 3 days slamming it into Claude. The resolution is literally 1 line of code that could be arrived at in about 30 minutes of patien…

If the solution is so simple, why claude did not found it? At this point we can assume, it is better than 90% of engineers (including me). After three decades of outsourcing to lowest bidder, I do not buy that humans are somehow better! > patient, old school troubleshooting I usually see similar arguments around systems with major red flags (no docs, poor CI, decade ago no CVS...). And engineers with private stash of…

So after 30 years of outsourcing to the bottom 10%, you think Claude is better than the bottom 90% even though it’s so stupid that it doesn’t even know it should ask for advice or more information when it’s stuck?

Re: AI handles incidents, engineers lose touch with their systems

#25

Post by mawadev »

Root_Denied wrote: post #8
bob1029 wrote: post #6

A natural evolution of engineers losing touch with the customers and users. I'm noticing some of the concern play out regarding AI weakening the capabilities of software people. I gave the team an exact solution on a silver platter and they still failed to identify how to go about it after 3 days slamming it into Claude. The resolution is literally 1 line of code that could be arrived at in about 30 minutes of patien…

I'm seeing this happen in the security space right now. Someone on my team I was helping train and bring along is all of sudden regressing in their understanding of the issues we're working on, and instead focusing on AI tool outputs to do their job for them.

I can share a weird story:

Usually, I take my time to understand each keyword of the code I'm looking at, especially if it is new to me, like terraform.

I work in a team/with one architect, who only did the DevOps/Infra stuff for the past years and I had the expectation he knows what he is doing and talking about.

At around 2 weeks, I noticed how his knowledge has severe gaps and how he takes things at face value or uses terminology interchangably, which confuses me. It sounds plausible, but it does not actually translate into a working system or shared understanding.

Then one day I did some pair programming with him and whenever there was an error or a resource missing, he would type it into the LLM, copy paste it out of it and then brute force error messages. He did not even wait a second to think or reconcile whats happening on the screen or what the exact requirement is. Never taking one step back and questioning any assumption.

Now that the timeline is shifting and everyone starts to be stressed, he continues to vibe code through me and it is so tiring, there is no higher level planning or architecture, its just a reactive type of trial and error to be faster. It feels like these people are so used to talking to bots, that they treat you like an agent they can chat to or talk through monologs with.

It is quite shocking how people went from being humble (learn the basics or close the gaps in understanding) to full on authority on everything and berating people 24/7...

So right now I'm considering quitting IT for a couple of years until people calm down, but I think its pretty futile

Re: AI handles incidents, engineers lose touch with their systems

#26

Post by coffeebeqn »

Root_Denied wrote: post #8
bob1029 wrote: post #6

A natural evolution of engineers losing touch with the customers and users. I'm noticing some of the concern play out regarding AI weakening the capabilities of software people. I gave the team an exact solution on a silver platter and they still failed to identify how to go about it after 3 days slamming it into Claude. The resolution is literally 1 line of code that could be arrived at in about 30 minutes of patien…

I'm seeing this happen in the security space right now. Someone on my team I was helping train and bring along is all of sudden regressing in their understanding of the issues we're working on, and instead focusing on AI tool outputs to do their job for them.

At least at my company the OKRs are quite clear and demand heavy AI utilization above all else

Re: AI handles incidents, engineers lose touch with their systems

#27

Post by yard2010 »

jtfrench wrote: post #5

The more code writes autonomously, the less intuition the human owners have about that code. Loss of intuition is a seed of technical debt that grows with time. Over a long enough horizon, it can make looking at your own codebase feel like the first day on the job (sometimes at a company you started). Luckily, there are ways to mitigate this and essentially translate those human intuition of how the codebase “should”…

I've been thinking about this lately - is it like using 3rd party libs to achieve stuff faster? As much as I would lovr to hand craft the datetime logic in my app, I might as well use luxon and invest this time somewhere else. Only now with llms, you get virtually infinite 3rd party libs you can use, you create them on the fly. So if you have strong engineering values, I would say simply it boils down to "contracts over programs", you can still be in touch with the logic that glues it all together and treat some logic as a blackbox the same way we do with 3rd party libs?

Re: AI handles incidents, engineers lose touch with their systems

#28

Post by gspr »

throw839948499 wrote: post #17
bob1029 wrote: post #6

A natural evolution of engineers losing touch with the customers and users. I'm noticing some of the concern play out regarding AI weakening the capabilities of software people. I gave the team an exact solution on a silver platter and they still failed to identify how to go about it after 3 days slamming it into Claude. The resolution is literally 1 line of code that could be arrived at in about 30 minutes of patien…

If the solution is so simple, why claude did not found it? At this point we can assume, it is better than 90% of engineers (including me). After three decades of outsourcing to lowest bidder, I do not buy that humans are somehow better! > patient, old school troubleshooting I usually see similar arguments around systems with major red flags (no docs, poor CI, decade ago no CVS...). And engineers with private stash of…

> At this point we can assume, it is better than 90% of engineers (including me).

Hard disagree. We absolutely cannot assume that. You can posit it, and we can have an informed debate about it. This is what irks me the most about LLM fans: they constantly try to reframe the debate to have their worldview as the agreed-upon starting point.

Re: AI handles incidents, engineers lose touch with their systems

#29

Post by hypfer »

Meta: The blinking cursor of the "logo" of the blog being sticky in the top left corner makes it impossible for me to read the text. It constantly fires interrupts at me.

Depending on what your goals as the author are, you may or may not want that.

Being able to scroll it out of view might be enough to achieve the aesthetics goal, and the goal of people actually listening to you.

Post reply on HN