3 ms·
I used to call this cowboy development, but I think the term is unfair and draws an inaccurate parallel between this and a bunch of mediocre programmers hacking
by swombat 18y ago
I used to call this cowboy development, but I think the term is unfair and draws an inaccurate parallel between this and a bunch of mediocre programmers hacking away without structure.
I made a point of not calling it agile either, because agile is actually very structured, not at all chaotic like this mode of development.
An important distinction with cowboy development is that you can do cowboy development with pretty much any programmers, but most programmers are not capable of this mode of development. It requires a very open and sharp mind (ability to discover and absorb new technologies at a very rapid pace and to embrace evolving requirements without always bitching about how requirements aren't stable).
I struggle to find a name for it, though.
- rapind 18y agoElite Cowboy Development then? I wasn't really trying to make a distinction about the coders capabilities. To be honest, I think it has more to do with creativity and drive than it does with mad maths or lambda the ultimate forum contributions. Regardless I don't personally associate negative connotations with this method. I'm sure in some situations it can be disastrous, but nothings perfect and I guarantee there have been plenty of agile disasters as well.
- notauser 18y agoThere could be very short book in this! The ECD process methodology. Chapter 1: Core Principles. - Just build it. Chapter 2: Defect management. - Just fix it. Etc :)
- MaysonL 18y agoCall it Pam - Project adapted methodology. The amount of rigor the development process needs depends on the project and the developers. With experienced developers, who are good at communication and negotiation (i.e. no big ego problems) working in a problem domain which they understand (i.e. no big unknowns waiting to bite) this is probably the quickest way to get a great product.