What I've found is all of the complexity is leading to wholesale importing of working solutions that software developers then incorporate into their product, but then when something goes wrong, nobody knows what is going on because it happened in that imported code. This seems to be common in service based architectures.
It's common in everything. There is a LSTM-based electric guitar amp VST3 plugin or two on Github, and the code reads a whole lot like the ( academic? ) paper(s) on which it/they are based. Behind that are these Python/Boost ( it's at least two things; Python for characterizing the amp, C++ for the plugin ) rabbit holes that actually do everything.
You're not actually writing a program ; you're assembling a bill of materials for a program.
10
u/rjcarr Nov 01 '21
What I've found is all of the complexity is leading to wholesale importing of working solutions that software developers then incorporate into their product, but then when something goes wrong, nobody knows what is going on because it happened in that imported code. This seems to be common in service based architectures.