acmerfight

8 ms·

1.
Pi's AgentHarness: From an In-Process Loop to a Durable Runtime(github.com)
1 points by acmerfight 1mo ago|0 comments
2.
Claude Opus fixed 3 production bugs perfectly. All 3 were the wrong fix(gist.github.com)
2 points by acmerfight 5mo ago|0 comments
3.
by acmerfight 6mo ago
Agreed. This is pure architectural thinking: you hold the ground truth, enforce the strict IAM boundaries, and outsource the mud-playing to the LLM. Mindless 'vibe coding' without this structural discipline is just tittytainment.
4.
by acmerfight 6mo ago
Guilty as charged. As a non-native speaker, I used an LLM to compile my original thoughts into fluent English. But notice the irony: I used AI exactly as I advocate. It handled the horizontal spread (syntax), while I rigorously enforced the
5.
by acmerfight 6mo ago
This is a phenomenal example of exactly what I am advocating. Notice you didn't ask the AI to 'just design a stereo pedal for me.' You interrogated it, reasoned about netlists, and forced the concepts into your brain through
6.
by acmerfight 6mo ago
Ironically, what you described is exactly using AI to help with deep work. You do the heavy lifting (reading), and use AI strictly for stateless verification and testing your mental model. That is the ideal synergy.
7.
by acmerfight 6mo ago
Spot on. The ultimate bottleneck is no longer generation; it's verification. If you don't intrinsically know what 'right' looks like, AI simply helps you build the wrong thing faster. This internal compass is exactly wha
8.
by acmerfight 6mo ago
Pure 'vibe coding' is essentially technical 'tittytainment'. Using AI for the horizontal spread while you enforce vertical architectural depth is true deep work.
9.
by acmerfight 6mo ago
We actually don't disagree at all—you are perfectly illustrating my point. Applying strict epistemic discipline (Popper, Russell) to resolve ambiguity and accelerate actual practice is the very definition of deep work. You aren't
10.
by acmerfight 6mo ago
I burn through $5,000 a month in API tokens. I am the last person to romanticize manual toil. The issue is the difference between using AI for shallow outsourcing ('summarize this') and deep cognitive work ('stress-test this
11.
The risk of AI isn't making us lazy, but making "lazy" look productive
76 points by acmerfight 6mo ago|88 comments
12.
The Fatal "Hotwire": Deconstructing Cloudflare's 2025 Architectural Meltdown(medium.com)
2 points by acmerfight 9mo ago|1 comments
13.
by acmerfight 9mo ago
Cloudflare’s dual 2025 outages weren't just about a missed Lua nil-check or a sloppy Rust unwrap(). They were the inevitable cost of "hotwiring" production to bypass ancient, broken test harnesses during a security panic. Thi
14.
AI Can't Save Software Engineering(medium.com)
7 points by acmerfight 11mo ago|2 comments
15.
by acmerfight 11mo ago
Lately, many people have been talking about AI for Software Engineering (AI4SE), hoping to find the next big startup opportunity there. My view is straightforward: this path leads nowhere. Most of these ventures make a fundamental mistake —
16.
Why Can't We Make Simple Software? – Peter van Hardenberg [video](youtube.com)
1 points by acmerfight 1y ago|0 comments
17.
Stop Solving Problems by Adding Processes(medium.com)
6 points by acmerfight 1y ago|1 comments
18.
by acmerfight 1y ago
Many SRE and operations teams predominantly address operational risks through “additional approval processes” — whether for database schema changes, service deployments, client releases, etc.
19.
Designing for the web ought to mean making HTML and CSS (2019)(signalvnoise.com)
8 points by acmerfight 2y ago|4 comments
20.
by acmerfight 2y ago
TikTok and the Scope of the Communications Act of 1934 Are Different The Communications Act of 1934 primarily targets traditional media (e.g., television, radio), while TikTok is an algorithm-driven social media platform where content is us
21.
Show HN: CCState is a semantic, strict, and flexible state management library(github.com)
16 points by acmerfight 2y ago|3 comments
22.
The Lies About Abstraction(alperenkeles.com)
1 points by acmerfight 2y ago|0 comments
23.
by acmerfight 2y ago
You're absolutely right that if someone decides to create a DSL, it needs to be done right. The issue, however, is that most DSLs fail to meet this standard. Extensibility and leveraging existing tooling, as you suggest, are indeed cri
24.
by acmerfight 2y ago
Thank you for sharing your thoughts. You’ve highlighted some great examples of DSLs that have become essential tools in software development, like SQL and Markdown. However, the success of these DSLs often lies in their universality, broad
25.
by acmerfight 2y ago
Thank you for your feedback! I've removed the image to make the content clearer. Please let me know if there’s anything else I can improve.
26.
Stop Torturing Your Colleagues with DSLs(medium.com)
3 points by acmerfight 2y ago|7 comments
27.
Lil’Log from OpenAI VP(lilianweng.github.io)
1 points by acmerfight 2y ago|0 comments
28.
Desired State Systems(branislavjenco.github.io)
2 points by acmerfight 2y ago|0 comments
29.
Strategic Scala Style: Principle of Least Power(lihaoyi.com)
2 points by acmerfight 2y ago|0 comments
30.
Writes and Write-Nots(paulgraham.com)
3 points by acmerfight 2y ago|2 comments

More ›