14 ms·
Maybe, but who's going to build that system when 110% of engineering is building customer features. Much more likely that a ) engineering doesn't want to touch
by pragmatic 6y ago
Maybe, but who's going to build that system when 110% of engineering is building customer features.
Much more likely that a ) engineering doesn't want to touch it ( for obvious reasons so b) sales/sales support maintains this in Excel or worse...
- cameronbrown 6y agoNothing wrong with maintaining in Excel as long as a computer system can serve that data. At that point it's just a fancy lookup table. Engineering != programming. People forget that choosing not to code is also an option.
- dannyw 6y agoOne of the companies I worked for got acquired. The CTO of the bigger company decided to personally lead a large rewrite, including: • replacing our Wordpress blog with something custom written, including building our own database migrator (you could manually data entry our few blog posts by copy and paste) • Replace our Google Sheets based asset tracking with an overengineered backend. The frontend was never built due to a lack of FE and design resources and everyone continued to use Google Sheets. • choose to delete some old sections of our app that still used jQuery, angering vocal customers.