Kevin Lyda
Software developer in the West of Ireland. Can also be found at https://mastodon.ie/@lyda
The mouse pointer background is kinda a dick move. Good article. but the background is annoying for tired old eyes - which I assume are a target demographic for that article.
ls /usr/share/man/man?/* will show you all the man pages on your system. I used to pick ones at random.
Originally there were a number of manuals. Manual 1 had user commands. Manual 2 had system calls. Etc. You can type man NUMBER intro to read about that manual. You can also use man -k or appropos but I’ve also just used grep. These days they’re compressed so zgrep.
I suppose I should be clearer on the features I want. I’d want to be able to store my cache in memcached or redis and I want the cached data to expire. So for one call, I might want to keep it for five minutes, but another one can stick around for 24 hours.
The memorize package falls down there.
I have never heard proper reasoning for squashing commits. I don’t think sanitized history is useful in any context. Seeing the thought process that went into building something has been repeatedly useful in debugging things. It’s also useful to me as a software engineering manager to help folks on my team get better. I could care less how “pretty” git log looks, but I care a hell of a lot about what git diff and git blame tell me. They help me figure out where issues actually are and how they came to be.
And then
git ci -am "Addressed performance issue in flurbin module
The flubin module was designed as a successor to the flurbar module
which took in...
[...500 line essay on the hostory, problem and solution deleted...]
Hopefully this will fully fix the issue discussed."
for a one character change that adds an additional, and unrequired, semicolon.