Aren’t you supposed to write out the broad-strokes of what you’re trying to do, that way when you get to the computer, you already know what you’re trying to write & you have an outline to reference.
You write it up only to write it up? Sounds like two times the work with no benefit. And what if someone breaks your concentration while you write the strokes up?
That’s what I was taught. Right an outline, in English or what you speak, of what each component of the program is supposed to do, then you write the actual components, in code, on the computer.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Aren’t you supposed to write out the broad-strokes of what you’re trying to do, that way when you get to the computer, you already know what you’re trying to write & you have an outline to reference.
Correct, came here to say this.
Now, do I practice what I preach? ehhhhhhhhh
You write it up only to write it up? Sounds like two times the work with no benefit. And what if someone breaks your concentration while you write the strokes up?
That’s what I was taught. Right an outline, in English or what you speak, of what each component of the program is supposed to do, then you write the actual components, in code, on the computer.
Ah, that’s what you meant, lol.