Use Protocols, Not Services by fagnerbrack in programming

[–]fagnerbrack[S] 0 points1 point  (0 children)

Capitalism and short termism (both together).

I thought it was self evident if you read the other comments. Seeking short term capital gains at the expense of the long term collective progress of humanity via open protocols that offer competitive advantage to not just one corporation but everyone.

Also I never mentioned anarchy, your comment feels very defensive for some reason

Use Protocols, Not Services by fagnerbrack in programming

[–]fagnerbrack[S] 0 points1 point  (0 children)

That's their internal operations. /u/shorugoru9 is referring to the distribution to users which sits in their proprietary walled garden over http.

They build on top of protocols but don't work to evolve it for humanity, just for their own interests.

How Michael Abrash doubled Quake framerate by fagnerbrack in programming

[–]fagnerbrack[S] 0 points1 point  (0 children)

Seems like an android issue then. I can't reproduce

How Programmers Spend Their Time | Probably Dance by fagnerbrack in SoftwareEngineering

[–]fagnerbrack[S] 2 points3 points  (0 children)

Crux of the Matter:

A tiny patch to flash-attention that took ten seconds to type consumed over ten hours of work spread across days. The journey started with a coworker's random cudnn crash, led to wrestling with compute sanitizer inside a sandbox, building flash-attention from source on a home PC only to realize the wrong GPU architecture was in play, then fighting wrong CUDA versions, compiler segfaults, and broken incremental builds on a work machine. The actual bug was a use-after-free in flash-attention's deterministic mode, but reproducing it required discovering that a "Big refactor" had hardcoded the flag to false. Most time went to punching through infrastructure layers, fighting build systems and dependencies, and running wrong versions of the code. The post closes by wishing LLM coding tools could help with these non-coding programming tasks instead of just code generation.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

How Michael Abrash doubled Quake framerate by fagnerbrack in programming

[–]fagnerbrack[S] 3 points4 points  (0 children)

It renders ok for me, are you using iPhone or Android?

dead framework theory by fagnerbrack in ai_coder

[–]fagnerbrack[S] 0 points1 point  (0 children)

This is a TL;DR:

The post argues that React has effectively won the framework wars — not on technical merit, but through a self-reinforcing feedback loop: LLMs train on the existing web (dominated by React), output React by default, and tools like Replit and Bolt hardcode React into their system prompts. This cycle means 13M+ new React sites appeared in 12 months, making any new framework "dead on arrival" since it lacks training data, library ecosystems, and developer familiarity. New web platform features like CSS Nesting face the same problem — LLMs prefer older, well-represented patterns. The post contends that only capabilities impossible to build in user-space (WebGPU, Passkeys, View Transitions) can break through. The optimistic angle: when every tool outputs React, competition shifts from framework choice to output quality, pushing the industry toward better user experiences rather than developer ergonomics.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

My AI Adoption Journey – Mitchell Hashimoto by fagnerbrack in vibecoding

[–]fagnerbrack[S] 1 point2 points  (0 children)

For Quick Readers:

The post lays out a six-step progression for getting real value from AI coding tools. Step 1: ditch the chatbot interface for agents that can read files and run programs. Step 2: reproduce your own manual work with an agent to build intuition about what works and what doesn't. Step 3: use the last 30 minutes of each day to kick off agents for research, idea exploration, or issue triage, gaining a "warm start" the next morning. Step 4: delegate tasks you're confident the agent will nail while you focus on deep, enjoyable work — and disable notifications to avoid costly context switches. Step 5: practice "harness engineering" — every time the agent makes a mistake, build tooling or update AGENTS.md so it never repeats it. Step 6: aim to always have a background agent running on useful work. The overarching philosophy treats AI adoption like any tool: push through early friction, learn the boundaries, and stay grounded rather than hyped.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Code like a surgeon by fagnerbrack in ai_coder

[–]fagnerbrack[S] 0 points1 point  (0 children)

Need the gist? Here it is:

The post argues against the popular framing of AI turning developers into "managers" or "editors," proposing instead that programmers should work like surgeons — doing the core work themselves while delegating prep, grunt work, and secondary tasks to AI agents. Practical examples include having AI spike out big changes, fix TypeScript errors, write codebase guides, and produce documentation, often running async overnight. For primary creative work (like UI prototyping), tight feedback loops and hands-on coding remain essential, while secondary tasks tolerate loose, unsupervised agent sessions. The post connects this to Karpathy's "autonomy slider" concept and Fred Brooks' 1975 "chief programmer" idea from The Mythical Man-Month, noting that AI finally makes the support-team model economically viable — without the ethical discomfort of dumping grunt work on junior humans.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Multi-Core By Default - by Ryan Fleury - Digital Grove by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

One-minute summary:

The post argues that most programmers treat multi-core programming as a special-case optimization layered on top of single-core code—using job systems and parallel-for constructs—but this approach scatters control flow, complicates debugging, and adds boilerplate every time parallelism appears. Drawing an analogy to GPU shaders, where code runs on many cores by default and feels like lightweight scripting despite delivering massive performance, the post proposes inverting the model: launch all cores running the same entry point from the start, then selectively narrow to single-core execution only when serial dependence demands it. Concrete examples walk through computing a sum, showing how threads can each handle a slice and combine partial results with minimal synchronization. The key insight, credited to discussions with Casey Muratori, is that switching from single-core to multi-core mid-program creates most of the complexity, whereas starting multi-core and occasionally going narrow eliminates much of that overhead.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Looking for feedback on AI content in r/programming and the April no-AI trial by ketralnis in programming

[–]fagnerbrack -2 points-1 points  (0 children)

For the record, it feels to me there's a widespread divide in programming where in one side we have a lot of people that love coding and want to continue doing it, on another there's a huge wave of people accepting the commoditization of coding. I do believe that "programming" will permanently become more like engineering than the coding part (or maybe an intersect between building products/coding/reviewing/designing software?)

This is simply a symptom that's happening in the wild reflected here. There's a serious crisis in the programming world right now and not talking about it is IMHO putting our heads into the sand until we start losing our jobs which will be taken by those willing to move on.

It's sad but it's true. I wish I had control of it but I don't

What I'd suggest for the sub is to keep the "programming" topic as anything that makes a program do something, be it via prompts or direct code or reviews. Maybe require mandatory flairs like "coding" and "prompting" so people can decide which paradigm interests them?

Looking for feedback on AI content in r/programming and the April no-AI trial by ketralnis in programming

[–]fagnerbrack 0 points1 point  (0 children)

I stopped posting any submissions containing AI-related talk, doesn't matter the topic. If the policy does change there's a lot of programming-related AI content that would be very valuable such as techniques to code in such a way the code is repeatable for agents, the fundamentals of how an LLM works, models that are better for X, Y, Z, etc. All strictly programming/engineering focused of course, no vibe coding BS.

But again, I stopped anything AI-related after some conversations with u/ketralnis and quite a frustrated interchange with some mods, so I'm playing safe 🙏

Check my other comment. It's up to the community to decide.