cn80

Since some asked: five months of Absurd in production. Durable execution on plain Postgres with tiny SDKs. The design held up fine, partitioning is still hard and some closing thoughts on the future of Open Source. lucumr.pocoo.org/2026/4/4/absur…

this thread is what mass cope from legacy devs looks like. i talked to @FastCompany about why @garrytan's "AI slop" is actually the future of software engineering. the mass code review. the line-by-line gatekeeping. the "craftsmanship" that was really just slow iteration disguised as rigor - that era is over. and the engineers who built their entire identity around it are panicking. @gregorein brags about burning 3 billion tokens last year while dunking on garry for flexing lines of code. i've burned 6.6 billion in the past three months on codex alone. by his own logic, i'm 8x as credible. see how silly that sounds? yes, he found real issues. yes, they got fixed. that's exactly the point. karpathy's autoresearch proved this already - AI agents can solve very complex problems just by operating inside feedback loops, iterating to optimize a loss function. this is what software engineering is now - gradient descent. ship, measure, self-correct, repeat. all by the agent itself. this is the new startup playbook. your job isn't to review every line before deploy. your job is to build systems where agents observe outcomes - mrr, analytics, error rates, user behavior - and self-improve. the engineer's role shifts from gatekeeper to building the machine that builds the machine. you could run this level of audit (using AI) on any production site and find the same issues - most just don't have a billionaire CEO attached for virality. mocking the people who adapted is easier than adapting. but the craft is evolving whether you like it or not.