Articles from TnL
I have incepted a pattern at a few big tech companies that my friends worked at after they did some side stuff with me. It makes your life testing against a database way easier. You'll never look back once you've got it going.
In computing performance, direct instructions are fastest, but are difficult to program. In code, indirect seems elegant, but just ruins cognitive ability. The balance should lean towards directness. Indirection may not be bad, but it's only good in small quantities.
Good fences make good neighbors. This is the most important concept in cooperation and coordination of work. Ostensibly I'm talking about software engineering, but it's also true of everything in life. Everything.
Everyone in business talks about "creating value" in various contexts, but what the hell does that mean? Well, there are two kinds, and you're either creating it directly or not, and with others or not. It can be complicated, but ultimately we can focus on ourselves and understand it all just fine.
Some data people think they're just software engineers with a different focus, while some software engineers think data people have no idea how to code at all, and all of this is both true and not and silly. The confusion needs to stop, because working together is hard enough without the egos and title gore and miscommunications.