11–20 of 30 posts
Working in software professionally, the internal struggle I seem to have is separating "personal software" from "resume fodder." The line of thinking is generally: "Why create this one-off thing for myself when I can publicize it, get some contributors, and add it to my list of successful OSS projects." It's a terrible loop, to be honest.
Working in software professionally, the internal struggle I seem to have is separating "personal software" from "resume fodder." The line of thinking is generally: "Why create this one-off thing for myself when I can publicize it, get some contributors, and add it to my list of successful OSS projects." It's a terrible loop, to be honest.
I wrote a notes app in react native just for myself a few years ago (out of frustration after changing notes apps every year or so) that does /exactly/ what I want and it has been the most used app on my phone for a few years now. It's offline-first but syncs reliably, uses the exact interpretation and display of markdown I like, searches and sorts the way I like, integrates with AI only in the ways I want it to (spe…
Working in software professionally, the internal struggle I seem to have is separating "personal software" from "resume fodder." The line of thinking is generally: "Why create this one-off thing for myself when I can publicize it, get some contributors, and add it to my list of successful OSS projects." It's a terrible loop, to be honest.
Do you write scripts for you own use? I've usually been able to do that without thinking "I really should publish this".
It's a culture I've subconsciously adopted, and I appreciate the author's intent to shrug it off.
I wrote a notes app in react native just for myself a few years ago (out of frustration after changing notes apps every year or so) that does /exactly/ what I want and it has been the most used app on my phone for a few years now. It's offline-first but syncs reliably, uses the exact interpretation and display of markdown I like, searches and sorts the way I like, integrates with AI only in the ways I want it to (spe…
Often the IDE tooling for certain languages doesn't work for me. It's too bloated or slow. I write my own tools instead. They're fast and tailored to my workflow. Custom debuggers, analyzers, etc.
I often need to perform certain tasks... sometimes they don't warrant any kind of automation. However I'll often write snippets of code in a literate `org-mode` file as I work and write down what I was doing/why, etc. Occasionally these will get tangled into a proper script that becomes the automation.
I grew up in an era when computers only came with a manual and a bare bones operating system. Writing your own tools was part of the experience from that time which stuck with me.
For any decent programmer, writing reusable small applications has always been a thing. Nothing new.