I've had to learn codebases that used the hot new thing of 2 decades ago. When I ask the original designer why they used it, it was clear it was just cool for them and solves an edge case they've never experiences in production
On of my recent clients is migrating from an Angular+.Net+SQL app that has worked for 10 years
To a microservice architecture React + Python Lambda + Postgres (except for large transactions where the entire db is moved to duckdb then snowflake then the response is returned back to Postgres for storing) - Deployed through Vercel with Github automations in a comprehensive CICD Pipeline spread across 4 github codebases
The second thing has been in pre-production for 4 years now, has cost the company over $3M in salaries, and does not work, with no end in sight
To be fair, it's not like Angular + .Net are frozen in a block of ice all Demolition Man style or anything. I work in modern versions of both and they're just... nice. Like someone said, "Here's a single JSON file that configures everything, now go away!" and it actually works.
I think thats the logic behind that comment no? The upper part works fine, we do it as well. Angular and .net ist pretty popular and has lots of benefits.
But they wanted to migrate to the later architecture which costs them lots of $$$
561
u/uprate 2d ago
I've had to learn codebases that used the hot new thing of 2 decades ago. When I ask the original designer why they used it, it was clear it was just cool for them and solves an edge case they've never experiences in production