Does anyone else type pseudo-code and then just stare at it in despair?

@JavaScriptCoff1 Usually that happens when I just start coding Then I write pseudo-code and it pulls me out of the abyss

@JavaScriptCoff1 Don't despair. You'll find a way! (Also, yes, some problems are hard to solve.)

@JavaScriptCoff1 Do you... have access to my desktop... ?

@JavaScriptCoff1 😅😊😂

@JavaScriptCoff1 Comment driven development here.

@JavaScriptCoff1 sometimes, yes. Most of the time I throw away what I just wrote, realise there was already a function to do this and throw away the code. Then I draw a diagram of what other services will provide stuff I need.

@JavaScriptCoff1 Sometimes, if the problem is REALLY hard. Haven't done that since 2016.

@JavaScriptCoff1 sometimes, yeah

@JavaScriptCoff1 Not I. I type *actual* code and stare at it in despair.

@JavaScriptCoff1 Yes but with UI sketches

@JavaScriptCoff1 Yes. Every day.😂

@JavaScriptCoff1 That's how I approach a lot of programming problems. Let the code explain the comments to the computer.

@JavaScriptCoff1 You're not the only one LMAO😂😂

@JavaScriptCoff1 You just made me laugh,its a struggle,good thing is once you start putting that pseudo-code into lines of code,you dont stop,

@JavaScriptCoff1 yeah I do that allot actually

@JavaScriptCoff1 🤣

@JavaScriptCoff1 Yes.

@JavaScriptCoff1 Sometimes I skip pseudo and go straight to comments haha 🤣

@JavaScriptCoff1 I often draw charts instead of pseudo-code. I think the brain or rather my brain feels more comfortable with diagrams than with "mathematical" representations of the problem I think real world/software problems/solutions can always be broken down in some kind of chart or diagram

@JavaScriptCoff1 I used to start out by writing pseudocode as comments in my editor, and then built my code around it and left it in there to document what was going on.