January 2015 Edition of MSDN Magazine

Click to open the PDF file

Erik Meijer: AGILE must be destroyed, once and for all

Enough of the stand-up meetings please, just WRITE SOME CODE

Comment A couple of months back, Dutch computer scientist Erik Meijer gave an outspoken and distinctly anti-Agile talk at the Reaktor Dev Day in Finland.

“Agile is a cancer that we have to eliminate from the industry,” said Meijer; harsh words for a methodology that started in the nineties as a lightweight alternative to bureaucratic and inflexible approaches to software development.

The Agile Manifesto is a statement from a number of development gurus espousing four principles:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Resigning from Mizuho

Today I took a plunge and decided to resign from Mizuho. While all the team members are great to deal with the boss is into micro-managing, trying to control every aspect of your work.This has lasted for several months now and pushed me over the edge, I absolutely hated coming to work.

The job market here in London is very good and I have already had several interviews. I noted that there are quite a few jobs requiring knowledge of web technologies – MVC, ASP.NET, jQuery, AngularJS.

Liking all things new, I went ahead and bought a few books on various web technologies:

My plan is to get up to speed with those technologies so that they can be put on my CV. Back in the days (2003 – 2005) I used to be a very good web developer. It would be very exiting to see the web development has progressed since

Automatic Non-Deterministic Finalisation

The automatic mechanism cannot be deterministic, because it must rely on on the GC to discover whether the object is referenced or not. At times this behaviour is a show stopper. because temporary “resource leaks” or holding a shared resource locked for slightly longer than necessary might be unacceptable in an application. At others, it’s perfectly acceptable. I will focus on the scenarios where it is.

Any type can override protected Finilize method defined by System.Object to indicate that it required automatic finalisation. However the C# syntax for requesting automatic finalisation on a class A is to implement method ~A(). This method is called finiliser a must be invoked when the object is destroyed.

Incidentally any type can have a finalizer, even the value types. However the finalizer on the value type object will never be invoked.