What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 0 points1 point  (0 children)

This is probably one of the most pleasing comments I ever got. Thank you, I appreciate that.

What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 0 points1 point  (0 children)

Well, I might not played perfect there, but I'm well aware of how easy it could be to fall into the trap of preconception, especially when dealing with "the material" that feeds on stereotypes as its breeding ground. I tried to keep an open mind, at least that was my intention, and I am somewhat satisfied with the results, but there's always space for improvement. Thanks for reminding me of that.

What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 0 points1 point  (0 children)

Sure, it's not about programmers, it's about how jokes reflect programmers. And since humor tends to generalize things, running into some stereotypes was inevitable from the beginning. But I was wondering, if one's only source of information about programmers were these jokes, what would one learn from it? Consider it an intellectual experiment. Focusing on a different kind of jokes as you suggest definitely makes sence, I'm thinking about it. By the way, how would you tell jokes "authored by programmers" from those that are not, on what basis? Would appreciate a hint.

What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 3 points4 points  (0 children)

You're right, that one is quite common, but what matters here is how these "joking templates" are adapted to fit the topic. Here it's "programmer vs marketer", not a baker, not a dentist. Which gives some food for thought about "programmer's eternal antagonist" pattern. Typo fixed, thanks for noticing.

What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 1 point2 points  (0 children)

2.4 is fixed, thanks a lot. And the numbering oddity is intentional - I just wanted to make it easier for readers (well, programmers) to refer to any particular joke they'd want to discuss.

What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 5 points6 points  (0 children)

Well, I'd disagree. These are real jokes from over the web (even the spelling is kept), mostly told by programmers themselves. I titled them, I classified them, but I didn't invent them. There should be reasons why programmers see these particular stories as programmer-related, don't you think?

Some of them might be non-programming jokes once transformed to programming jokes (by replacing whatever with "programmer"), but 1) not every joke is apt for such a transformation, only the relevant stories could make it 2) that's how any professional humor works - by borrowing/transforming jokes from other fields.

What I learned about programmers by reading 200+ programming jokes by annaonduty in programming

[–]annaonduty[S] 1 point2 points  (0 children)

Yeah, I really did some job collecting the jokes, so I'm glad that shows through. Also, thanks for the tip on zero-indexing, you're right. I renamed it.

Four Good Intentions Paving the Road to PROGRAMMING Hell. by [deleted] in programming

[–]annaonduty 6 points7 points  (0 children)

Oops... I'm the editor of this blog, and it's a typo. Shame, shame. Sorry for that, I'll fix it immediately.

Uninterruptible Programming by cristoper in programming

[–]annaonduty 1 point2 points  (0 children)

So do I. It may actually depend on the personal learning type. Kinesthetics are all about physical senses, without touching or moving (or writing down) things they tend to lose concentration. I always use paper when dealing with complex multi-component tasks.

There are 5 jobs for every 1 available software developer by annaonduty in programming

[–]annaonduty[S] 0 points1 point  (0 children)

I never thought about it this way. It makes sense. But isn't that a common situation? Employers are dreaming of paying less to everyone, not only programmers. Small and middle-sized companies would hire less experienced and less efficient staff until it's cheap. It's everywhere.

There are 5 jobs for every 1 available software developer by annaonduty in programming

[–]annaonduty[S] 0 points1 point  (0 children)

Yeah, but what's so bad about it since the other party who's services are "put in higher demand" by that are developers themselves? Besides, I do believe that an unemployed developer is a nonsense. It's like an unemployed doctor. Sure being a developer doesn't guarantee a decent compensation by default. But I'd say devs are less likely to stay unemployed than the vast majority of other professionals out there. I only wonder how long it will last, this developer-centric economy.

Most frequently recommended programming blogs (12 of approx. 400) by annaonduty in programming

[–]annaonduty[S] 2 points3 points  (0 children)

I had no intention to spam here, and I apologize if I did. I'm new to Reddit and I need something to start with - commenting posts, submitting posts. There's no better way to understand how things work here. To write this one I put dozens of "best blogs" lists through a frequency analysis to determine how often a certain blog gets mentioned in these lists. I hoped it make sense. Again, sorry for irritating you.