But maybe we'd all be a little saner if we remembered what we're actually doing: building tools to make our lives and the lives of others easier.
Any conversation
ๆ
ไบ็ๅผๅคดๆปๆฏ่ฟๆ ท๏ผ้้ขๅ
ถไผ๏ผ็ไธๅ้ฒใๆ
ไบ็็ปๅฑๆปๆฏ่ฟๆ ท๏ผ่ฑๅผไธคๆต๏ผๅคฉๅไธๆนใ๏ผby ๅผ ๅไฝณ ใไปไฝ ็ๅ
จไธ็่ทฏ่ฟใ๏ผ
Stories always begin this way: a chance encounter, completely unexpected. Stories always end this way: two flowers bloom, then drift apart. (by Zhang Jiajia, I Belonged to You)
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
i got into the fashion to vibevode some utility apps for myself. i didn't review the code. they work fine. colleagues are interested.
i don't feel comfortable to put such stuff on $Github. have no good consciousness with unreviewed and likely ununderstood (stack I am not really familiar with).
internet is full of people who don't care, I know. i tend to overthink.
what about you?
Whatโs the difference between a script-kiddy and a real ? Abstraction. You can program your whole life without learning how to meaningfully abstract problems into simpler pieces that TRULY make the problem easier to understand.
Iโm not talking about design patterns or vs . These tools can help. But to really simplify something for others, you need an intellectual empathy that many simply never figure out.

