74 karma · joined November 25, 2022
The experience of this tooling was make a change and it was in production. It was incredibly simple and productive to work with given the needs of the time.
There was also plenty of opportunities to make a mess, but I don't think that has really changed.
Learning was not difficult, you just had to be prepared to spend time and some money on books and courses.
It is not a tooling set you would want to go back to for a bunch of different reasons but it worked well for the time.
The collective 'we' developed nations have our own set of problems, but broadly speaking from time to time self correct away from polarisation to hopefully enough of a degree.
A unique kind of leadership needs to be allowed to grow in America to stear a less polarised course.
Databases store stuff really well. If get to the level of needing to configure storage for different tiers of access they can do that, it just takes a bit of work. Of course if your blob data is stored in tables that have OLTP data in them, then you have a bit of work to do to separate it out.
This is speaking from recent experience of having to manage random blobs of sensitive data in s3 buckets that engineers have created rather than bothering to put in the main application data store.
Maybe it is atonement of some sort.
So having a balanced prioritisation approach would seem to be pretty important.
Back in the day I even had an email thread with Ryan Dancy about making software tooling based on the OGL, which was pretty non-committal and discouraged me from proceeding with any efforts.
Extending use cases to cover behaviours that were not covered by the original software is where things get exciting. You will end up with a hodge podge of systems & processes that try to implement multi-step work flows and deal with failures through manual or equally complex automated methods to compensate.
Generally most industries are pretty terrible at evolving the solutions they have or completely replacing them. So you will see a multi-generational set of systems that are in place to provide an acceptably current set of behaviours.
This situation can arise due to varying commercial pressures, however Developer and Engineer's inability to communicate what the system currently does and what is easy and hard to change in no small way contributes to following paths that result in poor system outcomes over the lifetimeof systems.
https://www.nsw.gov.au/environment-land-and-water/water-rest...
Depending on how you count, defense industry could be 3.5 mil employees.
https://siteselection.com/issues/2012/sep/sas-military-econo....