No-Bullshit Guide into Building Software Don’t listen to JavaScript developers! bullshit / ˈ b ʊ l ʃɪ t/ Unnecessary steps and practices which add little to no value to the overall process The Software Process meetings • Sprint planning & Guesstimations • Daily standups • Review & Retrospection • PM says: “We need devs on this call” PM-ing the right way • Write better specs • Prioritize your features! • Buffer all comms for devs • Prioritize your features! • Regard guesstimations as optimistic • Know your product better than devs • Prioritize your features! How devs build shit • We’ll do it later (we wont) • We need this (YAGNI) • We do functional programming, fuck SOLID • Better architecture (overengineering) • New tech is better than everything we ever had! (it’s not) • OMG Microservices!!1! (I read an article) • sCaLaBiLiTy (facebook meta does this) Building shit the right way • Old tech is shark, not dinosaur • Most problems are already solved, your framework just did it too late • Patterns exist for a reason • You don’t have a scale problem (until you do) • Monoliths > Microservices * * Unless you absolutely need microservices