Wow. Just wow. I sure hope they get something more out of that, because 1200 dollars for fucking up who knows how many shitty chinese android boxes is worse than doing it for free. From a related article from TF:

Bug bounties and hackathons are notorious for being the coding equivalent of working for exposure. These are inherently cost savings programs so that companies don’t feel like they need to purchase these assets at market price.

Honestly the “old web” was also a hellscape for accessibility.

There’s been a lot more advances for accessibility in the last 5 years because of ADA lawsuits being successful against large companies with websites, so it’s seen as a liability.

In my personal experience in general this has been a big impetus for companies to start take WCAG seriously. However in practice a lot of this is box checking because it’s expensive and complicated.

A lot of our newer contracts have had explicit terms for various levels of accessibility, but this has lead to a problem in the sense that accessibility is something that is designed, and in practice the company has a very hard time changing it’s SDLC in most teams. So in effect the expectation from higher ups is that it’s a magic wand, these kinds of top down initiatives fail because they’re often just having people internally rewrite a11y tutorials or act as consultants to projects they know don’t have the resources to actually become accessible.

SDLC can be made to be inefficient to maximize billable hours, but that doesn’t mean the software is inherently badly architected. It could just have a lot of unnecessary boilerplate that you could optimize out, but it’s soooooo hard to get tech debt prioritized on the road map.

Killing you own velocity can be done intelligently, it’s just that most teams aren’t killing their own velocity because they’re competent, they’re doing it because they’re incompetent.

And note this is one instance of task, imagine a team of people all using your code to do the task, and you get a quicker ROI or you can multiply dev time by people

In practice, is only quicker ROI if your maintenance plan is nonexistent.

Absolutely not lol.

If SOLID is causing you performance problems, it’s likely completely solvable.

Most companies throwing out shitty software have engineers who couldn’t tell you what SOLID is without looking it up.

Most people who use this line of reasoning don’t have an actual understanding of how often patterns are applied or misapplied in the industry and why.

SOLID might be a bottle neck for software that needs to be real-time compliant with stable jitter and ultra-low latency, the vast majority of apps are just spaghetti code.

It’s windows host because it has the unique property of leaking to higher levels of abstraction and leaking to lower levels of abstraction, which is a technological feat that can only come from Microsoft.

Factory factory…n is literally just creating an OOP closure for when your language doesn’t support first class functions, closures and/or currying.

Also metaprogramming and abstraction is literally the only way to actually manage and deal with the capriciousness of your stakeholders.

It’s not simple, because it’s literally not that simple. It’s Conway’s Law. That’s what being a programmer in the industry is. I run a platform team, and I get paid because I can organize and deal with technical risk and contingency better than anyone else at my company. You bet your ass I do metaprogramming.

Also my product itself is a factory factory factory. Users create processes to author content, author content, and that content is delivered to other users. All in the same system. Managing complexity is extremely important if you want to work on interesting things.

“And this is the way everyone is doing it now? Everyone is using a general-purpose tool-building factory factory factory now, whenever they need a hammer?”

I’ve had this exact conversation with a programmer who was retiring. He was complaining that I ask too much because I told him that he needed a more generic way to represent the logic that encodes how our end-users traverse the content that our authoring users create and manage. He literally said something to the effect of the above quote to me, but as complaining contempt.

The business explicitly doesn’t want to spend money crafting individual code bases and products and unique logic. Our system lives and dies by our ability to service our internal clients and meet their needs in a dynamic manner. We need manage each factory layer carefully because very often different clients want two different things at two different times, and so each decision needs to be encoded in a way that allows us to make future platform changes without having to sell the business on refactors.

Sure you’ll run into people who overuse things when it could be simpler from the business perspective. But the reality is that most programmers in the industry have never stepped foot into a well run shop. Most programmers in the industry haven’t actually launched a product tip to tail.

It’s very easy to criticize patterns when you don’t actually have to use them, you’ve never seen them being used properly, and you don’t know how and when to implement them.

You don’t know how many times I’ve had to explain what two phase migration means and how to do them across multiple dependency links in the chain.