There was a lot to learn at the Java sessions of the GIDS 2012 with topics covering Java 7, Java 8, Concurrency in Java using STM model, Java EE 7 and its […]
The main focus of the day was the emergence or in otherwords out growth of mobile devices over desktop/laptop in the Q4 of 2010. And also the importance of making the applications […]
I got to know about Code Simplicity: The Science of Software Development book via some O’Reilly promotion and bought an eBook for some $6 or Re. 300. Some good points: The most […]
I have a few interesting titles lined up for this month: Test-Driven Development by Example, Kent Beck – Learning TDD by example, a fairly small book which gives me a lot of […]
I got to know about JDeodorant– a tool for identifying bad smells in code and helping it to refactor. I got curious and downloaded its Eclipse plugin, I then picked the first […]
There was a query on Javaranch regarding participating in Open Source projects and I made an attempt to provide somewhat elaborate reply to it. I thought of putting up the reply on […]
What is legacy code?
At the start of the post I tried to get some definition for the term: “legacy”. (we wish if the noun was true! but indirectly they are one of the reasons for our pay). The adjective definition is somewhat closer to our “legacy code”.
Legacy code is something:
that has been written previously ( may be years old or even months, may be written by another developer or by the same developer) and continues to work just well to satisfy the customer needs.
that is being written as I am writing this post (and it is something which evolves to a legacy code stature in no time) and just enough to implement the requirements.
This book does justice to its title and subtitle- it clearly tells you the basic design principles to write good code which is easy to read, debug and extend. At first glance the title may seem misleading as it uses the word “Agile Developer” but there isn’t much specific to agile in the book, though familiarity with terms like Scrum or Kanaban or TDD would be an added advantage.
Those who are working on High Available systems/databases consider Redundancy as one of the possible ways to achieve high availability. Redundancy in this case is helping in positive way. But consider the […]