5 ms·

Seems like as good of a time as any to bring up Zed Shaw's "Programming, Motherfucker": http://programming-motherfucker.com/ http://programming-motherfucker.com

Seems like as good of a time as any to bring up Zed Shaw's "Programming, Motherfucker": http://programming-motherfucker.com/ http://programming-motherfucker.com/ We are a community of motherfucking programmers who have been humiliated by software development methodologies for years. We are tired of XP, Scrum, Kanban, Waterfall, Software Craftsmanship (aka XP-Lite) and anything else getting in the way of...Programming, Motherfucker. We are tired of being told we're autistic idiots who need to be manipulated to work in a Forced Pair Programming chain gang without any time to be creative because none of the 10 managers on the project can do... Programming, Motherfucker. We must destroy these methodologies that get in the way of...Programming, Motherfucker.

trentmb 13y ago
He's very annoying to read. EDIT: To clarify, his style is incredibly annoying.
- djillionsmix 13y ago
  Annoying to people who don't like that he's correct
  - deleted 13y ago
    [deleted]
  - tcdent 13y ago
    I agree with his thinking, but his presentation is just too in-your-face. It can be hard to find a balance when communicating something you're passionate about.
  - rbanffy 13y ago
    Actually, no. He isn't right. Any significant programming project involves more than one person. Being arrogant is probably the most serious flaw in a programmer. You will be wrong. You will under or overestimate something important. You do have blind spots. Most important, you are not as smart as you think you are. If you are not careful, your mistakes will ruin your project. They'll delay you or create liabilities you'll have to deal with. Methodologies exist to help you manage yourself, not for your managers to better manage you (although they can be misused for that). You don't have to feel "humiliated" by them (neither methodologies nor managers). You don't have to be insecure.
  - trentmb 13y ago
    Right or not isn't the point. It's painful to read because it's a grown man that writes like a 10 year old that learned a couple of dirty words. I cringe in embarrassment on his behalf: http://zedshaw.com/#/fuck http://zedshaw.com/#/fuck
mercurial 13y ago
If only successful projects were a matter of good programming...

trentmb 13y ago

He's very annoying to read. EDIT: To clarify, his style is incredibly annoying.

djillionsmix 13y ago
Annoying to people who don't like that he's correct
- deleted 13y ago
  [deleted]
- tcdent 13y ago
  I agree with his thinking, but his presentation is just too in-your-face. It can be hard to find a balance when communicating something you're passionate about.
- rbanffy 13y ago
  Actually, no. He isn't right. Any significant programming project involves more than one person. Being arrogant is probably the most serious flaw in a programmer. You will be wrong. You will under or overestimate something important. You do have blind spots. Most important, you are not as smart as you think you are. If you are not careful, your mistakes will ruin your project. They'll delay you or create liabilities you'll have to deal with. Methodologies exist to help you manage yourself, not for your managers to better manage you (although they can be misused for that). You don't have to feel "humiliated" by them (neither methodologies nor managers). You don't have to be insecure.
- trentmb 13y ago
  Right or not isn't the point. It's painful to read because it's a grown man that writes like a 10 year old that learned a couple of dirty words. I cringe in embarrassment on his behalf: http://zedshaw.com/#/fuck http://zedshaw.com/#/fuck

mercurial 13y ago

If only successful projects were a matter of good programming...