Ask HN: Do you mostly program in a non-FP or non-OO style? Why?
Primarily a Python and Go programmer.<p>OO: Only rarely, and only where it really makes sense. Most programs I work on are not complex enough to justify the overhead (boilerplate, cognitive).<p>FP: I use this more, but again, only when I can really justify the added cognitive overhead.<p>You&#x27;ll notice the two references to cognitive overhead: I have adapted the &quot;write for a 6th grade level&quot; idiom into programming. I want as many people to be able to pick up the code and modify it as possibly can. I work with everything from interns to decades plus veterans, and my code must be grok-able by both. Pure FP tends to confuse interns, and veterans have a tendency to hate the layers and layers of indirection and abstraction OO brings into a program.<p>Normal and boring old &quot;an imperative main method with functions&quot; tends to be the least offensive and most understandable to all parties. Compromise r fun.