At my last job I had to endure 2-hour daily standups involving 120 people. Yes, I know that that's as far from actual agile as you can possibly get -- we still called it "agile".
I was at a funeral today. I swear the pastor's sermon was written by an LLM. Dude needs to go back to the traditional way: downloading sermons from religious websites.
I briefly wrote Blackberry apps circa 2010 (yes, I knew RIM was dying a quick death). The development process was insane: any module from the framework that you incorporated into your app had to be digitally signed by RIM servers every time you tried to compile your app and deploy it to a device, even if you had only made a one-line change to the code. On good days, this would make the compilation take 5-10 minutes; on bad days it would be upwards of an hour or never happen at all. Some wags had even set up a special website that would tell you whether the RIM servers were down or not (long gone now, of course). I got in the habit of making a large number of code changes before attempting to run and test stuff, which is obviously not the ideal way to do things but it certainly teaches you to be careful. It also make me think long and hard before including a new module into my code. As one example, for my GUI I needed to use trigonometry functions which were naturally (lol) part of one of the cryptography modules which took an especially long time to get signed. I ended up writing my own sin() function in Java just to avoid the hit of including that module.
The great part of this was that I always had a ready-made excuse whenever I felt like taking a long lunch or going shopping or going home early. "Sorry boss, the signing server is down" and I made damn sure they never knew about isthesigningserverdown.com. It also helped that it was Blackberry circa 2010 and it didn't make a shit bit of difference whether I got the app done or not.
Ironically enough, even most of the plantation "owners" didn't really own their plantations or slaves. They were typically massively in debt, usually to English bankers who were financing the loathsome operation to provide cheap raw material for their cotton factories. This is why the British government -- which had led the way in banning slavery in the British empire and using its navy to interdict the transatlantic slave trade -- was somehow on the side of the Confederacy during the Civil War.
I love programming and I did it as a job from 1995 to 2019. Absolutely the only time I enjoyed it was when I was left completely by myself to work entirely alone -- no managers, no designers, no junior developers, I did everything related to application production, deployment and maintenance completely by myself. These were also the only times I produced anything that was worth a shit and was actually used by people.
The dominant paradigm in software holds that it's fundamentally a team sport that requires an absolutely rigid division of labor. I know that this is not so and that in very many cases software is more like golf: just you and a heavy bag of clubs and a fuck ton of rough and sand traps.
I started working as a professional programmer in 1995. From the outset, I was pitching to clients how a GUI (thanks, Visual Basic 3!) would be so much easier for their employees to use than a command prompt. I find it very interesting how command prompts are still around 30 years later. I'm way more amazed by the continued existence of vinyl LPs, however.
I wrote mobile apps from 2005 to 2019, first on WinCE/Windows Mobile and then iOS. Briefly in 2010 I wrote a TV Guide-type app for Blackberry. Up to that point I had had nothing but contempt for Blackberry but that experience really changed my mind almost instantly. The keyboards on those devices were just so incredibly good, and even though the screens were tiny, the trackball was a fantastic pointing device that allowed pinpoint precision even on that tiny screen (cleaning the trackball was definitely disgusting but you didn't have to do it all that often). Under the hood those devices were really impressive as well; I don't think anybody appreciated how much memory they actually had and how fast the processors really were.
A minor weakness was that RIM chose 16-bit color for the displays early on, which gave a crappy look especially for videos (which were really too tiny to watch anyway). Halving your video RAM requirements maybe made sense in 2000 but it was a terrible decision just 18 months later (according to Moore, anyway). The major weakness, though, was the shitty development environment. The built-in controls provided by the framework were terrible, but the worst part was that any time you attempted to compile your app, each module incorporated into it had to be independently signed by RIM's servers. On a good day, the signing process would take 10-15 minutes, while on a slow day it would take upwards of an hour or maybe never happen at all. And this was even if you'd made a one-line change to your code.
RIP RIM, but I'd like to see the keyboards coming back. Also the trackwheels.
I had a teacher in high school (in Ohio) ask me if I was English. I don't sound even remotely English, I've just always generally spoken in complete sentences and occasionally use multi-syllable words.
My small company (~120 employees) got swallowed by a giant whale (rhymes with "Crisco") of a company like this. Except that everybody in the original small company got laid off six months later, and we had no assets whatsoever except for the "talent". Crisco even got stuck with the lease for our recently-renovated office and had to buy it out. Our C-suite got large stock awards when we were acquired but they all got dismissed, too. I have no fucking idea why it happened.
At my last job I had to endure 2-hour daily standups involving 120 people. Yes, I know that that's as far from actual agile as you can possibly get -- we still called it "agile".