The conversation

Lessons learnedExperience excerpt · English

There is so much framework stuff, when I started coding I could mostly concentrate on the …

… There is so much framework stuff, when I started coding I could mostly concentrate on the algorithm, now I have to do so much framework stuff, I feel like telling the LLM really only the actual algorithm, minus all the overhead, is much more "programming" than today's programming with the many many layers of "stuff" layered around what I actually want to do. I find it a bit ironic though that our tool out of the excessive complexity is an even more complex tool, although, looking at biology and that programming in large longer-running projects already felt like it had plenty of elements that reminded me of how evolution works in biology, already leading to hard or even impossible to comprehend systems (like https://news.ycombinator.com/item?id=18442637 ), the new direction is not that big of a surprise. …

Original discussionWithout data centers, GDP growth was 0.1% in the first half of 2025228 source comments · at import
2

What was this responding to?

Parent context · original excerpt

AM

Not the parent commenter, but why would you assume that he meant LLMs specifically? I'm one of the "tech people not interested in AI" and I mean everything around AI/ML. I just like writing OG code man. I like architecture, algorithms, writing "feeling good" code. Like carpenters who just like to work with wood I like to work with code.

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

WH

I predict the useful activity of writing LLM boilerplate will have a far shorter shelf-life than the activity of writing code has has.

Full original
BE

> There is so much framework stuff, when I started coding I could mostly concentrate on the algorithm, now I have to do so much framework stuff, I feel like telling the LLM really only the actual algorithm, minus all the overhead, is much more "programming" than today's programming with the many many layers of "stuff" layered around what I actually want to do. I was wondering about this a lot. While it's a truism the generalities are always useful whereas the specific gets deprecated with time, I was trying to get down deeper on why certain specifics age quickly whereas other seem to last. I came up with the following: * A good design that allows extending or building on top of it (UNIX, Kubernetes, HTML) * Not being owned by a single company, no matter how big (negative examples: Silverlight, Flash, Delphi) * Doing one thing, and being excellent at it (HAproxy) * Just being good at what…

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.