Monthly Archives: April 2015

I took the time today to move the protobuf-rpc-pro library from GoogleCode to GitHub. The new link:

There has been a lot of ranting and raving in the developer community about this decision to discontinue the GoogleCode service. Personally I can understand that it doesn’t bring any revenue to Google and Google’s own developers would prefer to use GitHub. I had also started using GitHub for new projects and so now consolidating protobuf-rpc-pro into GitHub is convenient for me.

The automatic export tool did all the heavy lifting and converted the repository from SVN to Git. A year ago i  might not have been so happy. I took my time transitioning to Git because it did bring with it a fair learning curve ( even after I’ve learned RCS, CMVC, CVS and SVN in the past ) – but after the pain there was some gain.


My #1 motto currently is “Don’t do something until you understand what you’re doing“.

Software developers are often tasked with doing something they don’t understand. This is normal in the enterprise world, particularly where “segregation of duties” is fashionable. When requirements are hashed out between business people and requirement engineers, designs between requirement engineers and architects, and implementation concepts between those architects and product responsibles – the developer is mostly invited very late to the party. The developer is put under pressure to deliver by the entire enterprise software delivery apparatus and if the developer then starts asking questions, this invariably is “frowned” upon by the powers that be. This pressure psychology automatically stops developers asking necessary questions and a culture of “just do it” takes over. The results are unsatisfactory for everyone – the delivery quality suffers and developers do not learn and grow as much as they could to satisfy the needs of the larger corporation.

If everyone tried to work by this motto, and let work by this motto, then I’m sure IT projects would be more successful.

Personally i make every effort to really understand what i’m doing, and acting as scrum master or in roles where work is prepared for others, i put making things understandable for others at the top of my agenda.