Are We in the Middle of a Programming Bubble?

may I ask what domain you are working in? Can you give some examples of how you've slipped in some programming knowledge into other job tasks? I love to hear people's anecdotal problem/solution approaches. Was the programming side of it actually slipping in some VBA/chrome extension/javascript or was it more of just an 'analytical' approach taken to a business decision.

I use programming extensively as a problem solving tool, for things like data analysis, modeling, automation of experiments, and prototyping. Almost all modern equipment is electronic and computerized. To be capable of rolling out an MVP on my own, I program.

You will rarely see my computer without a Jupyter notebook on the desktop. ;-)

In addition to working in a computerized field, program code is just a super powerful way to express ideas. And the disciplines of good programming practices (yes, learn them) provide ways to organize the innards of complex things, so they actually have a fighting chance of working and being right. Plus, it's fun.

People who work as full time programmers may make more money than me, but I'm not sure that I can do their jobs. When thinking of any profession, a person should not only look at the cool, fun stuff, or the money, but what the actual daily grind looks like, because that's what you have to survive.

Neither the SAG nor the AMA are unions in the traditional sense. In many ways, the AMA actively works against worker quality of life (consider that the horrible conditions for med students/residents and the high suicide rate among MDs) to artificially reduce supply.

>Why do doctors form a union to increase wages, if as you say, they would be better off without it?

The AMA is mainly a lobbying organization, not a union. Since a significant percentage of doctors are in private practices or small practices, they don't have representation with the government. So sure, the AMA does collectively bargain with the US Government. But by that same token, since 53% of MDs are self employed, the AMA can't do "normal" union things like set wages, because there's no one to bargain with except the doctors themselves.

And interestingly, the AMA actually admitted that its intentional supply-reduction is hurting the medical industry as a whole. To answer your question, "because they thought it would be better". But in hindsight, they probably weren't.

The Web bleeped that up. Everyone hoped HTML5 would fill in the CRUD gaps, but it didn't. Thus, we still waste lots of time because the Web was not designed for CRUD and shoehorning CRUD into it is like backing an 18-wheeler truck into a parking slot. In the old days you just pointed your sadan steering wheel into the parking slot and DONE. JavaScript-centric UI's have proven too fragile. It's great for eye-candy, but not reliability.

Yes, I know there are some good Web stacks out there that can mostly overcome this, but they are rare and/or hard for managers to recognize. Their urge is to "keep up with the Joneses" even if the Joneses are doing something that doesn't help typical CRUD. Nobody can tell fads from good stuff.

One good invention and/or new standard could wipe out half of CRUD coders. I propose the industry experiment with a standard GUI Markup Language designed to do desktop-ish things out of the box and be more stateful. Mobile-friendly UI's are nice for mobile devices, but not good for regular office productivity. Desktops and mice still rule work.

In the 1980s there was a lot of "foundational research" (poorly re-inventing the wheel) for microcomputer people who did not know about the work done on large computers in the 1960s. Move fast and break things was also very much a thing for microcomputer manufacturers and most microcomputer software vendors. Look at how many releases software packages went through, and at what rate.