HackerLangs
トップ新着トレンドコメント過去質問紹介求人

possiblydrunk

no profile record

コメント

possiblydrunk
·3 か月前·議論
Dammit! I was hoping for advice on improving and maintaining my backyard shed. My shed is not a means, it is an end. And it, too, brings me peace and joy and sometimes despair or a great laugh. Sometimes I even apply principles from work (but orthogonally) to development of my shed.
possiblydrunk
·4 か月前·議論
Nitpicky comment. The article says > "We call this the “light and shade” of AI: the same capabilities that lead to > benefits also produce harms. The two sides are entangled."

Why not call it a "double-edged sword" or something else? Light and shade are opposites but not necessarily two products from the same tool. It just irks me.
possiblydrunk
·4 か月前·議論
Nicely done! Scale matters. If you make something big enough relative to its expected size, it will impress and captivate, even if it's simple. General observation, not that the construction here was by any means simple.
possiblydrunk
·4 か月前·議論
Fair assessment, but you seem to love "creating" rather than "programming", not that there's anything wrong with that! Pondering the merits of AI has made me realize the opposite -- I love the process and challenge of creating (the programming) even more than the final product. AI is undoubtedly helpful, but when it solves my problem for me I'm not nearly as satisfied? as if I'd solved it myself. It's like copy-pasting an answer from StackOverflow, but for a whole program. I doubt my employer will share my feelings, and I'll have to use increasingly more AI to keep up the productivity.
possiblydrunk
·4 か月前·議論
Optimization usually trades complexity for speed. Complexity hinders debugging and maintenance. Don't optimize unless you have to and not before you know where the bottleneck is. Straightforward common sense advice as long as hardware is not persistently constraining.
possiblydrunk
·4 年前·議論
Being kind is for the benefit of the receiver, being nice is for the benefit of the giver.