Programming Circlejerk @programming.dev Drew @sopuli.xyz 2w ago

Liking any of these indicates a belief system I don't agree with

19 comments

Imagine what their home life is like.
perfect 80/20.
as in, 80% fully agree, 20% what a retard.
- He is opening a lot of fronts there. That is some highly efficient trolling.
No clue as who you are, but it's clear we'll NEVER work together. (And I for one are happy about that)
This is pretty clearly a joke… they said they won’t hire anyone with individual accountability.
- ever heard of blameless postmortems?
  
  I don't see what postmortems have anything to do with individual accountability. individual accountability means the ability to do your job, it has nothing to do with things going wrong. literally performing your job means having individual accountability.
  
  so yeah it's pretty dang clear it's a joke. same for code ownership, tasks for testing or refactoring, design and architecture reviews. The joke is that it's stuff that people love to hate on and then it gets increasingly more ridiculous until it's stuff that you most definitely want to hire for doing/having.
- When you're coding as part of a team blaming individuals isn't helpful. For starters, any code should have gone through at least one level of code review, so there's been multiple sets of eyes on it before it causes trouble. Better to learn from mistakes as a team so everyone gets the benefit of hindsight.
  
  From this, I feel like "accountability" has started to mean being blamed and berated.
  
  That's not what I consider to be accountability and is something I simply consider a waste of time, no matter whether it is a personal or a team thing.
  
  I do use blame and reflog though.
  
  nobody said anything about blaming anyone. Having individual accountability means literally having the ability to do your daily job, such as finishing a ticket you say you're going to finish, following up if you have a delay, working to create meetings if you need meetings, reaching out if you need help. It has nothing to do with if something goes wrong. Where did you get that idea? and like I said below:
  
  so yeah it’s pretty dang clear it’s a joke. same for code ownership, tasks for testing or refactoring, design and architecture reviews. The joke is that it’s stuff that people love to hate on and then it gets increasingly more ridiculous until it’s stuff that you most definitely want to hire for doing/having.
You can tell he's a simple minded idiot because Jabbascript and Go aren't immediate disqualifiers in all scenarios.
Don't mine me, I'm going to cross post this to !linkedinlunatics@sh.itjust.works
I mean it's not a totally unreasonable list but what's with "working alone with headphones on"? And what are "annotations"?

Also Typescript backend can be pretty great actually - especially because it lets you use JSX/TSX. Nothing else is as good.
- the whole post is satire. it's all a joke. It goes from incredibly divisive things to things you'd never reject from a candidate.
"branching strategies"

19 comments