The Holy Java

Building the right thing, building it right, fast

Most interesting links of August ’12

Posted by Jakub Holý on August 31, 2012

Recommended Readings

  • How To Fail With Agile:Twenty Tips to Help You Avoid Success – a great overview of ways people may make agile projects and initiatives fail – use them to either avoid the failure or to make it certain, according to your attitude towards agile
  • vim-adventures.com: Learning Vim keys in an entertaining way by playing an on-line 2D game. A brilliant idea!
  • The Search for a Better BIG Data Analytics Pipeline – how to use big data and analytics on it in a company. Big data = lot of data, simple processing; deep analysis = representative, small sample of data (no need for all), advanced techniques. Big data can provide input for analysis.

Links to Keep

  • Pat Kua’s Onboarding Strategies series – tips for getting new people onto your team as a tech lead and making them productive quickly. He also wrote the InfoQ article A Leaner Start: Reducing Team Setup Times based on the series. Some posts: Catalogue of patterns applied, Airing .. about feedback meetings, Pair programming, Preparation e-mail, Domain driven design and readable code, Tech huddles (what-we-learned session every 2nd day), Transparent technical debt, Visible architecture, Big vision business problem.

Useful Tools

  • OWASP Hatkit Proxy: TCP/HTTP proxy intended for developers that can intercept and modify requests and store parsed communication into MongoDB for later exploration. You can define what (not) to store/intercept with white- (black-)lists. Syntax highlighting, Swing UI etc.
  • Using Doxygen to understand a code base – Doxygen can generate a full cross reference of source code, class diagram, caller and call graphs for many languages including Java, PHP, C.

Interesting Quotes

Our standards by default exclude comments where possible replaced by representing as much intent as possible in the code itself. We focus on what it does and why. I’ve found “What” tends to be best represented by production code, whilst “Why” is better explained in tests because you can better represent different contexts there.
Pat Kua: Onboarding strategy: Domain driven design and readable code

About these ads

Sorry, the comment form is closed at this time.

 
%d bloggers like this: