Three good reasons to plan ahead
A large part of project management is about planning: a good plan with realistic goals and schedules goes an extremely long way towards a successful project. It is surprising, however, how many software teams start coding without hardly any planning at all. Worse: they now have arguments to do so, saying it's "agile".Just jumping into the code head-first is not agile: it's just plain stupid. Even on the smallest and easiest of projects, you need to ask yourself at least three questions...
Taking Run-Time Decisions with Funky
This white paper will show you how taking configurable run-time decisions using a small, embeddable, functional programming language – Funky – can increase the maintainability of an application, have very little run-time overhead and does not have any negative impact on application security.
Goals of Software Development and Design
As a professional software architect and programmer, I have had the opportunity to work on various software projects in various stages of development, both free and commercial, and have found that few things are as crucial to the development of a software project as maintainability, stability, scalability and the re-use of prior work. I therefore believe that all software design and implementation should, for as much as possible and in accordance with the development environment (in terms of business, people and tools) and goals of the project, aim for these four goals.
Design Reviews: What, When, How, Who?
In any software development process, whether it be an "agile" process, a "waterfall" process or something in between, design reviews are of the utmost importance - at least if you want to avoid investing a lot of time and money in something you'll throw in the trash when you're done.In this paper, I discuss different stages of design and design review, their different goals, who should do them and when they should be done.
