Ah, when we lose focus for a second and then we don't even known what our code was supposed to do

I like this version more personally.

jesus, this is so accurate is not even funny.
That is when you should have gone to sleep by now, but you just want to figure this out first, and of course it feels impossible because youaree far too tired to think
- Or you mistimed the Balmer Peak managed to do an ungodly amount of progress, forgot to comment in any meaningful way, and the next day try to go through all the changes you did and figure out what the Fuck your were on about, and how this thing works when it seems it really shouldn’t.
- man, you are right, I've gone down some deep, stupid, rabbit holes trying to code while sleep deprived
Personally my memory cache is not big enough in the first place to wrap around complex problems. So I just write things down while thinking.
Yeah the op is a rip off of this original that’s far better imo
Ditch the Remote Config Loader.

This is why I write down the questions I'm trying to answer in a text doc, e.g:

Where is this network call comming from? ../some-api-call.js Why do you think it's causing a 403?

I am authenticating correctly
the object seems to exist in s3
the bucket name is wrong

Etc. So if I lose my thought (all the time), I know exactly what and why I was doing it. Also stops you from re-investigating things you forget

It's a very valid advice.

I also try to do it for complicated bug and it helps me to keep a track of what I tried to do and my hypothesis.
I often take notes in the form of "TODO" comments, as I work through a problem. Then I have my editor set up to highlight them, and my git asks me if I'm sure I want to commit them. Works pretty well with keeping my thought process straight
It's also an amazing way of duck-debugging. By the time you write down what the problem is, you'll figure out where's the issue or at least what you should try next.

"X is giving me an error, I checked X's logs. X communicates with Y... Oh, I need to check Y next!"

And if you can't figure it out, you have the problem and everything you tried documented so you can ask for help and get answers effectively.

Actually there's also the breaking of the psychological state of Flow, which is the mental state of total focus and maximum productivity, which takes about 15 minutes to get to.

Years ago when I had to work as a programmer from the Trading Floor of a major Investment Bank (think Fishmongers' Market but with Financial Assets) I bought some noise reduction earphones and have used those kind of things ever since as they really cut down on distractions and it mainly works.

It even cuts down on the "can you help me for a second" thing because other people actually have to get up and move to were you are to get your attention (as you can't hear them unless they shout), so the zero-effort choice of just calling you from their seat to help them isn't there anymore and one thingI learned pretty early in my career is that in the absence of a zero-effort help path through you for their problems, your colleagues will actually try to first solve their problems themselves and only come to you if they're really stuck, whilst if you're the least effort path to having their problems solve most will just default to breaking your focus and using your time to have their problem solved.

Just sent this to programmer friends to induce certain irony

U madman.

I like it !

Aw I wish they had used “they” instead of “he” so I could put this up at work. But… accurate

Edit: the kind reactions here have changed this comic from one that would remind me of nasty to one that will remind me of nice when I see it. It’s going up.

We’re not on Reddit any more, see below for proof.

The top part is useless anyway, it's funnier if you just crop off the header... that's just one of those things people slap on so they can feel like they've contributed something, but really it's just noise.

Alternatively, just use this one instead:
- jesus, this is so accurate is not even funny.
The original does not have the banner
- Thank you!
i did that edit for you https://gram.social/p/Joe_0237/582801487814840095
- Hey thanks!
Use this version: https://res.cloudinary.com/practicaldev/image/fetch/s--q74QAzOg--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://heeris.id.au/trinkets/ProgrammerInterrupted.png
- I like this version, it is closer to my own drawing style. Thanks kind person
Your work doesn't know about males?

Why can't it say he? Don't understand...
- Female developers exist

Adderall my dudes

Working from home solved a lot of thos for me

the only downside of home office is having my wife do something like that 5x each day

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.