A set of utilities and classes that I have found useful over the years with features like Improved Loggers, Database Setup and many more.
I came across this very interesting article and the author’s views where programming started way back.
To kick it off, I have attached the tools that I am going to use in the development environment. This is not an exhaustive list, and I may add more things to it as I go about development.
What I intent out of this project is not to save the world, but to build a sandbox that can be used by myself and any other developer to try out bigger things like Performance, Analysis, Design, Testing, POCs on new technologies.
I have been running around many things, but I have realized that this time has now come for me to start something; something that I can be proud of. I am no Bill Gates or Einstein and I need to pick up things that I can do for the community. I have all those ideas where I want to do something.
Eclipse Market place – The experience of working on the marketplace was simply wonderful, something that I am not familiar in the Java world of development. Kudos to the Eclipse team to get this one going.
I will let you do the math, but what made me fell out of my chair was the fact that everyone in the room was accepting the fact that even before we were developing the application we would have 66% of the time spent in fixing defects. Not even once did anyone asked, how can we ensure that we do not have so many defects in the application. Now even once did anyone asked if we already have Unit testing how come we still have these many number of defects.
While working on enahncements on a project already in production, I had a very interesting conversation. Let me give a brief background – the core architecture is all in place and we need to build in new functionality. Of course, refactoring is being done along the road. In a specific scenario, I got into a
Unit testing is a way of testing a small unit of functionality. A unit is the smallest testable unit of program usually referred by a function, procedure etc which is a part of a class. Ideally, a unit test is independent of any other unit tests. Benefits The primary goal of a unit test is to
The 2009 CWE/SANS Top 25 Most Dangerous Programming Errors is a list of the most significant programming errors that can lead to serious software vulnerabilities. They occur frequently, are often easy to find, and easy to exploit. They are dangerous because they will frequently allow attackers to completely take over the software, steal data, or