Not to say monoliths are all “bad” but you only have ONE point of failure.
Issue with the website (SSL, availability, etc)? Mobile app won’t work.
API / DB / Integration down? Users will see a UI-unfriendly error. Plus, proper caching can hide the problem while fixing.
RANT TIME
I legit HATE mobile apps (built via native or hybrid framework) that just have a native and a webview for content. If I wanted that, I’d just visit the website.
If your website is a monolith, make an API and gradually move each webpage over to a hybrid framework…
One codebase is much easier to maintain. Think of all the new features you’ll be able to roll out faster and with fewer hiccups! Modernization is simple; you just need to work in iterations.
Many new developers think waterfall is a good idea
They look at Agile and think, "Wouldn't it be better if we just planned everything up front?"
"Why don't we just make sure we get it right the first time?"
There's a whole world of suffering they've never experienced
@svpino Correlation, not causation. Software engineering requires more context than other fields and AI will bulldoze through other fields before SWE. Layoffs happened because of hiring mismanagement
I’ve seen more and more companies pushing for a return to the office. I wonder why?
Are people more productive in the office or what’s the reason?
Personally, I enjoy working remotely, and I can hardly see myself going back to the office.