2 ms·
Witnessed a bit of the inverse or similar, dunno. Something written over many years and working very well, was to be "rewritten" as a web site/app/mobile thing.
by zo1 4y ago
Witnessed a bit of the inverse or similar, dunno. Something written over many years and working very well, was to be "rewritten" as a web site/app/mobile thing. And a "single" (wunder) dev pulled a miracle with a great POC demo where seemingly all needed functionality was almost there and working, all in a week which included many late nights according to them. This person had used the magical power of "angular" and all these "fancy" new things that wow-ed the leadership, that was so used to that "slow thick client" with it's outdated "C# compiled code".
Then after this transpired, it was up to the team to make all the APIs available to this new pretty-much-finished app and for it to be wired and polished into a "production ready" app. This process, along with all the unfinished, badly written, tech-debt ridden crap, took a year. Barely months in, simple features by this wunder-dev took weeks, incessant complaints about tech-debt by said dev, endless meetings and hand-wavy excuses about how "no we can't do it that way, it's not the angular way, and you don't know JS so shush!".
Countless angular upgrades and package updates with breaking changes, renderer this, web-component that, cordova that, do we support react, oh we didn't make it mobile friendly cause we can use native component libraries, oh crap we have multiple repos zomg now we need Lerna to compile our app, what about events let's use an event bus on the FE, and on and on, with no end in sight. It's years later and it's still being supported as if it's the holy grail, all while it continues dragging down actual feature dev. All this for a couple-dozen screens.