Hacker News Reader

Comment by Olscore | Hacker News Reader

Yes > real issues are in this layer of intent

This is why code is going to be automated, and the software engineer is a link between organizational intent and the code. This is what I’m working on.

View on HN

How does this differ from what I'm doing today? Want to say any more on the topic? This is a bit vague.

The difference is that instead of spending half your time understanding the business requirements and half your time writing code, you'll spend half your time understanding the business requirements, 5% of your time typing these requirements into a chatbot, and the rest of your time doing... ????

Some of the rest of the time can be spent making it look like your ratios are the same but in reality you just take the saved time and do whatever you want with it. The decision making and reviews aren’t happening any faster anyway so just take it easy and coast a bit

I guarantee there will not actually be saved time - the bullshit will increase to more than compensate, as everyone actually fixing things will be drowned out by bullshitters just pretending to fix things and creating more actual problems.

Design, writing specs: Same amount of time.

Finding the holes in your specs under automation: time spent is returned 10x

Writing code: Human 15 lines per minute. LLM: 600+ lines per minute

Functional Validation: same time per iteration. Fewer bugs with LLM when properly specified => fewer iterations. Increased awareness of LLM escaping specification boundaries feeds back into increasing quality of spec writing => fewer bugs.

Reply on news.ycombinator.com