Mind maps - You gotta love them!

Mind maps are a creative and much more interesting way, in my perspective, of taking notes, instead of those boring huge reports that we rarely read again...

Here's an example of a use to it:
http://ebgconsulting.com/blog/amplify-learning-with-mind-maps/

Enjoy!
And have fun! :-):-)

How to keep focus in an era of distractions (in Portuguese)!

:)

TDD in Javascript

Test Driven Development (TDD) is a crucial part of quality software development.

For that matter, exploring tools and frameworks to implement and/or improve the implementation of test suites is part of this process.

Here's a presentation on tools and frameworks for implementing TDD in javascript:
http://www.infoq.com/presentations/tdd-javascript

Have fun! :)

"10 management tips for great leaders"

For those in leadership positions, those that aspire to them, and those being leaded also!



Have fun! :)

Roadmap to Agile Documentation

It's freshly published my new article on Agile Methodologies, this one on the topic of documentation, and that InfoQ has kindly agreed to publish!

Since Agile Methodologies aren't specific about the documentation issue, it is a theme that frequently comes up in forums where folks working in Agile environments gather and share thoughts.

So, in this article it is proposed a kind of a roadmap that I hope will help to define some guidelines on how do we produce documentation (functional and technical) in the scope of a project managed in the Agile ways.

Here's the link: http://www.infoq.com/articles/roadmap-agile-documentation

Feel free to comment, criticize, disagree, etc etc...

And have fun! :)

Update:
It is also available through DZone, which also offers voting buttons on articles. Interesting :)
Here's the link, which also gives access to the article in InfoQ:
http://www.dzone.com/links/a_roadmap_to_agile_documentation.html

"The Importance of Slack in Achieving Speed and Quality", by Steve Bement

Article on the importance of planning your sprint with some slack in order to increase velocity and decrease technical debt, among other benefits.

"throughout the sprint your team follows the practices of emergent design and refactoring. [...] Refactoring is a way to pay down technical debt. If you don’t continuously pay down this debt, the design of the code deteriorates and the software becomes brittle (hard to change). This makes you go slower. On the other hand, if constant attention is paid to design, through refactoring, the code becomes easier to change, which increases velocity."

Take a peek: http://www.solutionsiq.com/resources/agileiq-blog/bid/101012/The-Importance-of-Slack-in-Achieving-Speed-and-Quality

Have fun :)

New Pyramid of Needs :)

[No legend necessary, I suppose... ;)]