As a programmer we sometimes might look like we are not doing much from the outside but actually we're dead inside thank you
Science Memes
Welcome to c/science_memes @ Mander.xyz!
A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.
Rules
- Don't throw mud. Behave like an intellectual and remember the human.
- Keep it rooted (on topic).
- No spam.
- Infographics welcome, get schooled.
This is a science community. We use the Dawkins definition of meme.
Research Committee
Other Mander Communities
Science and Research
Biology and Life Sciences
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- !reptiles and [email protected]
Physical Sciences
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Humanities and Social Sciences
Practical and Applied Sciences
- !exercise-and [email protected]
- [email protected]
- !self [email protected]
- [email protected]
- [email protected]
- [email protected]
Memes
Miscellaneous
ptogrammer, i think you mean
Shhh don't tell my boss I'm a PTOgrammer 😎🍹
pardon his spelling.. he was hiphotized!
I honestly needed to hear this today, so thank you. I'm at work trying to work out someone else's uncommented code and have just been staring at it mumbling to myself. I'm new to the position so I'm anxious my new coworkers will think I'm just dicking around... This is the validation I needed. Thanks everyone!
Say out loud to yourself, "What the hell is this?" or, "Why did they do it this way?" once in a while. Everyone around will think you know exactly what you're doing.
exactly. like a former boss of mine said: if they are complaining, they are working!
From what I learned in my workplace, it seems that for most people the best way to appear competent is to continuously criticize the work of your colleagues
I don't know your circumstances, but it is usually OK to just ask. Especially if the original author is around. Don't do it all the time and you'll be OK. Even can come with positive image out of it, if you ask the right questions.
Other than that, I found that the current llms like ChatGPT (and perhaps Claude) are very good at explaining code, most of the time, for some languages ;)
I find for coding problems it's actually better to walk away and let it tick over in your mind.
You'll often get a shower thought type moment.
That works for pretty much anything.
Get up and do anything else for a while. School teaches us to sit at our desks and work on the problem. Stop acting like a sixth grader.
That works for pretty much anything. Get up and do anything else for a while.
This got me fired from the daycare
You were just staring at the kids. You were supposed to be changing diapers and feeding them. Insert obvious misunderstanding here.
A true software developer will also raise their hands in celebration when they finally solve a problem that’s been plaguing them.
Even if you’re working from home, alone.
I often cackle maniacally when I solve something in a particularly effective way.
Aside from "learning to spell hypnotized or just trusting your phone knows better than you," there are a bunch of tricks we use.
- Staring at it and going over the code path
- Talking to a proverbial duck
- Going out for a proverbial cheeseburger
- Sleeping on it
Half of these tricks force the brain to stop confirming and start seeing, which is our biggest error source. The rest of these tricks let the problem ruminate in our subconscious which is sometimes really good at solving shit.
My math teacher in high school always said "math is 90% looking" and if you didn't get the task directly: "look again" ... Funny part is, that actually worked for most of the class xD
I used to work in an office with 4 other developers. It was a common occurrence to have the lights go off in the room, for energy saving.
Simone would wave their arm, then go back to staring.
God bless Simone
At least they’re moving. Sometimes it goes off and nobody reacts at all.
Sometimes figuring out what you’re supposed to do is most of the project.
I work in a dedicated room in my house (remote developer). During the day I don’t really need to turn the lights on—windows and a skylight. The sun sets and sometimes I really just don’t notice. My wife will come in at some point and scold me for working in the dark, claiming it’s bad for my eyes (as if staring at a screen all day isn’t already).
I actually rather enjoy that rather not-subtle marker of the passage of time and how entrancing “the zone” can be such that I fail to even notice that.
What I do is I read over something, take a nap, and then read it over again. If I don't get it after that I'll ask someone for help.
Taking a break helps a lot. I like to multitask for this reason and to not feel like wasting time. Also, important to remember to eat. There's an obvious drop in my clarity of mind right before lunch.
100%. Really, just go do something other than what you've been focusing on, then come back to it. When I was coding, I would go take a walk when I'd get stuck. 9 times out of ten the answer would pop into my head when I'd stepped away. A few times I even dreamed of the answer while sleeping.
If staring at it isn't giving the results you expect, try not staring at it. Math, much like photons, functions differently when observed.
I refer to the process as "loading" and it helps so much when coding, debugging or even playing puzzle games
I had a theoretical math professor. He said something along the lines of, "Being a theoretical math professor is the best job in the world. You can lean back in your chair, put your feet on your desk and close your eyes, and no one can tell if you're working or having a nap."
Tbh a good builder/technician will do this too when faced with a complicated fix
Same thing; every action has an opposite reaction, whether it's code or physical engineering
I'm a carpenter, I do high end stuff for rich people with really expensive pieces of wood. I'll stare as much as I need to on the issues I have or even before starting anything. Need to think about every way it could go wrong.
Don't ask him, he will be angry and mumbling something about "the zone".
I’ve often been accused of looking angry when I’m thinking about a problem. Of course I’m angry! How dare the solution allude me! 😡
Allude what to you?
If I intimidate it by staring at it long enough, it'll work eventually.
I don't like coding, so I became a systems administrator.
Today, I spent about three hours "coding" a script. Before I started my testing phase to see if all the code put together would work as intended, I just did a pass over the code. I literally just stared at it for a solid 20+ minutes to make sure it made sense.
I imagine any form of "real" programming is going to require a lot more staring for a lot longer just to make sure the code isn't profoundly screwed up.
Sometimes, very rare but still, I can stare at the screen for the whole day and write zero lines of code. These rare days are the most demanding and the most stressful. Any monkey can "write code", understanding the business logic of a complex application - that's a very taxing mental work.
Damn, I can't think about something for more than a minutes or two without getting distracted... Maybe I'm the one who's broken.
That's the fun part. We're all broken in some way.
Wait until she walks in on him explaining the problem out loud to a rubber duck.
Meetings where you're working on a problem together are also fun. Just a bunch of people staring silently at a whiteboard.