Learn More
Resend Email
27
darkney
5y

Today a new person joined the team.

Started bitching about the entire team for not having documentation for our already written code and software.

Asks the manager for a new task that he can take up so that he can write documentation for all our already coded works.

Manager says Go On.

Troubles me with 400 questions every 3 minutes in the name of Knowledge Transfer for writing his documentation.

Sends a proud mail to the team for writing this new documentation that no one else had time to do.
He is a newbie and had no other task to do anyway.

I seriously don't know if I should feel proud of him, for writing new documentation,
Or if he's doing this to defame me.

The team is filled with snakes.

rant

senior

team

new person

snakes
Favorite
Ranter
Comments
  • 3
    5y
    @rutee07 because he sends a mail to the entire team that he has done something that I have not done at all (in a proud fashion and mentioning my name on the mail). Portraying as if I never wanted to help the team.
  • 20
    5y
    Somebody is attention horse
  • 18
    5y
    Shoot the attention horse.
  • 7
    5y
    The perfect word - Attention Horse.

    Whoever coined this word, deserves a cookie 🥠
  • 10
    5y
    If the team had written docs, the knowledge transfer wouldn't have involved 400 questions. Next time, it won't.
  • 9
    5y
    @Fast-Nop agreed, however the dev's speech as OP is saying makes me think he has an ego issue.
  • 9
    5y
    I hate writing documentation. But it's necessary and very helpful.

    I would've done the following:

    Set up a meeting for him once/twice a day at a time of your choosing. Ask him to prepare all the questions for the documentation beforehand and ask him to come prepared for the meeting. If he has new questions, he should list them and ask them ONLY in the next meeting.

    Emphasize the importance of the concentration of a developer and send the meeting and emphasis information in an all-in-one email including him, the management and other relevant devs who would need to be in said meetings.
  • 3
    5y
    Quite a typical newbie dev on the autism spectrum. When I was young I’ve also made many similar comments, not realising these were serious personal attacks.
    Can you send him a tip from someone experienced joining a team multiple times?
    You don’t complain in the first few days, because the real wtf’s are the things that noone wants to talk about during your introduction. These are the things you should complain, but only after you understand what the main objectives of the team are.
  • 2
    5y
    Maybe just write some docs next time yourself? Regardless of other people.
  • 6
    5y
    Beware, he may write some unit tests next
  • 0
    5y
    cool
  • 2
    5y
    Whoever spend time writing documentation is the champion. You should be proud of him.

    He’s not a newbie. He’s an experienced who knows how important of documentation is. Give him a medal or a pizza.
  • 1
    5y
    I haven’t worked with anyone who could actually write a readable documentation. Writing skills are rare amongst programmers. Outdated, crappy docs are often worse than nothing.

    I must see his results, before giving him a pizza.
  • 1
    5y
    It always scares me when there’s a new member and they are or they have potential to be better than me! Just makes me feel old.

    I just hope they’re not as attention seeking as this horse. 💆🏻‍♀️
  • 1
    5y
    I agree that being bombarded with questions is a huge time suck and kills your productivity.
    .
    .
    .
    .
    .
    But you need docs dude. Props to this guy for taking initiative and doing it because you obviously don't have the time, he definitely didn't need to come off high and mighty or overly proud for doing what was asked of him (even if he asked to do it).

    Plus he probably has a pretty good understanding of the system now.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment