Random
Source Code
Random
n. {proh-gram-er}
An organism that turns caffeine and pizza into software.
I am a programmer. :p
2👍 7👎
The feeling of satisfaction a person gets after writing his or her own program and running it successfully. Lasts approximately 10 minutes before wearing off, due to another task appearing immediately after the completion of one task
I let out a sigh of relief and basked in the programmer's high after I had completed this week's programming task. Sadly, hearing my victory sigh, the boss gave me another job to do. Son of a... !!!
45👍 1👎
Those white and blue/pink striped socks femboys wear. Seeing as how a vast majority of programmers are joked to be furries or femboys, that's where this saying gets it's origin.
Twink A: Babe you look really good in your programmer socks, wanna put them on for me?
Twink B: Sure! UwU
The pasty white tan of a person who works over eighty hours a week and never gets any sun.
Bill's been doing a lot of hours lately -- he's really working on his programmer's tan.
2605👍 446👎
In software development, "Ghost Programmer" is a programmer that works for another person's task and receives no credit. This applies for programmers who doesn't have any project assigned to him/her; yet he is forced to join a certain team in a project and works for them secretly making sure the client would not know. When a ghost programmer finished his assigned task, the name/credits that will be written in the code and the document is the one who was originally assigned to that certain task.
Boss: Our project is delayed. We need help from someone. John, can you help with this bug fix?
John: Sure.
After 4 hours..
John: Boss, i'm finished.
Boss: Okay, since you're a ghost programmer, the client should not know about it.. So, the name you should write on the code and the document is the programmer who is originally assigned to it. Okay? :)
John: Okay. (Man! I'm such a ghost programmer. I also want some credits.. )
You've just spent the whole day trying to solve a problem, a design problem, a bug, etc. You know the solution is simple but you just can't see it.
A colleague walks past and notices your anguish: "What's up?".
"Oh, I'm ...". You explain the problem and what you have done so far. However you suddenly discover the solution before you have finished speaking! So far your colleague has been as useful as a cardboard cutout.
This happens often and I think it is due to you having to present your problem to someone in a way that you think will aid their understanding, often dispensing with some of the details. In doing so, you also clarify your own thoughts, untying them in your mind to eventually cite a solution.
Sometimes all it needs is a cardboard cutout of your favorite GURU!
-- RussFreeman.
Also sometimes known as a Programmer's Dummy - DarrenTarbard
My Cardboard Programmer was outsourced to a shoebox in India.
These programmers don't know actually how to write code from scratch or engineer anything; They watch youtube videos online on leetcode and the dry principle 100 times over. They can be intern vloggers, or some layed off PR intern from a big corporation. They commit to open source projects (documentation) and have a soft filter background pfp (With a bland tshirt, short hair or extremely long hair, it's binary; And talk in a very monotone soft voice). Their daily routine consists of waking up, reviewing all the trivia for their language, going into work and not being able to debug anything. However they can talk up a storm, just not actually be the engineers they're required to be. They job hop to the next job before anyone can figure out they actually don't know what they're doing. In meetings they will spit out all the trivia they know, keeping up the act long enough so the manager doesn't notice anything.
Person A: "You remember Jerry? On lunch yesterday he was talking about how he made project x and y in this framework, and how our systems can be completely re-written and improved within a month on this new cool framework he couldn't stop talking about"
Person B: "Oh yea I remember him, he seemed knowledgeable, he passed our medium and hard questions easily."
Person A: "Yea, haha thought the same thing. Turns out he just sat around doing leetcode all day, but I don't know if he even knows what a breakpoint is"
Person B: "His github was really nice!"
Person A: "Well he couldn't debug anything, I ended up doing all the work for him. I think he was just a Trivia Programmer"
Person B: "Really?"
Person A: "Yea he kept asking the same questions, didn't write anything down, never saw any improvements even though I was helping him. I think he just new a lot of trivia, but he can't code"
Person B: "Oh a Trivia Programmer"
Person A: "Yea, last I checked he's making lofi hiphop soft filter videos online about the dry principle. I don't think he applied it in any of his work"
Person B: "His latest video is 'Former Senior Startup Executive Developer Advice' and 'Doing Leetcode As An Intern'"