This is one of the major drawbacks to ORMs imo (though it’s not necessarily the ORMs fault). People think domain and data models are the same but they most definitely are not.
The most recent episode of the podcast “Search Engine” explored the cost of war and pretty much said exactly what you did. Besides the obvious war is bad, it’s so unfortunate we are passing on the cost to future generations. And for what?
I find testing terminology very confusing and inconsistent. Personally, I prefer tests that cover multiple components. Is that an integration test because you test multiple components? What if you system is designed in such a way that these tests are _fast_ because the data access is abstracted away and you can use in memory repositories instead of hitting the database?
While it's truly a great ongoing effort and I am grateful to all the contributors, it's not nearly complete. You may think you're using the correct type until, surprise, you are not.
Hi! I bring over a decade of experience as a software engineer. I spent a solid portion of that time as a backend engineer building out APIs in Django. In my current position, I have built upon those skills and acquired plenty of new ones as a platform engineer. A significant part of my role has involved evolving and optimizing our infrastructure (AWS) with a focus on cost savings and maintainability with improved Terraform practices. In addition, I have built and improved multiple internal libraries and services to make our engineers' lives easier. In my next role, I'm looking to leverage these skills and help advance a team to the next level.