Meetings

Have you ever been in too many meetings in the name of Agile, or the lack thereof? Convince them of too many unnecessary meetings: http://www.expensivemeeting.com

08858487db1237f4bc818b002f761713

meeting

Advertisements

Web Summary of the Day

On dynamic versus static typing: “fully expressive language is one that supports the delicate interplay between static and dynamic techniques. Languages that force only one perspective on you, namely the dynamic languages, hobble you; languages that admit both modes of reasoning enable you and liberate you from the tyranny of a single type. Let a thousand flowers bloom!” (https://existentialtype.wordpress.com/2011/03/19/dynamic-languages-are-static-languages/)

Agile was never meant to be commercialized. Agile is a set of values, not a certification. One blogger boils it down to: “Being resolute to work with others to always steer to the next possible “better” seems to work nicely.” (http://zuill.us/WoodyZuill/2014/03/31/to-me-this-is-agile/)

Learn to negotiate well behind the keyboard.

For fun, here is an API for insulting people: http://pleaseinsult.me
If you don’t have a Mac, but need one, you can now run one on the cloud: http://www.macincloud.com

Documentation As Your Legacy

Based on hearsay, developers hate documentation…until they come across a project with no documentation!

As you leave your company, how do you want to be remembered? Let me put it this way, if the next programmer is a serial killer that has to review legacy code that you wrote, would you want him to know where you live? Once I thought following a zero comment policy as good because classes, methods, variables should be human readable and obvious, however, there will always be someone who complains about the lack of comments and that your documentation is overwhelming. So, comment sparingly, but when you comment, complement the existing code and comment specifically business reasons behind your code. It’s also useful to use tools in your IDE that automatically apply comments to properties and classes. This is important, but if you comment every object, please don’t leave the default auto-generated comments in there, as they are just as useless as no comments. Finally, you should always reference your code classes to the user-friendly documentation in some other system (such as Confluence). If you comment your code where appropriate and also provide documentation for all your code, then you will be appreciated long past your stay.