Does anyone have experience on just "taking" the team organizer slot? My current team meetings are just nuts. A lot of ummms and awkward silences no structure and each runs at least 100% longer than the allotted time. No preparations are made before the meetings. The oldest team member has only been with the company like 1,5 year. I crave more organization

Story of onboarding in the age of Corona!

Monday:
Office is big but almost empty, people are working from home. Guy welcoming me says he is not the one supposed to help me(he is sick I'm told) and the rest of the team is not there. The man I'm talking to is this other guys boss. It's OK I think it will work out.

Turns out this guy helping me is actually the CTO so he does not have that much time on his hands. He shows me were to get my computer and desk and hands me documentation to setup some software.

I spend the time before lunch installing linux, setting up git and some other software. CTO checks up on me once.

Then after lunch nothing...I look for him but he is in some meeting. I find some videos by myself labled "onboarding" on the company website. They are OK. I ask my deskmate if he heard what team I will be in. He doesn't know. I sneak out a little early since I have nothing left to do.

Tuesday:
The CTO is now also sick I see in an email when I arrive at the office. Still don't know what team I am in.

I spend the morning reading coding blogs and websites. After lunch I have a meeting. The only one in my calendar. It's about the product software architecture for all new employees. It's good but still no news about what team. I aimlessly read up on some software architecture untill I go home.

Wednesday:
I arrive at the office first, only the receptionist is there. I listen to podcasts until a few more people show up. I ask another guy if he knows what team I'm supposed to be in. He doesn't but laughs and says it was the same when he started last year.

I send out messages on slack looking for anyone that knows...still no one knows. I guess Im in limbo now. Perhaps i should just start making coffee for people or something...

Switching workplace after new year.
Already told boss I'm quitting last week. And it is like as soon as It was official I lost all patience with the company bullshit and lost the little interest I had left for my daily work. The codebase seemes bad before but now it feel 100x worse.

Work ethic keeps me from doing nothing but man I just want to get out.

Will be so nice to work with a new project and code base.

What is your favourite pasta-code?

I think mine is tortellini/ravioli code. Where someone has taken Object Oriented Programming to the absolute worst extreme. You have loads of seemingly unrelated tiny classes/functions with just a few lines. All split between 30 files to perform one module function

And somewhere is a bug. Bon appetit💋👌

So the development team are being sent very angry emails from a customer.

Reason being that we can't send a release to them because we are waiting for the signing of a document our managment has known about for five months...

While mangement just keeps passing around responsibility and just throws poop. I'm seriously starting to question why middle managers are allowed to exist in a company structure.

I'm two days away from personally calling the CEO then someone gets fired. It's me or one of these middle manager clowns.

I cant keep this inside anymore I have to rant!

I have a colleague that is an horrendous loose bug-cannon. Every peer-review is like a fight for the products life.

Now I understand - everyone makes bugs me included and it is a huge relief when someone finds them during peer-review. But these aren't the simple kind of bugs. The ones easily made when writing large pieces of code quickly. Typing = instead of == or a misshandling of a terminating character causing weird behaviour. These kinds of bugs rarely pass by a peer-review or are quickly found when a bug report is recieved from testers.

No the bugs my colleague makes are the bugs that completly destroy the logic flow of a whole module. The things that worst case cause crashes. Or are complete disasters trying to figure out what causes them if they are discovered first when the product reaches production!

Ironically he is amazing a peer reviewing other peoples code.

But do you know what the worst thing of all is! Most of the bugs he causes are because he has to "tidy up" and "refactor" every piece of code he touches. The actual bugfix might be a one liner but in the same commit he can still manage to conjure up 3 new bugs. He's like a bug wizard!
*frustrated Aruughhhh noises*