Missouri also has a governor that vowed criminal prosecution for a newspaper reporter who discovered “View Source” on a state website revealed teachers social security numbers [1]. This went on for months.
Even if a white hat had discovered flaws in Jackson County, they’d have to be insane to do anything with that information.
Yea, just to be clear though: Asahi Linux still works pretty well. My system boots near instantly; wifi, mouse, keyboard work fine. Its enough where I can easily use my M2+linux as my daily driver.
This article is addressing misleading comments that made it sound like everything for apple silicon was merged into upstream kernels. It's not. You're still going to need to use Asahi kernels and userspace bits for a while.
Sad, but I would occasionally use my "unlimited" PTO to take a week off and just get work done. Most of the pain started when we transitioned to a sprints from a lack of process. In theory, this was to make things faster (which actually most of the reasons we were so slow was unrelated to process). My week suddenly went from getting things done to:
- 60 minute meetings fighting over whether tickets were 3 or 5 story points
- turning our entire process into some kind of perverse waterfall method where stories involved days of prep work defining every step so that we could accurately estimate story points (I thought this was the opposite of agile?)
- offers to "help" from project managers and managers when things took longer than expected - this help took the form of additional meetings.
- absolute inflexibility over my noon standup. I could be in the deepest of zones and people would literally slack repeatedly until you showed up for that thing
Cue the "oh you were doing <X> wrong!!" people. Modern software practice sucks. Its fine for small bugs and very well defined tasks. Outside of that it is just interruptions, interruptions, interruptions.
I also ended up just quitting. New place is better, but still in many ways the same. At least here I don't have comparisons made to my old days of the pre-software-process productivity.
100%. I worked at a company that really went in hard on Agilent Vee for hardware testing in the early 2000's. Absolutely a thing where a manager saw a "Hello World"-like demo and was so impressed that they went 100% full buy in.
Besides the obvious UI issues (like the fact that you couldn't really zoom out, you could just pan around your code), we had a bunch of engineers that still needed to do things like "get the three largest values from this array" and it just turned into the most ridiculous bubble-sort implementation you've ever seen.
Its pretty hilarious seeing some of the old screenshots now [1].
Anyways, I think it will always be really easy to sell some simple demos on low-code/no-code, but then the second you need something slightly outside the eco-system it just turns into a substandard mess that doesn't work well with source-control (or diffs) and in general is just harder than the code-full solution.
I worked for a company that used A/B testing to justify call-to-cancel; makes me angry every time I think about it. I guess that's one of the tricky things about A/B testing - it is easy to measure that call-to-cancel decreases customer churn, not so easy to measure the number of people that will never sign up for your service or the number of customers that do churn and swear to never use you again.
Even if a white hat had discovered flaws in Jackson County, they’d have to be insane to do anything with that information.
[1] https://missouriindependent.com/2021/10/14/missouri-governor...