Man, I can just like, upload whatever I want to PyPI and it's great.
I really want to like biome,
but having to have a configuration file to cause it
to use spaces over tabs (the default for prettier) isn't great.
I don't have .prettierrc and don't really want to start with biome.json
either.
What does it say about me that tinkering with CI is more addictive than Netflix?
python -m http.server is such a nice built-in command and I wish I knew about
it like ten years ago
I think I have an unhealthy addiction to setting up CI.
Are people really so slow at reading emails that having an LLM summarize the email for them is useful? I can't imagine not preferring to just read the original.
we learned that apparently the actual purpose of MOP was to mine OTIS diamonds buried deep within the earth
that has got to be one of the quotes of all time
all i want for christmas is django support for ty
Appreciated this paragraph from gasche:
The policy that I proposed has been described to me as:
- disturbingly anti-AI by people who are very positive about AI usage for programming
- disturbingly pro-AI by people who are very negative about AI usage for programming
My immodest take-away from these conflicting sentiments is that the proposed policy is in fact reasonably balanced.
I think I would have liked to have a teacher like Dijkstra.
Reading ocaml PR 14369 generates so much entertainment value for me every time.
Actually one of my favorite parts of the MOSP hunt is the rec letter in the Epilogue of Chapter 1.
Are these log messages too snarky?
log "♻️ RELOAD TRIGGERED. Every day I'm shuffling 🔀"
# …
log "☀️ GOOD MORNING, my glorious webmaster! How are you this fine $(date +"%A in %B")?"
log "🩷 Please enjoy these logs, I wrote them just for you 💌🖋️"why do i push updates to production right before going to bed on a Friday night isn't that just asking for trouble
oh it's almost april 1 which means it's time for me to decide on a new career
I'm always reminded of this sentence in esr's how to ask questions
When asking your question, it is best to write as though you assume you are doing something wrong, even if you are privately pretty sure you have found an actual bug. If there really is a bug, you will hear about it in the answer. Play it so the maintainers will want to apologize to you if the bug is real, rather than so that you will owe them an apology if you have messed up.
I feel like I always did this, and it just seemed like common sense to me. In fact, I assumed that's what everyone did. But apparently not?
It's pretty nice that most of the museums in Washington DC are free.
New mosp.evanchen.cc archive up and running!
Maybe binge-watching High Potential is not a good way of coping with not having enough time to finish my work.
A sentence I read on Wikipedia today:
On 30 April 2015, the U.S. Federal Aviation Administration announced it will order Boeing 787 operators to reset its electrical system periodically, to avoid an integer overflow which could lead to loss of electrical power and ram air turbine deployment, and Boeing deployed a software update in the fourth quarter. The European Aviation Safety Agency followed on 4 May 2015. The error happens after 2^31 hundredths of a second (about 249 days), indicating a 32-bit signed integer.