Software development requires servant leaders
This is the sort of article that makes me imagine a dialogue between a senior software engineer and a newb developer that goes something like this:<p>Newb: Hey man, I think for this project I&#x27;ll write my own SQL datastore from scratch. I&#x27;ve looked at a bunch of them and my project, which is basically an inventory management system, is such a special snowflake that it needs its own datastore.<p>Senior: That would be insane. Never do that. Use what&#x27;s already out there, and is tried and tested. In fact, just use postgres and make it work.<p>Newb: Aw, ok. I was so much more excited about writing a new SQL datastore than I was about the actual project it&#x27;s for, but sure, I&#x27;ll just use postgres. <i>starts to walk away...</i><p>Senior: Hold up a sec before you go, I want to run something by you. Because our discipline, which is basically a team of people who are hired to build things on a schedule, is such a special snowflake, I&#x27;ve invented this totally new way of thinking about work, and of organizing a team and leading it, and there&#x27;s a bunch of new terminology and I have some cool diagrams... I&#x27;m lobbying that we all switch to this at the end of the month.