subreddit
stringclasses
7 values
author
stringlengths
3
20
id
stringlengths
5
7
content
stringlengths
67
30.4k
score
int64
0
140k
programmerhumor
Dylantheshoe
h4gyvtm
<|sols|><|sot|>Every damn time<|eot|><|sol|>https://i.redd.it/cxvreisjcx971.jpg<|eol|><|sor|>One word - flexbox<|eor|><|sor|>Me: Yeah flex box is so easy, it just makes sense! Also me: Yeah its easy! Just do align-items-center! No justify-items-center? No place-items-center? Align-self center? Align content center? Wtf this worked last time! Item spacing stretch? Gah just put two siblings with flex: 1! text-align: center?<|eor|><|sor|>And then 30 minutes later you discover you forgot to add "display:flex;"<|eor|><|sor|>Spent half a day realizing I forgot to put flex-direction: row. I put that one line in and everything worked, I then went to the bathroom to cry. This is the way.<|eor|><|eols|><|endoftext|>
124
programmerhumor
Fravona2211
zujq6b
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|eols|><|endoftext|>
29,889
programmerhumor
IAmFalkorn
j1kfwqg
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>can't wait until scrum masters become scrum daddys<|eor|><|eols|><|endoftext|>
5,241
programmerhumor
CHIKIKCHI
j1k438n
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>DB admins managing clusters: <|eor|><|eols|><|endoftext|>
3,327
programmerhumor
heresyforfunnprofit
j1kmwkp
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>DB admins managing clusters: <|eor|><|sor|>Dom and sub. Replicate me harder, daddy.<|eor|><|eols|><|endoftext|>
3,111
programmerhumor
Sindef
j1k1005
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>We don't care so much in my country. Usually we have our branches set up like: ``` Master QA/Test Dev Slave<Employee ID> Slave<Employee ID> Slave<Employee ID> Slave<Employee ID> .etc ```<|eor|><|eols|><|endoftext|>
1,977
programmerhumor
UpstairsAd4105
j1jpsk6
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>Lets not talk about IDE drives.<|eor|><|eols|><|endoftext|>
1,879
programmerhumor
BaronZoltaK
j1kp0ky
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>can't wait until scrum masters become scrum daddys<|eor|><|sor|>I called myself a scrum lord<|eor|><|eols|><|endoftext|>
1,775
programmerhumor
Fourstrokeperro
j1kn4oq
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>`git push origin hamster`<|eor|><|eols|><|endoftext|>
1,739
programmerhumor
DatCoolJeremy
j1khamf
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>That's it. I'm naming my main branch "a" now.<|eor|><|eols|><|endoftext|>
1,375
programmerhumor
skwacky
j1ky1bb
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>That's it. I'm naming my main branch "a" now.<|eor|><|sor|>I use this simple branch naming structure: ``` a |> a-a |> |> a-a-a |> |> a-a-c |> a-c |> a-d ``` (You might notice I skip 'b' this is merely to avoid invoking the historical tensions between the hierarchy of 'a' and 'b')<|eor|><|eols|><|endoftext|>
1,343
programmerhumor
noodle-face
j1kam8t
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>I've never met anyone that actually cared about this. I feel like it was a false sense of panic<|eor|><|eols|><|endoftext|>
1,255
programmerhumor
Icy-Mongoose6386
j1kc40d
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>We don't care so much in my country. Usually we have our branches set up like: ``` Master QA/Test Dev Slave<Employee ID> Slave<Employee ID> Slave<Employee ID> Slave<Employee ID> .etc ```<|eor|><|sor|>each employee is a slave, make sense.<|eor|><|eols|><|endoftext|>
1,206
programmerhumor
Takamasa1
j1kp5vz
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>DB admins managing clusters: <|eor|><|sor|>Dom and sub. Replicate me harder, daddy.<|eor|><|sor|>Out with Master/Slave, in with Dom/Sub<|eor|><|eols|><|endoftext|>
1,117
programmerhumor
gomugomunorocket42
j1k610h
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>[removed]<|eor|><|sor|>Its penis and vagina now.<|eor|><|eols|><|endoftext|>
960
programmerhumor
outhereinamish
j1kbdgx
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>I have always called it master branch, and so have the places Iv worked and people I talk to irl. However, I always called it child branch, or just a branch. Never even heard of slave branch until Reddit.<|eor|><|eols|><|endoftext|>
845
programmerhumor
SleepWouldBeNice
j1kwc3g
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>My electrical engineering textbook in university had the sentence: race conditions can be solved with a master-slave relationship.<|eor|><|eols|><|endoftext|>
793
programmerhumor
AshleyLadyOfDairy
j1kd6fm
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>Mfw I name my default branch 'mistress'<|eor|><|eols|><|endoftext|>
675
programmerhumor
m1ndcrash
j1kbr2i
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>Lets not talk about IDE drives.<|eor|><|sor|>This guy is my age.<|eor|><|eols|><|endoftext|>
671
programmerhumor
BluudLust
j1ksr6j
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>I renamed the branch to Anakin because it is not a master.<|eor|><|eols|><|endoftext|>
612
programmerhumor
difused_shade
j1kd377
<|sols|><|sot|>Ohh well<|eot|><|sol|>https://i.redd.it/xfdzfwo0ly7a1.jpg<|eol|><|sor|>I've never met anyone that actually cared about this. I feel like it was a false sense of panic<|eor|><|sor|>It is.<|eor|><|eols|><|endoftext|>
609
programmerhumor
pizzanreddit
hi4c87
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|eols|><|endoftext|>
29,890
programmerhumor
ScorpionGlitch
fwe7fx6
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Trial and error gives dopamine, reading documentation does not.<|eor|><|eols|><|endoftext|>
917
programmerhumor
ganja_and_code
fwed2m8
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Bold of you to assume the README contains more than boilerplate<|eor|><|eols|><|endoftext|>
867
programmerhumor
captainjon
fwe9xfq
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Trial and error gives dopamine, reading documentation does not.<|eor|><|sor|>I never thought of the why. I just took it as I know better. Typical macho bs. So of course I spend far too much time. And the very top of the document showed what I discovered. So documentation instead proved I know what Im doing after all<|eor|><|eols|><|endoftext|>
222
programmerhumor
domin8r
fwey49d
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Bold of you to assume the README contains more than boilerplate<|eor|><|sor|>[deleted]<|eor|><|sor|>**go to url** Page not found, redirected to homepage.<|eor|><|eols|><|endoftext|>
139
programmerhumor
ltssms0
fween7f
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>[deleted]<|eor|><|sor|>I like writing them because it organizes my thoughts and notes in a more coherent form, and helps make sure the main use cases flow properly.<|eor|><|eols|><|endoftext|>
88
programmerhumor
trimeta
fweapwi
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>In the sciences, I've heard this quoted as "a month in the lab can save you an hour in the library."<|eor|><|eols|><|endoftext|>
80
programmerhumor
Psychpsyo
fwetqof
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Trial and error gives dopamine, reading documentation does not.<|eor|><|sor|>Alternatively you can have hours of trial and error while reading the documentation cause the documentation is a cryptic, incomplete pile of garbage that is three versions out of date.<|eor|><|eols|><|endoftext|>
74
programmerhumor
mustang__1
fwf5if4
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Bold of you to assume the README contains more than boilerplate<|eor|><|sor|>[deleted]<|eor|><|sor|>**go to url** Page not found, redirected to homepage.<|eor|><|sor|>Home page loads to a different company.<|eor|><|eols|><|endoftext|>
74
programmerhumor
RepostSleuthBot
fwedpjv
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>u/RepostSleuthBot<|eor|><|sor|>Looks like a repost. I've seen this image 10 times. First seen [Here](https://redd.it/9vh4vz) on 2018-11-09 100.0% match. Last seen [Here](https://redd.it/ddsfzi) on 2019-10-05 100.0% match **Searched Images:** 128,021,475 | **Indexed Posts:** 529,777,224 | **Search Time:** 7.07594s *Feedback? Hate? Visit r/repostsleuthbot - I'm not perfect, but you can help. Report [ [False Positive](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Positive&message={"post_id": "hi4c87", "meme_template": 1885}) ]*<|eor|><|eols|><|endoftext|>
72
programmerhumor
lemortede3
fwf8buk
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Bold of you to assume the README contains more than boilerplate<|eor|><|sor|>[deleted]<|eor|><|sor|>**go to url** Page not found, redirected to homepage.<|eor|><|sor|>Home page loads to a different company.<|eor|><|sor|>Different company is one of those "purchase this domain that we definitely aquired legally, and we won't screw you over at all"<|eor|><|eols|><|endoftext|>
63
programmerhumor
Karjalan
fwezj6a
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Trial and error gives dopamine, reading documentation does not.<|eor|><|sor|>I never thought of the why. I just took it as I know better. Typical macho bs. So of course I spend far too much time. And the very top of the document showed what I discovered. So documentation instead proved I know what Im doing after all<|eor|><|sor|>Sometimes you can learn more from trial and error. Depends your learning style. Reading often doesn't stick in my head, but if I play around with something, I can experiment to see how the intricacies/edge cases work, and my memory for it down the line is better.<|eor|><|eols|><|endoftext|>
62
programmerhumor
hackintosh5
fwedwrg
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>u/RepostSleuthBot<|eor|><|sor|>Looks like a repost. I've seen this image 10 times. First seen [Here](https://redd.it/9vh4vz) on 2018-11-09 100.0% match. Last seen [Here](https://redd.it/ddsfzi) on 2019-10-05 100.0% match **Searched Images:** 128,021,475 | **Indexed Posts:** 529,777,224 | **Search Time:** 7.07594s *Feedback? Hate? Visit r/repostsleuthbot - I'm not perfect, but you can help. Report [ [False Positive](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Positive&message={"post_id": "hi4c87", "meme_template": 1885}) ]*<|eor|><|sor|>My expectations for you were low but 10 times?!? Holy fuck.<|eor|><|eols|><|endoftext|>
57
programmerhumor
TheTerrasque
fwen8de
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>[deleted]<|eor|><|sor|>I like writing them because it organizes my thoughts and notes in a more coherent form, and helps make sure the main use cases flow properly.<|eor|><|sor|>That's cool, and useful. Problem is two weeks later when only the title is still relatively correct<|eor|><|eols|><|endoftext|>
53
programmerhumor
28f272fe556a1363cc31
fwewpg6
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>I get paid to code, not read. ^/s<|eor|><|eols|><|endoftext|>
36
programmerhumor
hackintosh5
fwednvz
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>u/RepostSleuthBot<|eor|><|eols|><|endoftext|>
36
programmerhumor
higuy8000
fweyyxa
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Bold of you to assume the README contains more than boilerplate<|eor|><|sor|>Bold of you to assume a readme even exists<|eor|><|eols|><|endoftext|>
32
programmerhumor
gunvalid
fwf09kp
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>Trial and error gives dopamine, reading documentation does not.<|eor|><|sor|>I never thought of the why. I just took it as I know better. Typical macho bs. So of course I spend far too much time. And the very top of the document showed what I discovered. So documentation instead proved I know what Im doing after all<|eor|><|sor|>Sometimes you can learn more from trial and error. Depends your learning style. Reading often doesn't stick in my head, but if I play around with something, I can experiment to see how the intricacies/edge cases work, and my memory for it down the line is better.<|eor|><|sor|>I mean yea, if you spend 15 minutes with the system itself, that's gonna be more helpful than 5 minutes of reading.<|eor|><|eols|><|endoftext|>
29
programmerhumor
gutotudo
fwf4ufc
<|sols|><|sot|>Readme is still optional<|eot|><|sol|>https://i.redd.it/upacfh01xv751.jpg<|eol|><|sor|>In the sciences, I've heard this quoted as "a month in the lab can save you an hour in the library."<|eor|><|sor|>Lab sounds more fun<|eor|><|eols|><|endoftext|>
21
programmerhumor
aloofloofah
fmmf3w
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|eols|><|endoftext|>
29,876
programmerhumor
down_vote_magnet
fl55qik
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>This is amazing. Imagine if this was in an office and everyone would be notified that you fucked up a build.<|eor|><|eols|><|endoftext|>
2,256
programmerhumor
BesottedScot
fl5nql5
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>This is amazing. Imagine if this was in an office and everyone would be notified that you fucked up a build.<|eor|><|sor|>Alternatively, one light above your desk. Kinda like a blue-light special, but for embarrassment and peer pressure.<|eor|><|sor|>Delete this before you give management any more fucking bright ideas.<|eor|><|eols|><|endoftext|>
641
programmerhumor
Sammy_Ghost
fl5p0wk
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>Imagine compiling a program a lot of times but the light doesn't turn green so you keep looking for errors before releasing that it's in the lights program<|eor|><|eols|><|endoftext|>
585
programmerhumor
JzJad12
fl5os0f
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>Now you can leave the room for a big build and know if it was successful before going back in. The "do I need a drink before I return" lights.<|eor|><|sor|>My exact thought, this would be sorta useful....<|eor|><|eols|><|endoftext|>
506
programmerhumor
sumdudeinhisundrware
fl5ib3n
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>That red light is going to get old fast.<|eor|><|eols|><|endoftext|>
290
programmerhumor
DeeSnow97
fl5nbt9
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>[deleted]<|eor|><|sor|>This is truly the apocalypse, just not the one we've been expecting, instead of a zombie virus we get bored programmers booting up Skynet<|eor|><|eols|><|endoftext|>
232
programmerhumor
aloofloofah
fl56x7e
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>This is amazing. Imagine if this was in an office and everyone would be notified that you fucked up a build.<|eor|><|soopr|>Some teams have [traffic lights](https://i.imgur.com/pf9rJVp.jpg) or [other contraptions](https://i.imgur.com/e5r6cr0.jpg).<|eoopr|><|eols|><|endoftext|>
231
programmerhumor
meDicenPepe
fl5qtjp
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>Now you can leave the room for a big build and know if it was successful before going back in. The "do I need a drink before I return" lights.<|eor|><|sor|>>do I need a drink before I return yes<|eor|><|eols|><|endoftext|>
214
programmerhumor
WhiteRabbit-_-
fl5ruvq
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>Now you can leave the room for a big build and know if it was successful before going back in. The "do I need a drink before I return" lights.<|eor|><|sor|>My exact thought, this would be sorta useful....<|eor|><|sor|>I had a little 3d printed cube with 9 lights inside that I bought from someone. Did basically this but you can control things like blinking, and running a rainbow, etc. Was a fun little project and could keep it on my work desk.<|eor|><|eols|><|endoftext|>
183
programmerhumor
skt84
fl5pqxn
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>This is amazing. Imagine if this was in an office and everyone would be notified that you fucked up a build.<|eor|><|sor|>Alternatively, one light above your desk. Kinda like a blue-light special, but for embarrassment and peer pressure.<|eor|><|sor|>Delete this before you give management any more fucking bright ideas.<|eor|><|sor|>> light ideas FTFY<|eor|><|eols|><|endoftext|>
168
programmerhumor
Rakkner
fl5k07x
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>Guess I better get used to a red house<|eor|><|eols|><|endoftext|>
115
programmerhumor
Xtrendence
fl5t4it
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>This is amazing. Imagine if this was in an office and everyone would be notified that you fucked up a build.<|eor|><|soopr|>Some teams have [traffic lights](https://i.imgur.com/pf9rJVp.jpg) or [other contraptions](https://i.imgur.com/e5r6cr0.jpg).<|eoopr|><|sor|>Always green! Always green! Always green!<|eor|><|eols|><|endoftext|>
97
programmerhumor
SP0OK5T3R
fl5ozjy
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>src?<|eor|><|soopr|>https://www.linkedin.com/feed/update/urn:li:activity:6646378854137114624<|eoopr|><|sor|>He probably meant the source code, not the source of the post. At least, thats what I expected he was asking for.<|eor|><|eols|><|endoftext|>
80
programmerhumor
JTVivian56
fl5xe2d
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>That red light is going to get old fast.<|eor|><|sor|>Red light, at a dim level, is actually pretty okay to sleep with<|eor|><|eols|><|endoftext|>
77
programmerhumor
grizcreative
fl5vasc
<|sols|><|sot|>Self-isolation day 3: Builds are now hooked up to house lights.<|eot|><|sol|>https://v.redd.it/ej5y8cipa3o41<|eol|><|sor|>Imagine compiling a program a lot of times but the light doesn't turn green so you keep looking for errors before releasing that it's in the lights program<|eor|><|sor|>Underrated comment right here<|eor|><|eols|><|endoftext|>
75
programmerhumor
pawangupta12
e5cmjd
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|eols|><|endoftext|>
29,876
programmerhumor
puplicy
f9j4lrz
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Write code, write test, write bug. Shake all together. Where is the bug now?<|eor|><|eols|><|endoftext|>
1,419
programmerhumor
_-_blade_-_
f9j50jj
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Write code, write test, write bug. Shake all together. Where is the bug now?<|eor|><|sor|>There is no bug if your entire program is a bug<|eor|><|eols|><|endoftext|>
640
programmerhumor
OkazakiNaoki
f9j466q
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Glad there's no test in my code (What?<|eor|><|eols|><|endoftext|>
355
programmerhumor
SeriousSamStone
f9j6dq5
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Easy solution, just write tests for your tests<|eor|><|eols|><|endoftext|>
241
programmerhumor
Mozza7
f9javxv
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Write code, write test, write bug. Shake all together. Where is the bug now?<|eor|><|sor|>There is no bug if your entire program is a bug<|eor|><|sor|>Life, hacked<|eor|><|eols|><|endoftext|>
202
programmerhumor
evenisto
f9j9cyc
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Glad there's no test in my code (What?<|eor|><|sor|>Greatly I have no test,either!<|eor|><|soopr|>but you should always test of your code.<|eoopr|><|sor|>Lol no time for tests when you're the only dev<|eor|><|sor|>You'll regret it later<|eor|><|sor|>My company will regret not hiring more devs.<|eor|><|eols|><|endoftext|>
161
programmerhumor
SuitableDragonfly
f9j7jcm
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>That's why you write the tests first, and then add dummy code to make sure the tests are working, then write the real code.<|eor|><|eols|><|endoftext|>
147
programmerhumor
linus_stallman
f9jaqyk
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Easy solution, just write tests for your tests<|eor|><|sor|>To understand recursion you must first understand recursion<|eor|><|eols|><|endoftext|>
140
programmerhumor
Dazeeeh
f9j9qoz
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Shouldnt it be: Write tests, the tests fail, write code, the tests pass, refactor, success and happiness?<|eor|><|eols|><|endoftext|>
131
programmerhumor
emilews
f9j7f12
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Glad there's no test in my code (What?<|eor|><|sor|>Greatly I have no test,either!<|eor|><|soopr|>but you should always test of your code.<|eoopr|><|sor|>Lol no time for tests when you're the only dev<|eor|><|eols|><|endoftext|>
111
programmerhumor
PM_ME_TITS_4_MEMES
f9j6oe8
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>One time, when I was pretty new to C++, I made a test pointer to an object, so I could watch it while I was debugging. It didnt do anything to the object, just a simple auto var = pObject; Everything in that function looked fine, so I checked in the code. Days pass and I get a bug report saying the program is crashing. Digging into it, elsewhere in the code, far away from my changes, it was crashing because that object was just gone. Couldnt find out why, nothing was modifying the object, no code should be intentionally deleting the object, so why is it- The function I was testing from a few days earlier was destroying my auto var when it ended, and thus destroying the object. Removed my test variable and the code worked fine. Took me 6 hours to find.<|eor|><|eols|><|endoftext|>
96
programmerhumor
conancat
f9ji9ni
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Write code, write test, write bug. Shake all together. Where is the bug now?<|eor|><|sor|>There is no bug if your entire program is a bug<|eor|><|sor|>Life, hacked<|eor|><|sor|>Life,fucked<|eor|><|sor|>Hotel, Trivago.<|eor|><|eols|><|endoftext|>
89
programmerhumor
Adam-Stimulation
f9j5dze
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Glad there's no test in my code (What?<|eor|><|sor|>Greatly I have no test,either!<|eor|><|eols|><|endoftext|>
88
programmerhumor
thatwasagoodyear
f9j8c6p
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>That's why you write the tests first, and then add dummy code to make sure the tests are working, then write the real code.<|eor|><|sor|>And make sure the test is small, only a handful of lines of code. A smaller surface area allows less chance of introducing bugs. Big, complex tests are a code smell.<|eor|><|eols|><|endoftext|>
73
programmerhumor
drewsiferr
f9j99et
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>One time, when I was pretty new to C++, I made a test pointer to an object, so I could watch it while I was debugging. It didnt do anything to the object, just a simple auto var = pObject; Everything in that function looked fine, so I checked in the code. Days pass and I get a bug report saying the program is crashing. Digging into it, elsewhere in the code, far away from my changes, it was crashing because that object was just gone. Couldnt find out why, nothing was modifying the object, no code should be intentionally deleting the object, so why is it- The function I was testing from a few days earlier was destroying my auto var when it ended, and thus destroying the object. Removed my test variable and the code worked fine. Took me 6 hours to find.<|eor|><|sor|>That was not a pointer, then. Not sure what type your pObject was, but a pointer in C++ does not include any cleanup. C++11 introduced `unique_ptr` and `shared_ptr` which do have auto cleanup built in, but you shouldn't get one of those using auto and a pointer type.<|eor|><|eols|><|endoftext|>
59
programmerhumor
sebkuip
f9j989c
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Easy solution, just write tests for your tests<|eor|><|sor|>This comment is how I'm going to explain recursion to others.<|eor|><|eols|><|endoftext|>
55
programmerhumor
Mozza7
f9jaxc0
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Shouldnt it be: Write tests, the tests fail, write code, the tests pass, refactor, success and happiness?<|eor|><|sor|>Success? What's that?<|eor|><|eols|><|endoftext|>
51
programmerhumor
pawangupta12
f9j6qmp
<|sols|><|sot|>Full Procedure of Coding from Beginning to End<|eot|><|sol|>https://i.redd.it/wk0k1s4kyc241.jpg<|eol|><|sor|>Write code, write test, write bug. Shake all together. Where is the bug now?<|eor|><|soopr|>When the tests fail, get the bug in your code and then analyze your code where is a bug<|eoopr|><|eols|><|endoftext|>
46
programmerhumor
Demobeast
gozf5t
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|eols|><|endoftext|>
29,860
programmerhumor
Arhkei
frix7sb
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|eols|><|endoftext|>
3,803
programmerhumor
lordorwell7
frj1ngi
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>A bug that is fixed can be forgotten. A bug that vanishes will always be there. Watching. Waiting.<|eor|><|eols|><|endoftext|>
997
programmerhumor
CaptainLord
frixrlj
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>Especially when you want to see the path the programm took to hit a weird state.<|eor|><|eols|><|endoftext|>
912
programmerhumor
Pixel_Veteran
frjad35
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>Especially when you want to see the path the programm took to hit a weird state.<|eor|><|sor|>That's what debugger is for.<|eor|><|sor|>>The most effective debugging tool is still careful thought, coupled with judiciously placed print statements. Brian Kernighan, "Unix for Beginners" (1979).<|eor|><|eols|><|endoftext|>
408
programmerhumor
bravoalpha90
frizmbm
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>Especially when you want to see the path the programm took to hit a weird state.<|eor|><|sor|>This but specifically in C languages.<|eor|><|eols|><|endoftext|>
379
programmerhumor
retief1
frj0ufa
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>I mean, printing "here" once isn't much, but printing the relevant variables after every line can solve a lot of problems.<|eor|><|eols|><|endoftext|>
344
programmerhumor
theLastNenUser
frj414c
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Read the docs is way too far to the right<|eor|><|eols|><|endoftext|>
334
programmerhumor
UnkleRinkus
frizxes
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>[deleted]<|eor|><|sor|>Taking a walk in my garden is a very common, and effective tactic. Clearing the mind, and letting my background processes work...<|eor|><|eols|><|endoftext|>
275
programmerhumor
How_Does_One_Even
frj5gfn
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>A bug that is fixed can be forgotten. A bug that vanishes will always be there. Watching. Waiting.<|eor|><|sor|>Commiserating<|eor|><|eols|><|endoftext|>
272
programmerhumor
Sororita
frj5i4o
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>I mean, printing "here" once isn't much, but printing the relevant variables after every line can solve a lot of problems.<|eor|><|sor|>it's basically my default debugging method.<|eor|><|eols|><|endoftext|>
217
programmerhumor
John_cCmndhd
frj0nif
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Talking to a rubber duck?<|eor|><|sor|>Or any inanimate object, really https://en.wikipedia.org/wiki/Rubber_duck_debugging<|eor|><|eols|><|endoftext|>
195
programmerhumor
vedran_
frjbl60
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>Especially when you want to see the path the programm took to hit a weird state.<|eor|><|sor|>That's what debugger is for.<|eor|><|sor|>>The most effective debugging tool is still careful thought, coupled with judiciously placed print statements. Brian Kernighan, "Unix for Beginners" (1979).<|eor|><|sor|>Debuggers have come a long way in last 41 years.<|eor|><|eols|><|endoftext|>
193
programmerhumor
itsm1kan
frjby3j
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>Especially when you want to see the path the programm took to hit a weird state.<|eor|><|sor|>That's what debugger is for.<|eor|><|sor|>>The most effective debugging tool is still careful thought, coupled with judiciously placed print statements. Brian Kernighan, "Unix for Beginners" (1979).<|eor|><|sor|>Debuggers have come a long way in last 41 years.<|eor|><|sor|>> 41 years <|eor|><|eols|><|endoftext|>
165
programmerhumor
Alex_Sobol
frj58wx
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>This week I wasted 3 days to rewrite entire code because my old code has this: if(condition)**;** { //code }<|eor|><|eols|><|endoftext|>
153
programmerhumor
leimd
frj1kh7
<|sols|><|sot|>Run it again, that should work<|eot|><|sol|>https://i.imgur.com/giPffR3.jpg<|eol|><|sor|>Print("here!") is underrated in this graph<|eor|><|sor|>Especially when you want to see the path the programm took to hit a weird state.<|eor|><|sor|>This but specifically in C languages.<|eor|><|sor|>[removed]<|eor|><|sor|>I'm genuinely curious how do you relate this meme to the Chinese Government.<|eor|><|eols|><|endoftext|>
150
programmerhumor
Chron0_
aq4isw
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|eols|><|endoftext|>
29,857
programmerhumor
Chron0_
egdfdv1
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>[deleted]<|eor|><|soopr|>It also shifts time by 6 hours<|eoopr|><|eols|><|endoftext|>
534
programmerhumor
walkinghard22
egdfwsf
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>It is 4:09 and I literally just finished doing this.<|eor|><|eols|><|endoftext|>
486
programmerhumor
Chron0_
egdfs12
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>Literally me right now. <|eor|><|sor|>Maybe you'd make progress if you weren't getting distracted by reddit.<|eor|><|soopr|>Its compiling<|eoopr|><|eols|><|endoftext|>
294
programmerhumor
Chron0_
egdfxr8
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>It is 4:09 and I literally just finished doing this.<|eor|><|soopr|>The prophecy holds true<|eoopr|><|eols|><|endoftext|>
272
programmerhumor
kisuka
egdffx3
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>Literally me right now. <|eor|><|sor|>Maybe you'd make progress if you weren't getting distracted by reddit.<|eor|><|eols|><|endoftext|>
201
programmerhumor
kisuka
egdft1c
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>Literally me right now. <|eor|><|sor|>Maybe you'd make progress if you weren't getting distracted by reddit.<|eor|><|soopr|>Its compiling<|eoopr|><|sor|>Oh. Carry on.<|eor|><|eols|><|endoftext|>
122
programmerhumor
Cultured_Swine
egdkjae
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>[deleted]<|eor|><|soopr|>It also shifts time by 6 hours<|eoopr|><|sor|>[insert *Interstellar* water planet time dilation may-may]<|eor|><|eols|><|endoftext|>
103
programmerhumor
Mango1666
egdgh7l
<|sols|><|sot|>Time flies when your doing nothing<|eot|><|sol|>https://i.redd.it/6inluhemsag21.jpg<|eol|><|sor|>im was just doing this... i was updating a file format for a project im developing and i wondered why reading a file in python wasnt reading the same in kotlin. i spent a good 2h getting frustrated and not being able to go deep enough to find a difference in the code. and then i look at the names of the file i am reading in kotlin and they were not the same names.... sometimes the most frustrating bugs are the simplest.<|eor|><|eols|><|endoftext|>
89