Live data from Hacker News

We mourn our craft

nolanlawson.com

731–740 of 918 posts

Re: We mourn our craft

#732

"They can write code better than you or I can" They can not. They can make some average code. On Friday one suggested an NSI installer script that would never bundle some needed files in the actual installer. I can only imagine that a lot of people have made the same mistake (used CopyFiles instead of File ) and posted that mistake on the internet. The true disaster of that being that then testing out that installer…

[deleted]

Re: We mourn our craft

#733

"They can write code better than you or I can" They can not. They can make some average code. On Friday one suggested an NSI installer script that would never bundle some needed files in the actual installer. I can only imagine that a lot of people have made the same mistake (used CopyFiles instead of File ) and posted that mistake on the internet. The true disaster of that being that then testing out that installer…

So it can write better code than your below average software engineer.

It still cuts out 40-50% of workforce out.

For above average engineers its very good.

For bottom half not so much.

Translate for Mgrs - it replaces offshore completely.

Re: We mourn our craft

#734

Earlier quoted context omitted.

> as a senior engineer, most of the stuff you do shouldn’t be stuff that an LLM is good at to begin with Your use of the word "should" is pointing to some ideal that doesn't exist anymore. In current actual reality, you do whatever your employer gives you to do, regardless of your job title. If you have 40 years of broad development experience but your boss tells you to build more CRUD web apps or start looking for a…

I think the point is that if you're building yet-another-CRUD web app, why aren't you abstracting more of it away already? It's not like we don't have the facilities for this in programming languages already.

The main issue with current LLM hypers is the complete unrealistic scenarios they come up with. When building a CRUD app, the most obvious solution is to use a framework to take care of the common use cases. And such framework will have loads of helpers and tools to speed up boilerplate.

Re: We mourn our craft

#736

I was very impressed by AI-generated CSS when I didn't know CSS. Then I learned CSS. Now I am not as impressed by AI-generated CSS.

This seems to be a general rule for AI-generated anything. It's impressive in domains you're not an expert in. Much less so on domains you are an expert in.

Re: We mourn our craft

#737
post #590

Earlier quoted context omitted.

It's funnily enough quite the opposite front ends that have a focus on UX are pretty well protected from generative AI

I haven't heard this perspective. I'm kind of surprised the LLMs can't generate coherent frontend framework-ized code, if that's the implication.

Both of you are right. They can generate the code quite well, but well-considered UX is another thing entirely.

Re: We mourn our craft

#739

Earlier quoted context omitted.

I’ve got 8 year old Go code that still compiles fine on the latest Go compiler. Go has its warts but backwards compatibility isn’t one of them. The language is almost as durable as Perl.

It depends on your threat model. Mine includes the compiler vendors abandoning the project and me needing to make my own implementation. Obviously unlikely, and someone else would likely step in for all the major languages, but I'm not convinced Go adds enough over C to give away that control. As long as I have a stack of esp32s and a working C compiler, no one can take away my ability to make useful programs, includ…

For embedded that probably works. For large C programs you're going to be just as stuck as you are with Go.

Re: We mourn our craft

#740
post #566

Earlier quoted context omitted.

A desktop/laptop is fundamentally different from a phone.

except of course they are controlled by huge corporations and cost a significant amount of money to use

Yes, but they are fundamentally different use cases.
Post reply on HN