Reminds me when I had to sort some payments FE-wise which was a very trivial array sort (there was at most 50 payments per page, nothing impactful performance-wise) on a json array which had a timestamp value, but CTO got involved with this triviality for some reason and started blabbering of how business logic had to be on the backend.
I literally had a working feature branch in 10 minutes, but it ended up being a 6 weeks job involving architects, devops, 3 backend engineers to have a microservice implemented in GO (which basically no backender knew) to handle those payments sorting. I'm not kidding.
I didn't got a promotion to staff engineer or architect few months later because CTO was fixated with "micro services experts" which basically consisted of anyone putting Go on their CV and having an AWS certification.
The guys hired were so sweet, they would spend like months repeating in the daily every day they were doing analysis and understanding our architecture, just to produce after 8 weeks a pdf of few pages with their in-depth analysis of Kafka vs RabbitMQ which was basically a summary of their landing pages lol.
I literally had a working feature branch in 10 minutes, but it ended up being a 6 weeks job involving architects, devops, 3 backend engineers to have a microservice implemented in GO (which basically no backender knew) to handle those payments sorting. I'm not kidding.
I didn't got a promotion to staff engineer or architect few months later because CTO was fixated with "micro services experts" which basically consisted of anyone putting Go on their CV and having an AWS certification.
The guys hired were so sweet, they would spend like months repeating in the daily every day they were doing analysis and understanding our architecture, just to produce after 8 weeks a pdf of few pages with their in-depth analysis of Kafka vs RabbitMQ which was basically a summary of their landing pages lol.
I love the information economy.