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
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
asgs115627y@xavier666 not a standard, it is sarcastic. And it is exactly orthogonal to what you are doing, which I guess some people are already doing
-
LdwVII147yYou're/I'm not alone in this :)
Extra happy if afterwards I can delete all except the top-most comment (the one explaining 'why' all that had to be done) :D -
I did it often when i started learn php; the problem is that this approach lead me to write procedural code, not oop and not easily mantainable in the mid-long term...
-
hendrik5237yI usually create a diagram on Draw.io for OO projects but this sounds like a pretty good idea.
-
creator22067yI put those //TODO: comments.
They are picked up by the IDE and then I know why I screwed up. -
Huuugo25207yI rather go into more detail in the comments and use that pseudocode for going through the logic in my head. Usually every line of pseudocode evolves into 1-3 lines of actual code
-
donuts238507yI just write Main and for each step call another function or interface that does not exist yet...
So yea if you run my initial code, you'll just get a whole bunch of NullPointer or NotImplementedExceptions -
deadfond-1169dFor each phase, I just write Main and call an interface or function
that is not yet defined.
Related Rants
I sometimes write code by first putting comments and then writing the code.
Example
#fetch data
#apply optimization
#send data back to server
Then i put the code in-between the comments so that i can understand the flow.
Anyone else has this habit?
undefined
comments
coding
habit