Customization/Power vs Modularity and Team Work « TuringBank

Knowing where to draw the line between full customization/power and when to sacrifice that for better teamwork and ease of understanding code.  For example, in your tools – Vim, debuggers, profilers etc – the tools of your craft, stuff only you will be using to get your work done, by all means make it as customized/powerful as you like.  However, this is not the best approach for code.  When you start building larger things, you need to take the dynamics of production into consideration:  how easy is it for everyone else to get up to speed/working, how easy is the code to extend/modify etc.  As machines get faster/more powerful we can almost begin to abstract them away.  We can now just focus on computation and the problems we're trying to solve. Share this: Print Email Facebook