Many school shooters talk about wanting to be seen, wanting fame/notoriety, and so on. With the huge positive response to this, it wouldn’t be too surprising to see copycats. “If I do this, people will remember me and love me for it.”

I see the great minds are thinking alike

My reaction when I heard it was trending was to slap this together:

The idea that a country needs (to exist) to be ruled by a single individual is completely unfounded, and perpetuated by people who are either fools or foolish enough to think they have a shot at the throne. Early on, there were proposals for the USA to have a king, a president, and many other ideas including no executive branch or having a tribunal. I could see a good case for splitting the executive across 3 persons with equal and asymmetrical powers.

Assuming you do a ranked choice vote for all 3 at once (or 1 at a time in rotation, like Senators) it should be extremely difficult to compromise the office by, say, buying one deeply indebted former TV host and running them for president.

¿Por que no los dos?

Who’s that supposed to be? Must not get up to the Cloud District very often!

I’ve absolutely driven past a cop who was playing WoW on his laptop while sitting in traffic.

“The economy” is just money in motion. Like how electric charges moving create light, moving money carries and creates value in the exchange. When rich people soak up money from millions of people, they destroy all that value and the economy stagnates. When millions of people are given money and then spend it in millions of ways, the global economy improves.

We optimize our economy around stagnate money sitting in septic pools, when we should be trying to build an ocean of money that never stops flowing.

Her story behind this is so funny too. She’s claims she was already sitting there, when Putin and a handler just walked up and sat down. No one said anything because no one spoke Russian (though Putin speaks English and German, and apparently didn’t have a translater handy at this international event). Since no one could talk, they awkwardly got up after a while and walked off!

Sounds extremely plausible and defensible to me, don’t see what people are so hung up about! /s

In Alejandro Jodorowsky’s concept for a Dune film from the early 1970s, each house has their costumes and architecture designed by a contemporary artist. Giger was the designer for the Harkonnen, and several of his ideas persisted beyond the failed film.

The Harkonnen Castle

A Harkonnen chair

I assumed Villeneuve was calling back to those designs.

Former president and current chair of the face-eating leopard party shocked at the amount of hungry cats patrolling around their mansion.

I’ve been wanting to get a pipe Garfield tattoo since first seeing this. It changed me. Made me better.

I’m definitely getting my blog going regularly again… next year…

I wrote a powershell script to parse some json config to drive it’s automation. I was delighted to discover the built-in powershell ConvertFrom-Json command accepts json with // comments as .jsonc files. So my config files get to be commented.

I hope the programmer(s) who thought to include that find cash laying in the streets everyday and that they never lose socks in the dryer.

Seeing this actually sent a small wave of dread through my body

I should get to work on my opus, “Dirty Code”

Inside I’ll reveal all my secrets like: not writing tests, not documenting anything, putting the whole app into a single python file, object-disoriented relational mapping, obscure SQL tricks, unobscure no-sql tricks, and more!

I made a static site with Hexo a few years back. I thankfully didn’t make any “Get started with Hexo” posts but I did only really use it for a few months. I think that puts me in the cluster with the “switch from Jekyll to Hugo” people. Now it just sits there, absorbing some money every two years for the “personal website tax”.

Shame too, I constantly think I need to get back to it. Hexo is nice, popular with Chinese users I think. I don’t recall now why I liked it over Jekyll or Hugo, but I’ve always loved an underdog. Once I got the hang of using it, it was very customizable and fun to work with.

As a senior at my last big company job, basically all I did was conduct meetings and do PRs. It’s such a grind.

My opinion now is that most PR is worthless anyway. Most people give, at best, a superficial skim for typos, lack of comments, or other low-hanging replies (that usually, really, a static checker or linter should be dealing with).

Reading the code base in little chunks like that doesn’t give you proper context for the changes you’re reading. Automated unit and integration tests would be better for catching issues like that, but of course then who is reviewing and verifying the tests? Who’s writing them for that matter?

Ideally, pair-programming or having extra people on projects to create knowledge redundancy would help. But companies want to replace juniors with AI now, so that’s not looking good. Senior devs and architects might know the major pieces of much of the code, but can they “load it into working memory” sufficiently to do a quality PR that will catch something the tests didn’t and QA wouldn’t? Not in my experience.

I think the best actually-implementable solution for most teams is to get rid of PR expectations and take a multi-pronged approach to replacing that process.

1. use tooling to check for and fix basic stuff. Use a linter, adopt a code standard, get a code formatting tool that forced adherence to the standard and run it on every PR.
2. Unit tests if you got them, start if you don’t. You don’t need 90% code coverage, just make sure critical paths are covered.
3. Turn one of your useless meetings into a code review session. Each week/sprint, one Very Important Code section is presented by the developer that works on it most or that last changed it. This helps the whole team learn the code base, gets more eyes on the important stuff regularly, and enforces not just a consistent style but a consistent approach to solving and documenting problems.
4. PR (and the github PR approval stuff or its equivalent for you) should be streamlined but preserved. Do have a second person approve changes before merging, just to double check that tests have finished and passed and all that. If your team is so busy that no one ever approves PRs then allow self-approval and be done with it. This will make regular code review very important for security and stability, since any dev could be misbehaving unseen, but these are the trade-offs you make when burning out your team is more important than quality.