Agile software development, the principles. Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.
Agile software development, the principles. Principle 10: Simplicity -“the art of maximizing the amount of work not done“- is essential
This is the tenth of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher quality, faster, with a higher acceptance to end-users and able to follow the changing business requirements to strive for competitive advantage.The question is: is this going to work in practice or is this only based on a nice marketing and sales story. Principle 10: Simplicity–the art of maximizing the amount of work not done–is essential. The KISS rule (Keep it stupid and simple) applies here. Simple things are easy to understand, and straightforward to implement. Simple things do not cost a lot of time (or money) to implement and are therefore also easy (painless) to revert. The middle part of this principle “maximizing the amount of work not done” is harder. When implementing agility in an organization this is the cause of discussion. Maximizing the work not done implies that the agile method will skip some processes, code and steps that where More >
The Java Specification Request 317 (JSR-317) aka JavaTM Persistence 2.0, (JPA 2.0) has finally reached the last stage, “Completion of Reference Implementation (RI) and Technology Compatibility Kit (TCK)”, before it’s officially released. Therefore last week a Knowledge Class was given at Amis with a presentation of the new functionality and differences compared to JPA 1.0 and some hands-on exercises. (more…)
Bloom Filters, Hierarchical Profiling, Synopses & One pass distinct sampling, jumping the GAPP … – feast for DBAs (considered harmful..)
It’s Monday night and a select company of DBAs and Database developers have gathered at AMIS HQ in Nieuwegein for the ‘Looking Back at Hotsos 2009′ session. It is one of those sessions that has a lot of energy, laughter and a wealth of serious content. Four very experienced speakers relate their best experiences and most important learning points from the Hotsos conference. And the audience is allowed to participate. Speakers are Marco Gralike, Toon Koppelaars, Gerwin Hendriksen and Jeroen Evers.
The evening brings us – apart from a quite good dinner – interesting topics such as Bloom Filters, Hierarchical Profiling,..
(note: the text in the title between parentheses are for insiders only)(more…)
When developing or testing your web application, you often have to support different browsers and versions. On Window machines testing for different versions of Firefox, Opera and Chrome is not a real problem as these browsers all allow you to install different versions on one machine. Only Internet Explorer (IE) is always a bit more difficult, because it’s integrated in the OS (Windows) of the machine. This mostly ends up installing multiple IE versions on multiple (virtual) machines, which is not a nice way of working when developing. Can we do this different and easier? Yes, we can!
Update (4-4-2012): IETester now supports IE 5.5 up to IE 10!