3 ms·
At my previous job, my assignment was to rebuild a front-end 10 years in the making; the company had lost (idk if they fired him or he moved on, I suspect the l
by Cthulhu_ 3y ago
At my previous job, my assignment was to rebuild a front-end 10 years in the making; the company had lost (idk if they fired him or he moved on, I suspect the latter as he was one of the founders) their previous developer, who was both not a very good developer and very productive.
But yeah, when I joined that software had been built for over 8 years, using technology and practices from the 2000s (think AJAX where X is XML, a PHP back-end that concatenaded XML tags, and a Dojo front-end), and my goal was to rebuild it.
I spent 2.5 years there, using Go as back-end so it's all integrated (one issue was that the PHP runtime they had at customers couldn't be updated because RHEL didn't have a newer version in the repos), React as front-end, etc etc. But there was just too much functionality to rebuild, and they didn't / couldn't find other people to hire (until I quit, because of course).
In hindsight, while PHP wasn't really my thing, I should've focused on improving the existing codebase and then only incrementally improve and replace things in-place. I mean at the same time, I knew a full rebuild of that was a Bad Idea, but that's what they wanted and I wanted to do stuff in Go as well so I didn't challenge it too hard.
But yeah, I could've easily made the back-end twice as fast with at worst a week or two of work; half the back-end's processing time and memory usage was because they took that concatenated XML, parsed it, and converted it into JSON. Because at some point the previous author realized JSON is the new cool kid on the block.
- ChrisMarshallNY 3y agoWell, I wrote both the backend (PHP), and the frontend (Swift). The backend is too complicated, because I originally wrote it as a general-purpose server, and it is now specific, but it works fine. No need to rewrite, although I’d love to. The frontend had been “accreting” features, because it was really a high-quality prototype. When we had nailed down the functionality, I knew this was a ball of mud that I didn’t want to maintain, so I factored the business logic into a standalone library, and most of the work has been on the “chrome” for the app. It’s not-simple, but much more straightforward than the previous version. Also, this time, we brought in a professional designer, and have been applying style from the beginning.