Our culture only focuses on negativity and using reporting that randomly provides bad data. Wonder how long before employees are laid off due to this c r a p.
11 replies (most recent on top)
It is passé to complain about hours on the RTO report. Jeremy told us it’s now about checking in code. If you are not programming and checking in code once a day, you are not a doer it doesn’t matter how many hours you are here or not, you will soon be let go if you are not coding.
Just make sure you check your info. I did have an error in mine, so I just had to submit the info.
I looked at my RTO report after reading this and know my boss lacks any skills to defend anyone but herself .
This is a tool to be compiled down the road with corrupt data and create a bs rating at EOY.
The data is totally accurate. I would defend it.
March data is inaccurate. Had me leaving 2 days an hour earlier than I do and 6 days working 9.5. (I only 8-&-skate)
review the results with your supervisor and then ask your supervisor's supervisor.
Domestic L2s report devs are purposely sabotaging the reports. They are part of the resistance.
They can’t fire you based on flimsy data. But they want you to resign. They will harass you and threaten you with layoffs and possible termination for not following RTO.
Paper Samir and Paper Sandeep are currently looking into said bugs.
At such of time when real people come to office, we will do the needful and check the codings into github.
Does pretty defend inaccuracies?
The march data is pretty accurate