Project start is the time when is most critical and single-handedly decide the fate of the project. That is the time when we are preparing ourselves for a journey, and how well prepared decides: When we reach out destination – on time or late In what condition we reach – as expected or all burnt…
For many years now, I have always found myself going back to TestNG whenever it comes to doing Unit Testing with Java Code. Everytime, I picked up TestNG, people have asked me why do I go over to TestNG especially with JUnit is provided by the default development environment like Eclipse or Maven. Continuing the…
Many years back, I moved over into Java world and when I was asked to implement my very first security implementation, I realized that there was no easy way to do this and many clients would actually want us to use LDAP for authentication and authorization. For many years, I continued to use that. And, then one day in a discussion with a client, we were asked to provide SSO implementation and client did not have an existing setup like SiteMinder. I started to think about if we can go about using NTML based authentication. The reason that was possible was because the application we were asked to build was to be used within the organization itself and all the people were required to login into a domain.
I came across this very interesting article and the author’s views where programming started way back.
I have been a part of a project/product where we did have similar discussions and ensuring that people are getting information relevant to them. The filter bubble that Eli Pariser mentions in his talk is exactly what we did try to build in our product and are even trying to do so today. We pick up programs that people have selected and we then pass on content based on the selections.
I chanced upon this yesterday (http://sourceforge.net/adobe/cairngorm/home/) and was impressed with what they are trying to do. Building upon Parsley looking to do a lot of injection and also support modules that they have been criticized for in the past. Looks like Adobe Cairngorm team finally got it right.
This presentation talks about how mobile web should be thought about and does talks about some numbers too. I like three things about the presentation: 1. The creativity with whcih it has been built and; 2. Talks about the core of the problem and; 3. Touches upon how we can go about fixing it.
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.
In many of my projects, I have found architects guilty of preparing a design that leaves the error messages out of the question. And now, I come across an article that shows us 35 creative designs of showing a 404 page (http://www.onextrapixel.com/2011/03/09/the-secret-of-a-successful-error-page-with-35-amazing-404-page-designs/). As I was browsing some of these designs, I recall a designer I…
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.