But with different levels of quality control and potentially ingredients - not trying to dimmenish white labels, they serve a role, but its always been absurd to me that just because something is made in the same factory that those products are identical - a few items might be - but you can taste white label and brand name side by side and they taste different even if they have the same manufacturing marks and have different failure rates (and sometimes the white label even tastes better!)

https://youtu.be/yA5lujNlkn8

Destroy abstractions

The reality is, if you have an abstraction layer and one implementation of it, you dont need that abstraction layer

People will complain, “oh but think about the refactor if we have to change vendors/etc” but i have yet to ever switch vendors/api/etc and not had to completely rethink the abstraction layer

Just get rid of it, it will be easier, less code, more precise, and in the long run you’ll cargo cult less

Just write the code for the things you have, and if things change, yup then things will change - to anticipate future changes and upfront the work for the unknown only to then have to make more changes once those real changes eventually arrive and dont match your old predictions is just more work and more confusion

NASA or NSA?

I think java has enough momentum that it will join in the perpetual pantheon of languages with FORTRAN and C - however with that said, learning Go changed how I write Java for the better, I was able to do this within my java job after convincing the team that a small but neccisarry but not critical side project could be done in Go to test it out - I had a blast learning and writing it, even though ultimately the dynamics of my company kept us in Java