dark_stang

I joined a team years ago where everyone would catch exceptions then throw a different exception in the catch, swallowing the original. Sometimes these were nested many layers. Troubleshooting was a nightmare.

I spent a week deleting all of them and told everybody that "try" was now a forbidden word outside of entry points.

As wraithcoop suggested, you can install additional software like rectangle to do the job. But why is that necessary in 2023? Window snapping has existed forever on Linux DEs and Windows since Vista.

"You're ~~holding~~ plugging it in wrong."

I'm amazed at how many professionals use Macs because Apple seems to hate power users. I had to use a Mac briefly recently and was amazed to find they still don't have window snapping.

It also had no idea what to do with my monitor, couldn't even detect the correct resolution. I'm guessing if I had bought a $3000 Apple monitor it would have worked immediately. But had to dive into "advanced settings" just to set the correct resolution.

If they wanted to make browsers less secure, they would do so in much more obvious ways.

The new proposal demands browsers automatically trust government created root certificates. That means any EU government can do a man-in-the-middle attack on any end user running that web browser, even users in other countries. There is no reason to do that other than to spy on people or to manipulate the content that they're viewing.

If any government, or company for that matter, wants to make their own root cert and deploy it to all their users/machines they can already do that easily. A lot of companies that work with sensitive data already do this, and some companies (ex: symantec) provide solutions to do it very easily, so the IT team can see everything the users are doing.

If you want something scary, go with a shirt that's a stack trace about an error on line 9376.

If you want something funny, look at deranged as possible with a shirt that says "stakeholder" or "end user".

Sometimes you have to do something this. Like when working with a horribly designed legacy database that put property values in a child table and you need to map those to actual properties in your API model.

Sometimes you get the opposite too. Like an 8pm slack message stating the head of engineering has "decided to step down effective immediately" (aka: forced to resign). Which is a nice surprise cause you had a meeting booked with them for tomorrow.