"Design First" might send the wrong message. If your design is more than a very rough archtiecture then it'll more likely get in the way than be helpful. Detailed designs are generally not helpful. Langauges, and libraries, are high enough level now that you can easily think about desing while coding.
I'm not certain multiple prototypes are really that helpful. Actually, I've rarely done much prototyping. I see no reason why you'd intentionally build code to throw out. Why not write code with the goal of needing lots of refactoring? This isn't to say some code won't be thrown out, but why make that the goal?
I do believe in automating as much as possible, but I must say I don't use an IDE.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Design First" might send the wrong message. If your design is more than a very rough archtiecture then it'll more likely get in the way than be helpful. Detailed designs are generally not helpful. Langauges, and libraries, are high enough level now that you can easily think about desing while coding.
I'm not certain multiple prototypes are really that helpful. Actually, I've rarely done much prototyping. I see no reason why you'd intentionally build code to throw out. Why not write code with the goal of needing lots of refactoring? This isn't to say some code won't be thrown out, but why make that the goal?
I do believe in automating as much as possible, but I must say I don't use an IDE.