Point being: lets not turn platitudes into rules:)
Exactly where the "point" at which efficiency drops sharply is certainly project-dependent, but thesash didn't claim that it was not: only that people make the mistake of not realizing that this is even a problem worth understanding and taking into consideration, much less a fundamental one that will likely affect their project.
I think the subject matter would be interesting here and would love to hear if there is anything you think I missed. Startup Weekend gets to be in a cool place to lead among tech entrepreneurs and I'm always to happy to advocate for those in our field.
Thanks for reading :)
I actually just forwarded it to one of my partners.
His reply: "Is that a hint? JK. Good read man."
Where to start...having open conversations with your developers is a great place to start. It turns out we love studying and talking about our field.
If you don't have ready access to developers, you can try reading through "Coders at Work" that I linked to at the bottom of my post. Another great idea is to just go to Wikipedia with any of the terms you don't know.
Codecademy or things like it might teach you a little more about a specific language, but these are general principles that are not dependent on a given programming language. This is more about software engineering as a discipline.
You might also try "The Agile Samurai" by Jonathan Rasmusson. I've never personally read it, but it's in our office and I didn't hate what I saw in the table of contents.
Thank you for your comment.
The demo that was thrown together is not ready to release into production!
