sn0wflak3s

3 ms·

1.
So Much for O(1)(yasint.dev)
3 points by sn0wflak3s 6mo ago|0 comments
2.
Show HN: Envsh – Zero-knowledge secret sync using your SSH keys(envsh.dev)
1 points by sn0wflak3s 7mo ago|0 comments
3.
by sn0wflak3s 7mo ago
The line is scope. I'm not asking an agent to build me a full-stack app. That's where you end up babysitting it like a kindergartener and honestly you'd be faster doing it yourself. The way I use agents is focused, context-dr
4.
by sn0wflak3s 7mo ago
I wrote it myself. But the irony isn't lost on me. "Who did what" is kind of the whole point of the article. Appreciate the feedback.
5.
by sn0wflak3s 7mo ago
This is a fair point. The cognitive load is real. Reviewing AI output is a different kind of exhausting than writing code yourself. Even when the output is "guided," I don't trust it. I still review every single line. Every s
6.
by sn0wflak3s 7mo ago
I get this. I don't think either of you is wrong. There's a real loss in not writing something from scratch and feeling it come together under your hands. I'm not dismissing that. I have immense respect for the senior enginee
7.
by sn0wflak3s 7mo ago
Fair enough. I know how that reads. But when anyone with a laptop and a subscription can ship production software in a weekend, the architecture and the idea start to matter a lot more. The technical details in the post are real. I just can
8.
by sn0wflak3s 7mo ago
This is the question I keep coming back to. I don't have a clean answer yet. The foundation I built came from years of writing bad code and understanding why it was bad. I look at code I wrote 10 years ago and it's genuinely terri
9.
by sn0wflak3s 7mo ago
The K-shaped workforce point is sharp and I think you're right. The curious ones are a minority, but they've always been the ones who moved things forward. AI just made the gap more visible :) Your Codex case study with the conten
10.
We might all be AI engineers now(yasint.dev)
224 points by sn0wflak3s 7mo ago|353 comments