Rule 4, I have always practiced and demanded of junior programmers, to make algorithms and structures that are simple to understand, for our main user: the one who will modify this code in the future.
I believe that's why Golang is a very simple but powerful language.
Few software companies consider this: users appreciate it when the interface remains constant over time, and especially if we can continue using previous versions without being forced to change, since learning new things again takes time.
My biggest fear with macOS right now is that because there's no LTS version, I'll eventually be forced to upgrade in 2-3 years if I want to use some new apps compiled by some hipster developers who use Xcode 28/29 and don't care about old versions.
Homebrew doesn't support any macOS version that isn't supported by Apple either.
It's laughable how often companies redesign the UI, when it's counter to what their users want. Nobody wants to re-learn how to interact with their software. Gradual changes, sure, but a total redesign and then releasing it as a "feature" is such a turn-off to so many people.
When working with CLI agents like Claude Code on writing projects, the most natural generation format is Markdown. But iterating on those docs via Google Docs is painful — uploading a Markdown file to Google Drive with proper formatting requires multiple manual steps.
md2gdoc reduces this to one command. gdoc2md does the reverse.
I have followed him for a long time and learned a lot too. I always wonder the same thing about the “tech influencers” and I’d love to know more about how they structure their days.
I find it difficult recently to sit down and complete a meaningful piece of work without being distracted by notifications and questions. In the last year this has been exacerbated by the wait time on LLMs completing.
I would love to know how top performers organise their time.
reply