Viewing profile — acmerfight
acmerfight
HN member- Joined
- Mon, Jan 29, 2024, 3:03 AM UTC
- HN karma
- 103
- Public activity
- 55 items
- HN profile
- View on Hacker News ↗
About acmerfight
No profile information was provided.
Recent public activity
-
comment
Comment #49255682
[flagged]
- story
- story
- story
- story
-
comment
Comment #47568765
[dead]
-
comment
Comment #47568718
[dead]
-
comment
Comment #47559874
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 …
-
comment
Comment #47559430
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…
- comment
-
comment
Comment #47556088
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…
-
comment
Comment #47556070
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 menta…
-
comment
Comment #47555993
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 fast…
-
comment
Comment #47555906
Pure 'vibe coding' is essentially technical 'tittytainment'. Using AI for the horizontal spread while you enforce vertical architectural depth is true deep work.
-
comment
Comment #47555875
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 practic…
-
comment
Comment #47555846
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'…
-
story
The risk of AI isn't making us lazy, but making "lazy" look productive
I've been reflecting on how LLMs are changing our learning habits as engineers, and realized something worrying. AI can now quickly help search and research information, distilling…
-
comment
Comment #46263047
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, broke…
- story
-
comment
Comment #45642305
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 …
- story
- story
-
comment
Comment #43960814
Many SRE and operations teams predominantly address operational risks through “additional approval processes” — whether for database schema changes, service deployments, client rel…
- story
- story