3 ms·
> I spent that time building, learning, and trying to get better. Looking back now, much of it feels like time spent getting better at a problem that has alread
by zahlman 2mo ago
> I spent that time building, learning, and trying to get better. Looking back now, much of it feels like time spent getting better at a problem that has already been solved.
> And so I have come to a harsher conclusion: I wasted a lot of that time. What I have done feels bad, and I do not see what is left for me to do in this direction.
Unless you didn't actually build, learn and improve, how could it have been a waste?
Do you really not value becoming a more capable person, in and of itself?
- gokuljs 2mo agoIf you can do system design well, prompt effectively, and ask the right questions, I don’t see much point in going extremely deep into all of this anymore. I’ve learned a lot of new things, but now it often feels like I can just prompt the model and get the implementation in one shot. For problems with a closed feedback loop, I don’t think you need to spend nearly as much time learning every implementation detail. A person who never invested that time can often produce the same result with the right tools. That’s the part I’m struggling with.
- zahlman 2mo agoThe interesting problems don't have a closed feedback loop. You don't know what the requirements are until you try something yourself and decide that isn't it.
- gokuljs 2mo agoTell me at least one interesting problem that you have encountered. That is related to coding and software engineering
- taurath 2mo agoIdk in my experience that’s the mark of someone whos not worked on complex or critical systems, or is wowwed by a bunch of PoCs.