I swear this is like the fifth time I've seen something like this on HN!
Is this a "everyone feels the need to reinvent the wheel" thing, or is it a "junior dev gets excited by an idea, builds an implementation ... and then realizes there are inherent flaws in the approach, and gives up ... until the next junior learns about the idea and ..."?
I can't wait until it's formalized enough that I can just buy a $20 light bulb, update it wirelessly somehow, and then have my own little "light bulb library" server.
It's so annoying how he starts out talking about boot speed, does the entire project, and then doesn't even mention how long it takes to boot up! All he ever says is "boots a bit quicker".
They do, but only for specific definitions of "work". Like, benevolent dictators in Cuba 100% raised the literacy rate by an insane amount in just a few years (something like 20% => 80%").
If you define work as "literacy", they no doubt succeeded. But if you consider the people (and children) they tortured, raped, and murdered, suddenly literacy doesn't seem so important.
> Turns out, the friction I felt around picking one thing may have actually been beneficial. Perhaps it was actually helping me stay focused. Even if it cost just a bit of extra time before I sat down and worked.
It's point is highlighting a common issue that is becoming widespread due to AI tool proliferation. I have the same exact issues. I used to love sinking into deep work mode but now that's gone.
Is this a "everyone feels the need to reinvent the wheel" thing, or is it a "junior dev gets excited by an idea, builds an implementation ... and then realizes there are inherent flaws in the approach, and gives up ... until the next junior learns about the idea and ..."?
reply