weimaraner_of_doom

Not as much as I used to, sadly. I don’t remember what the first thing I volunteered for was but I suspect I started doing it because I was asked. I volunteered a lot more when I worked at a company that encouraged community service and would give their employees time to do volunteer work during business hours.

Nano is the proper tool for this job.

Instructions: “Next, open the .config file in vim…”

Me:

The Germans were pissed when the American’s showed up with shotguns. Can you imagine the protests if they showed up with T. R.?

Gambling for schmucks.

And the options are still not great.

The circle of life.

I’m going to wager this is mostly an attempt to get more people into the Apple ecosystem. The more integrated the user is, the harder it is for them to get out.

I’ve worked with so many people who use their job to escape their marriage. That sucks. I love spending time with my wife. I wish we got to go do things like we used to.

Jimmy came in first place. What a loser! – The Kid in Second Place

Just give me your ID bro. It’s totally to protect the kids bro.

Forgot “Glorified Pump-&-Dump scheme” (NFT’s)

The average corporate executive has no idea just how much of their organizations resources are dedicated to “churn.” By “churn” I mean the flurry of activity that provides the illusion of productivity while actually producing very little.

I worked for one company that liked to move dev teams around to different platforms to [theoretically] increase productivity around major feature releases.

Pretty much anyone who has been in software engineering for more than a week knows that reassigning devs to a project that they’re unfamiliar with and only plan to work on for a short time will actually slow development down, not speed it up. To make matters worse, some of these teams had very poor practices. I’m trying to be charitable with my words.

The immediate result was that the number of bugs and defects skyrocketed, dramatically increasing the workload for QA and the core dev team. Management’s response was to pile a bunch of unnecessary requirements that had to be met before a PR could be merged. This failed to produce a meaningful reduction in defects while bringing development almost to a halt.

One of the directions I gave to the core team was that when they worked a defect ticket, in addition to fixing the defect, they needed to perform a root cause analysis, link the defect ticket in Jira to the ticket that introduced the defect, and write the root cause analysis in the comments.

If anyone from the product team had bothered to review the defect tickets, they would have found that a small number of individuals produced 90% of the defects. Instead, they carried on with the unfortunately common notion that software engineers are just overpaid monkeys and that pretty much anyone can bang out web apps.

The current views on “AI” are often a continuation along that line of thought. The value of Institutional knowledge is basically impossible to quantify so it gets ignored altogether. I honestly don’t know what impact this will all have on the average organization. I do think that if someone has staked their entire organizations future on an LLM, they’re in for a bad time.