Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
1 but trying to move to 2 in the long run. But I'm not good enough to write things without trying some stuff first. But for the current project I take my time to think first and code later.
-
1, and as things begin working i refactor into objects and functions for repeatable actions. Generally end up with a nice utility set.
-
I'm definitely #1. I get an idea and have to try it before I can organize it. Otherwise, I forget.
-
#2 because:
1. it's efficient
2. it makes things easy, especially when your code is 1000 lines long
3. when you're done, no need to reorganize your code, it's already done!!!
4. documenting your code is easier, because the best moment to document a function is when you're writing it
Some people mentioned testing. It is always possible to test a piece of code by creating a stub or on a side project you keep for testing stuff. -
xroad23808y1 is pretty tempting. But unless you're an amazing coder that's spent years perfecting your craft you'll eventually be stuck fixing things you didn't think through
Related Rants
[POLL] How do you develop stuff?
1 - just write code. It doesn't need to be organized, it just need to work how you thought it would, and THEN you start organizing things, like editing/creating new files, letting things DRY, optimizing the sutff you did earlier;
OR
2 - you surgically write code, making sure you keep everything is organized from the beginning. Basically you only write when you are sure.
Or maybe it's a blend between the two or something.
I'm asking because I do like the #1 and I feel uncomfortable when people see my code when it's under development. It's a mess, there are tons of comments everywhere and a bunch of repetition. But, when I find the right stuff, I start writing modules to make my code work better, remove unnecessary things, add documentation, and so on.
My development process is not the best of the best, but I get things done with it.
undefined
process
programming
code