Scripter -> Developer -> Architect
Reactive -> Proactive -> Pragmatic
Developter is proactive. Architect not focused solely on completion, more about reason and problem solving.
In development there are lots of wrong answers. Lots of really wrong answers. No right answers. Eventually learn to bend rules to solve problems creatively.
Why have coding standards? Consistent both internally and externally Consistent within your own work as well as the community as a whole. Standardized code tends to be self documenting.
Events vs. Method calls. Events don’t rely on other bits of code. They simply broadcast. Something else may or may not be listening. Doesn’t break due to dependancy. Try to absract external dependencies. When something changes, make adjustments to the connection rather than the funcitonality.
Build isolated test cases and integrate when stable. Set micro-deadlines.
Design -> UX <- Developmet
Thoughts:
Really a great roundup of best practices and ways to think about working. It’s nice to have this information collected in one presentation. Made me proud to be part of a development team that implements most if not all of these techniques on some level.