What's the best software development cycle

Use a piece of paper to draw boxes and arrows
Write something that works
Clean it up, then add and improve.

Rinse and repeat. Common mistakes include adding too many features before you get something to work, or spending too long doing the pen and paper and writing an autistic ASM engine for ten years.

PROGRAMMING, MOTHERFUCKER
http://programming-motherfucker.com/

>>55865659
Red
Green
Refactor

>>55865697
Writing down the diagrams first will make you stick to the diagrams.
It will make you use a bad design, if your initial conceptions were wrong. Using TDD and refactoring your code will help you find the fitting design during development.
That does not mean, that you should not plan the design. It means, that you know the design, but it won't be written in stone. Write the documentation after you wrote the code.

>>55865742
That's a good description how to make unmaintainable software.

>>55865659
>worf high on euphoria

>>55865987
Depends on how you read it. I read it as "Just hire smart enough devs and they'll be reasonable about it without you having to enforce a procedure."

>>55866037
I see what you mean.

It will need the programmers to have strict development standards.

What I experienced is, that different people think differently. Without a reliable development procedure, these ideas can be really hard to standardise.
It will make harder and harder to refactor the code in a maintainable order. Thus it will eventually become unmaintainable.

>>55866245

This is what annoys me about industry. Too many thick graduates that think they can program. You don't need software lifecycle bullshit to write understandable maintainable code.

If you are a good programmer you understand the problem, and understand the language in which you express your solution to that problem.

The two greatest programmers in any language will have very similar solutions to the same problem if they both understand it fully. This is because they will write in the idiomatic style of that language.

OOP has brought in a generation of retards who dribble "huh duh i use the singleton design pattern here" and think this means that other people as smart as they are will understand because "huh duh everyone knows that pattern" rather than understanding the problem and finding the simplest idiomatic solution in their language.

Fucking retards ruining programming.

Fucking graduates that don't understand computing but dribble out design patterns.

Fucking industry that just hires the lowest tier because people are interchangeable rather than hiring skill.