175 karma · joined August 12, 2025
Sounds like business as usual to me, with a little sensationalization.
Charging hundreds of thousands if not millions per year for very basic functionality is what is "killing" b2b SaaS.
To give an idea, this is a proprietary system that is extendable via scripts, but all of the artifacts are exported via XML files where script source is escaped into one XML tag within the metadata. Same with presentation layers, the actual view XML is escaped into one line within one attribute of the metadata file. The "view" xml may be thousands of lines but it is escaped into a single like of the export file so any change at all just shows that line as being changed in a diff. Attempts at extracting that data and unescaping it even seem to present problems because when the XML is exported often times the attributes within the schema are exported in a different order, etc.
It doesn't write the code for me, but I talk to it like it is a personal technical consultant on this product and it has been very helpful.
If I put corn in a pond to hunt waterfowl, I go to jail.
If I put pond in the corn, I can charge $10k+/yr to hunt my personal duck park.
Of course the advice in OP is going to be relative, but it’s not a bad rule of thumb to have a good sense of what your immediate does, how they think, what metrics they value, etc. If not for your own advancement- keeping immediate leadership off tilt can greatly increase QOL, or vice-versa. I personally would love to have leadership above me that I think "damn, I'd like to be a little more like that guy" but in almost 20 years of being in the workforce, including military and the likes, that kind of leadership has been hard to come by.
Preceding wall of text to explain how hard the realization hit, for practically the first time in my life, when stuff started going crazy in the feds: "damn... I really could be ~6mo away from losing it all." As many of you know, the market was and is ridiculous. Thankfully a few years back, even when I "knew" I didn't need it, I finished my BS:CS before my GI Bill dried up. And then as another challenge took the Security+ exam before I started applying for a job in the private sector. A lot of people in this industry like to say none of that matters-- which might certainly be true, but I can say without a doubt that those pieces of paper are the main reason I was about to get out of the hole I was in. I'd rather not be in that position ever again, but I'd like to be well prepared "on paper" if I am.
Absolute positioning wasn't available until CSS2 in 1998. This is just a table with crafty use of align, valign, colspan, and rowspan.
Better yet- why are there orgs that accept this behavior? I know mine is far from it, as they should be.
Once you pull that prey drive out of a working dog and associate it with something such as a ball, there's no greater satisfaction this planet than doing the thing for that animal. It usually works better as a reward for what we're doing, is more instant, but also it can be deadly for a dog to eat food when they're at working-level activity.
The foundations of card magic are certainly out there, and for me knowing how the fundamental slights work make it that much more magical to see it performed at such a level. No different than having played a sport makes spectating that much more interesting and appreciable.
I think some of what I'm trying to portray is that this should be the incentive. Either do it or you don't have a customer. Yet, the customers don't hold this standard.
As an individual consumer, if I don't get what I pay for, I return it or can even submit a charge-back. Is it not irresponsible of business management to not do the same?
Enterprise software licensing, support contracts, and technical account managers (TAMs) often run into hundreds of thousands or millions annually per organization. Yet, in practice, support tickets go unresolved or ignored, even for large clients.
The software quality of our most expensive products is extremely poor and unreliable, almost across the board. Many products suffer from bugs, outdated features, or incompatibility issues that disrupt operations. In development roles, this means wasted time on workarounds, custom patches, or integrations that shouldn't be necessary. For a non-small organization, this scales up to significant productivity losses and hidden costs in overhead.
These companies actively alienate us, the customer, through their business practices. Changes like aggressive licensing shifts (e.g., moving from per-core to per-employee models) force reevaluations and migrations and eroding trust (i.e. Oracle with Java, VMWare fiasco). This isn't isolated—it's a pattern where short-term revenue grabs risk long-term relationships, yet companies seem unfazed.
This jacks the entire ecosystem up. These practices stifle innovation by locking customers into suboptimal tools, increase overall IT spend industry-wide, and contribute to employee burnout in dev and ops teams.
It seems like it’s a race to the bottom. The strategy is to create an ecosystem with high switching costs and vendor lock-in. It just doesn’t seem sustainable, yet- it keeps truckin’ along.
With hundreds to thousands of people spamming every job posting under the sun the second it is posted, just getting your credentials read by a human is a major barrier right now that career fairs help alleviate.
What's old is new again. Get those soft skills warmed up and go out and shake hands.