this post was submitted on 02 Sep 2023
236 points (94.4% liked)
Programming
17660 readers
156 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You never heard of pair programming?
With juniors Tim would pretty much be training them and nudging them on to write better code.
With seniors, like the short article says, it's more a sparring match, trying to find the best solution. You also find a lot of edge cases when someone else works with you together.
I haven't been in a company yet where they have a full time floating position for pair programming, but if it's a senior doing it I can see how it's very beneficial for product quality.
Tim should be fired for insubordinate and his lead should be fired for protecting him.
I get that every shit developer thinks they a Tim or aspires to be one but Tim is a lazy developer doing the fun parts without producing.
Everyone here is assuming Tim is something because you've told he is by the lead.
It's troubling.
Huh, it's like I'm reading something my nephew wrote. He has a tendency to only read the first few sentences, skim through the story, and come back to his conclusions based on those first few sentences.
You would be wrong.
I've read the article a couple times now trying to understand why this resonates so hard with some people.
I have tried to bring up what I feel are valid points and the responses are not engaging with what I've discussed but acting like I lack the ability to understand.
I get that attacking me is easier than addressing my points; I have the social skills of a software engineer after all.
I like code because there is no arguing. It's just math.
People on other hand are caught up in emotions and ego, creating anecdotes to fit their biases.
I can't fix the tangled mess of the human mind, but I can fix the crazy spaghetti code those type of people create.
Firstly, anecdotes aren't "created". Anecdotes happen. The reason a singular anecdote isn't accepted as fact is because without a pattern between isolated incidents there is no way to prove that an anecdote is not simply another isolated incident.
Things like this, needing to explain this concept is why I think you don't understand. Your knowledge of English is clearly rudimentary, and you use words you don't understand to explain concepts you understand less.
It is of no surprise to me that someone who doesn't know how to communicate simultaneously doesn't see the value in good communication. You are cog, cogs are not required to do anything beyond what they do.