this post was submitted on 21 Feb 2025
70 points (88.0% liked)
Technology
63082 readers
4585 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You know when users complain about the lingering bugs, unexpected slow downs, and slow delivery of new features caused by tech debt (even though they don't know that). That's them caring about your stack, whether they know it or not.
Banks.
Do you know why banks are still running COBOL on new, old architecture, IBM mainframes? Sure, it's in part due to risk aversion, ignorance and inertia. But it's also because, if in the end the result is the same, then the tech stack doesn't matter.
Very few people are tech fanatics, most people want results. They care when the products don't work. They don't care how you fix it as long as you fix it in a reasonable manner, within an acceptable timeframe at an affordable price.
Doesn't matter if the customer is a billion dollars bank or a social network. Debbie thinks javascript is when the barista puts her initials on her latte and rust is something to fear when it shows up under her car. Too many devs forget this.
In contrast, banks all universally moved to single page apps lately, and every one of them sucks. Some suck more (we don't support you having more than one tab open while you are researching stocks) and some suck less (what is the back button for, anyway? Just ignore it). But they all suck.
And yes, users do care about using shitty stacks when they make shitty results.
If your users are aware and complaining about your tech stack, you failed as a Dev. The stack had nothing to do with it, its on you.
Edit: unless your customers are other devs, of course.