HN user

ppqqrr

179 karma
Posts7
Comments99
View on HN

it usually takes a little longer than this, but yeah, everything in the world eventually caves in for whatever makes more money. you can't tell me you're surprised, look at the state of facebook, instagram, twitter, iOS, OSX, Windows (god)... once you expect something to work good that you would pay for, the only thing left to do is to make it shitty and sell the quality back you for extra margin. it's called private equity (polite term for the business of telling people "it's not yours, it's mine"), favorite son of capitalism

the discourse around "code quality" has always attracted the least nuanced minds, ones who see the world and the phenomenon of life as nothing but territory to be divided up by the latest buzzwords. the worst ones insist that we narrow the discussion even further, to focus on the conflicts between these buzzwords. whenever i have to sit through such discussions, i try to meditate on the irony of mother nature weaving the most functionally brutal, ruthlessly redundant poetry that is the genetic code, only for the resulting creatures to deny themselves the power of the principles inherent in their own construction.

i've learned in two years of unemployed hacking that there is a camp 3: you treat code like an evolving life form, requiring both ingenious introspective craft and utilitarian grit to survive and thrive. a product is a trajectory of software in time, and software is a trajectory of code in time; this is no different from how our genetic code determines our physical existence, which then shapes our lives. there is no spectrum between code vs product; if you want to remain relevant in software design, you must see them as layers of a larger whole (and there are many, many more layers once you go beyond the binary of code VS product).

false dichotomy. neither company will make it. the winner will be some solo dev with a singular vision and ruthless dedication to quality. “teams” do not have visions, individuals do. the more people are involved in a product, the blurrier the vision becomes, the more insidious the vested interest of the organization to profit from the user, rather than align themselves with the user. solo devs do not have such problems, because they’re no different from users, aside from the fact that they were users before the software existed. they make the software because they want to use it, and there is no amount of payroll employees that can replicate the quality and innovation that results from this simple, genuine self-interest.

i’ve been doing this for a while, you create an extra file for every code file, sketch the code as you currently understand it (mostly function signatures and comments to fill in details), ask the LLM to help identify discrepancies. i call it “overcoding”.

i guess you can build a cli toolchain for it, but as a technique it’s a bit early to crystallize into a product imo, i fully expect overcoding to be a standard technique in a few years, it’s the only way i’ve been able to keep up with AI-coded files longer than 1500 lines

copyright is not “broken,” it was always a two-faced scam designed to protect “owners” at the expense of creators. don’t expect this blatant hypocrisy to kill copyright, either - death of copyright is a slippery slope leading straight to communist utopia, and the death of the global acqui-parasite class

in a world where getting 3 people to show up to dinner is a challenge, a coherent, organized group large enough to be visible as a percentage of the population is an exceedingly rare and powerful entity. but history shows that such an entity is usually either 1) stable and peaceful, but actively decaying due to its position of hegemony or 2) unstable and violent, using conflict to sharply define its boundaries and growing by dividing the rest of society into "insiders" and "outsiders". some days i feel like we're microbes stuck in microbiological cycles. but if we make it past this rut, we will have all that we need to lay down an even stronger foundation, to codify systems and organizations designed to scatter and suppress hate and intolerance.

nothing lives forever. software comes into life out of necessity, develops complexities, eventually becomes incomprehensible, obsolete and dead. it’s a natural cycle that we should work into the user experience, instead of defining it as a failure state that we need to “solve for”.

most web pages are about to be HTML/JS/CSS generated by LLMs directly for users. Truth is, pre-LLM web frameworks were designed for two things: save developer keystrokes and delay the spaghettification of the codebase. We just automated keystrokes, so that's largely irrelevant now. Users don't read code, so spaghettification is also a non-issue, as long as the framework defines clear containers for spaghettis, and provide clear ways to fork the spaghetti or start over when the user is frustrated with some bug. There's no framework designed with these requirements in mind, but I am working on one.

we’ve been taught to think of programs as sculptures, shaped by the creator to a fixed purpose. with LLMs, the greatest advance isn’t in being able to make larger and more detailed sculptures more quickly; it’s that you can make the sculptures alive.

generic advice about how you should use the same tool and methodology (claude code, scrum) that everyone’s already using, lot of hand waving about being “senior,” This may be the most 2025 blog post ever written.

if anyone takes the art of software programming further using LLMs, it’s going to be young inexperienced people who grow up closely observing and learning the transcendental nature of LLMs and software, not hardened industry titans joyfully cracking their whip over an army of junior devs and LLMs.

there's always people who go against the incentives - all they need to win is for the status quo to become so rigid and fragile to a point where all it takes to create a promising independent alternative is like one guy determined to be "based"

these are excellent questions, but imo the answer isn't "the old web lacked unnecessary friction designed to inflate the cost of basic storage operations" - the blockchain is a lie: it is obviously the most centralized form of computing (literally nothing can happen without global consensus?), being sold as "decentralization". It is a scheme to trap the web into a centralized ledger and sell it to the highest bidder.

the web died years ago, for a different reason: labor monopoly. The web, and software in general, stopped reflecting or serving users, when the ruling class started pouring massive capital to dismantle any paradigm for major web/software development other than ones vetted by pedigree VCs and planned for obsolescence by acquisition. Gen AI is actually the only thing that could’ve punctured their hold on world software - the vague air of confidence they maintain when they talk about “their future of AI” is a facade. There’s already a new Web (or Webs) coming that will dwarf the current one, and it won’t be coming from them - so they’re clinging to their only means of control: the AI token infra.