data-plumbing-for-corporations tends to be able to be done in a way that’s easily testable, but also most people get paid to bolt on new shit onto old shit and spending time on “done” code is discouraged so once they fall behind on writing tests while developing the new shit those tests will never be written.
and bad developers that won’t write tests no matter what actually do exist.
i’ve only read about rust, but is there a way to influence those automatic implementations?
equality for example could be that somethings literally point to the same thing in memory, or it could be that two structs have only values that are equal to each other
Strings are Objects, Doubles are Objects (that are than unboxed into primutives doubles)…
the “what” is interesting on interfaces or when you generate documentation with some tool like sphinx or javadoc.
the “why” is interesting when you are somewhere inside a class or function and do something in a “strange” way, to work around a quirk in the codebase or something like that, or when you employ optimizations that make the code harder to read or atleast less obvious why somethings are done.
good Tester.
If something stupid can be done, it will be done.
for receipts and such paperless ngx is good. that won’t track your repairs or inform of you of likely maintenance problems, but that and a spread sheet sounds like a good start.
there is no “undefined” in java. this would either be a map containing the key value pair (“name”, null) or it would be mapped to an object of some class with an attribute “name” which can hold a null value. in any case {} wont equal {“name”:null}.
look into local dns servers if you want multiple machines to use your local domains if you only want a single windows or linux (and probably mac) computer to use the domain to access a specific local ip an entry in your etc/hosts file would be enough
https://github.com/docker-mailserver/docker-mailserver should be able to do it.
if i remember this in 6 weeks i’ll check the setup at work.
because no one follows the damn guide and “scrum” is done so managers can claim the company can work “agile”, because customers dont want “not agile”, customers also dont want to participate in the way it would be necessary for a project thats supposed to follow the scrum guide. that also sounded good for people looking for a new job so hr wants to put that into job descriptions and now everything is scrum and agile and i still have to sneak in refactorings or have to fight to get time to work on our fricking ci pipeline or need to conspire with QA to get them time to work on test automation, because screw the notion that decisions should be done by the people doing the work.
screw “scrum”, and the word “agile” should never have been taught to anyone claiming to be a “manager”, we don’t need managers we need people helping us getting the tools we need and trust that what we do, we do to deliver better solutions and helping us to fascilate constructive exchanges with customers.