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
What frustrates me most is that jetbrains had a winning formula
They made, imo, the best ide's, striking the balance between intuitive and useful without drifting too far into bloat
I just don't vibe with jetbrains wanting access to my code and data and how i use the ide itself - imagine if your hammer took a picture every time it was swung while tracking the swing trajectory and force and sent it to a thousand unknown people
its just fucking weird and its fucking weird that jetbrains presses this onto us - even as an opt-in its wierd
Even at it most innocent, and not the reality of trying to build the tool that ousts us out of our trade and craft, i still dont want some code cuck sitting in the corner of my periphery hyperventilating on every keystroke and variable name i make
No, but it is racist to assume that a person is an illegal immigrant based solely on their race.
Likewise, i think there is a deeper connection being made, that theres an assumption that an illegal immigrant is a bad person, and i also do not think that is a valid assumption.
To know if a person is a bad person, you have to know the person.
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
I'd counter part of that is that US law is based on common law, which is defined by prior court cases not just law - vs civil law which is only based on law.
There are issues with both of course, but, its common law that requires lawyers and knowledge of every court case and knowing what a judge in the 1800s thought a word means to win or lose a case.
I think the common law system of justice is deeply flawed and leads to this legalese where everything is vague and malleable with no certainty
A monthly playlist of about a 100 songs from small artists, not all of its to my taste, but there's definitely some diamonds in the rough and a lot of exposure to the unfamiliar
Its intentional that he doesn't say genocide, because its a powerful legal word and he believes its not his place to apply it - however his stance and his actions are clear - abundantly clear - latching onto this one point, that he explicitly has a rationale for is silly at best, and deceptive at worst.
~2% of the US population - getting closer to the famed 3.5%