baw

I have watched both sides of the discussion (yes, you @cmuratori). Two thoughts I want to share: 1. Clean Code != (OOP & SOLID). Clean code == writing code that is respectful of your coworkers' time. 2. Your work domains are different and require different solutions. Respectful code is different for each domain. Thoughts below: Writing "a clean code" is not the same as following OOP. Writing clean code is not the same as following SOLID. If I could point any criticism, I wish the Clean Code book was just about "clean code," and wouldn't touch specifically on OOP or SOLID. The reason is that even if part of those two practices are germaine to the question, Clean Code is not not bound by the whole of it. It's just about writing software of any sort in a way that is respectful of your coworkers' time. It could be done in procedural, functional, or object-oriented programming. The last point is: your domains are so different. Bob has worked on enterprise software, while Casey worked on game engines. It is completely absurd to me that anyone in the world would ever ever dismiss a whole book over the fact that it doesn't work on his domain; just as much, it's completely absurd for someone to ever think writing software in OOP, and following the SOLID principles, will give them the real-time performance necessary to write a game engine! There is no way you can reconcile those practices with the way interpreters/compilers work today, and it is a foolish waste of human hours to be continuously discussing about this like people have been for the past 17 years since this book hit the shelves. Why can't people see this is a domain-driven issue, not a performance discussion? Casey, I want to watch you eek every gram of performance out of the computer, and I want to watch Bob teach people write software in a respectful manner. But please, make it very clear that your views are domain-specific, and if you try those techniques in another domain, you might ruin the day of a whole bunch of people. The amount of bike-shedding I had to deal with in day-to-day because someone was shit-talking Clean Code, worring about performance while copying 8GB or RAM maps of a parsed JSON with 5 cores dying and the 6th a knife's edge away from harakiri is insane, and it starts when people look too much at engineering and too little at what the actual f*** they're doing!

Today, we are proud to announce that Cfx.re — the team behind the biggest Rockstar roleplay and creator communities, FiveM and RedM — are now officially a part of Rockstar Games: rsg.ms/db4ed99

@CancelBaw @onebawbag