Earlier quoted context omitted.
Do you know how every nail was put into your house? Does the general contractor?
I know where they fucked up and cost me thousands of dollars due to cutting corners during build-out and poor architectural decisions during planning. These kinds of things become very obvious during destructive inspection, which is probably why there are so many limitations on warranties; I digress. He’s mildly controversial, but watch some @cyfyhomeinspections on YouTube to get a good idea of what you can infer of…
How I write software with LLMs
341–350 of 544 posts
Re: How I write software with LLMs
#342Re: How I write software with LLMs
#343That exact thing happens with people too! Specifically when a cheap entrepreneur hires a novice developer and can't give the developer appropriate mentoring and reviews.
Re: How I write software with LLMs
#344Earlier quoted context omitted.
Explain how fragility of implementation, like spaghetti code, high coupling low cohesion fit into your world view?
As human developers, I think we're struggling with "letting go" of the code. The code we write (or agents write) is really just an intermediate representation (IR) of the solution. For instance, GCC will inline functions, unroll loops, and myriad other optimizations that we don't care about (and actually want!). But when we review the ASM that GCC generates we are not concerned with the "spaghetti" and the "high coup…
Why? Because LLMs can get easily confused, so they need well written code they can understand if the LLM is going to maintain the codebase it writes.
The cleaner I keep my codebase, and the better (not necessarily more) abstracted it is, the easier it is for the LLM to understand the code within its limited context window. Good abstractions help the right level of understanding fit within the context window, etc.
I would argue that use of LLMs change what good code is, since "good" now means you have to meaningfully fit good ideas in chunks of 125k tokens.
Re: How I write software with LLMs
#345Earlier quoted context omitted.
Valid points. But crucial part of not "letting go" of the code is because we are responsible for that code at the moment. If, in the future, LLM providers will take ownership of our on-calls for the code they have produced, I would write "AUTO-REVIEW-ACCEPTER" bot to accept everything and deploy it to production. If, company requires me to own something, then I should be aware about what's that thing and understand i…
In the past ten years as a team lead/architect/person who was responsible for outsourced implementations (ie Salesforce/Workday integrations, etc), I’ve been responsible for a lot of code I didn’t write. What sense would it have made for me to review the code of the web front end of the web developer for best practices when I haven’t written a web app since 2002?
on the other hand, you may have been an engineering manager, who is responsible for the team, but a lot of times they do not participate in on-call rotations (only as last escalation)
Re: How I write software with LLMs
#346Earlier quoted context omitted.
Sounds like influencer nonsense to me. Touch grass. If the people are fed and housed, there's no collapse. And if the billionaire class lets them starve, they will finally go through some things just like the aristocracy in France once did. And I think even Peter Thiel is smarter than that. You can feed yourself for OTOH if what you're really talking about is the long-term collapse in our ludicrous carbon footprint w…
>You can feed yourself for You are the epitome of the tech bro.
Re: How I write software with LLMs
#347Re: How I write software with LLMs
#348Earlier quoted context omitted.
As human developers, I think we're struggling with "letting go" of the code. The code we write (or agents write) is really just an intermediate representation (IR) of the solution. For instance, GCC will inline functions, unroll loops, and myriad other optimizations that we don't care about (and actually want!). But when we review the ASM that GCC generates we are not concerned with the "spaghetti" and the "high coup…
I've actually found that well-written well-documented non-spaghetti code is even more important now that we have LLMs. Why? Because LLMs can get easily confused, so they need well written code they can understand if the LLM is going to maintain the codebase it writes. The cleaner I keep my codebase, and the better (not necessarily more) abstracted it is, the easier it is for the LLM to understand the code within its…
Re: How I write software with LLMs
#349Earlier quoted context omitted.
>If you can build things, AI coding agents will let you build faster and more for the same amount of effort. But you aren't building, your LLM is. Also, you are only thinking about ways as you, a supposed builder, will benefit from this technology. Have you considered how all previous waves of new technologies have introduced downstream effects that have muddied our societies? LLMs are not unique in this regard, and…
Would you say the general contractor for your home isn’t a builder because he didn’t install the toilets?
Re: How I write software with LLMs
#350> On the flip side, when I’m not familiar enough with the technology to be on top of the architecture, I tend to not catch bad decisions that the LLM makes. This leads to the LLM building more and more on top of those bad decisions, eventually getting in a state where it can’t untangle the mess. You know this happens when you keep telling the LLM the code doesn’t work, it says “I know why! Let me fix it” and keeps br…