I recently looked into the Programmer’s Bill of Rights and one commenter’s revised edition.. However, there’s one key problem I had with it and that is the focus on the company providing everything to the developer. Personally, I don’t think it is sustainable for larger enterprises. As such I have a rewrite of the Programmer’s Bill of Rights that can be adapted to more enterprises especially those that are not focused on IT.
Continue reading Enterprise Programmer’s Bill of Rights
On a shared stream (bad idea to begin with) during development, you sometimes have to hold off delivering your changes as it may break the build. However, someone else on your team may need to take your change (even if it is incomplete) to get his work done. This post shows how to cherry pick an undelivered change set into your workspace.
Continue reading Pulling in someone else’s change in RTC
The process to set up Jazz Build Engine which is the continuous integration component to Rational Team Concert is much like setting up the Transient Name Server as a service. The advantage is that the JBE can start when the system restarts automatically. This post shows how to do this task.
Continue reading Running Jazz Build Engine as a service
In a recent interview I had, the interviewer had told me about one of the technologies they use, namely Liquibase. One of the articles I found talked about how to do automatic DB migration for Java web apps with Liquibase. The article had a similar idea flow I wanted to implement. As I was trying to do my implementation of Liquibase DB migration, I found that the schema generation didn’t work as I expected, most likely because I was using Java EE 7 and JPA 2.1. So the search for a plug-in to do this has begun…
Continue reading JPA 2.1 Schema Generator plugin for Maven
Enterprise level Software Configuration Management is important to keep an enterprise going. It’s main purpose is to make sure you can rebuild your software [not the data] in the event of a disaster. However, if someone says the reason for enterprise SCM is so we can track what requirement went with one line of code change two years down the line, I would ask this… why is it important? The only realistic reason is because the organization is riddled in politics and wants the capability of assigning blame two years down the line rather than fixing the issue and moving on with life.
Continue reading The place for Enterprise SCM