4 ms·
Wait! If there was a sane set of APIs and data interchange formats that was standard across the whole system, development would be the simplest part. It's beca
by fractallyte 6y ago
Wait! If there was a sane set of APIs and data interchange formats that was standard across the whole system, development would be the simplest part.
It's because they have to shoehorn their solution into a morass of garbage software, that this turned into such a complex task.
The real answer is to dump ALL these huge contractors, and their 'solutions', and make something new and better, with proper engineers directing the process.
Imagine if Deloitte had been contracted to 'invent' the Internet...
- NearAP 6y ago>>> with engineers directing the process This is usually not the solution. You have to understand the requirements/know your actual users. Engineers don’t necessarily do this well. They build with the latest tech but as you see in this example, the primary users are older people who can’t use latest tech
- Aeolun 6y ago> Engineers As far as I’ve seen there’s people that build first, and ask questions later, and the reverse. Only the latter are engineers.
- nitrogen 6y agoAgreed. This is not a No True Scotsman -- understanding true requirements is a fundamental attribute of engineering. If you aren't doing that, whatever you are doing it isn't engineering.
- flarg 6y agoHa ha I know, but it isn't like that. APIs are always written as REST but the systems serving those APIs are not REST so everyone starts off building lots of GET APIs and then progress steams to a halt because it's tough to write loads of APIs for the many different types of write data flows in most systems.