FUCKING TIMESHEETS!!!

"Have you got your timesheets?"

NO, I FUCKING DONT, BECAUSE I WAS ACTUALLY WORKING A ROLLOUT, MY FUCKING TIMESHEET ITS A FACT, SOFTWARE WORKS = I WORKED, SOFTWARE DOESN'T WORK FUCK ME IN THE ASS WITH A TIMESHEET!!!!!!!

Started part time job at a company, had to log my time on timesheets. Said fuck this and now the whole company logs their hours on a custom web based time logging system which I built.

Desktop SSD just failed. All VMs lost. Domain admins too drunk to fix. No timesheets no sprint diary no mail no IM.

Red flags in your first week of your software engineering job 🚩

You do the first few days not speaking to anyone.
You can't get into the building and no one turns up until mid day.
The receptionist thinks you're too well dressed to work in this building, thinks you're a spy and calls security on you.
You are eating alone during lunch time in the cafeteria
You have bring your own material for making coffee for yourself

When you try to read the onboarding docs and there aren't any.
You have to write the onboarding docs.

You don't have team mates.
When you ask another team how things are going and they just laugh and cry.😂😭

There's no computer for you, and not even an "it's delayed" excuse. They weren't expecting you.
Your are given a TI PC, because "that's all we have", even though there's no software for it, and it's not quite IBM compatible.
You don't have local admin rights on your computer.💀
You have to buy a laptop yourself to be able to do your job.

It's the end of the week and you still don't have your environment set up and running.
You look at the codebase and there are no automated tests.
You have to request access every time you need to install something through a company tool that looks like it was made in 2001.

Various tasks can only be performed by one single person and they are either out sick or on vacation.
You have to keep track of your time in 6 minute increments, assigned to projects you don't know, by project numbers everyone has memorised (and therefore aren't written down).
You have to fill in timesheets and it takes you 30 minutes each day to fill them in because the system is so clunky.🤮

Your first email is a phishing test from the IT department in another country and timezone, but it has useful information in it, like how to login to the VPN.
Your second email is not a phishing test, but has similar information as the first one. (You ignore it.)
Your name is spelled wrong in every system, in a different way. 2 departments decide that it's too much trouble, and they never fix the spelling as long as you work there. One of them fixes it after you leave, and annoys you for a month because you haven't filled out the customer survey.

They've told me I'm going to have to start doing timesheets.

When should I tell them I'm going to start producing work much more slowly?

Yesterday I worked 27 hours on a task.

Current workload as dev lead:
- 1% actual development
- 2,5% waiting for SaaS to load
- 2,5% cursing company server network connectivity issues
- 5% switching VPNs
- 7,5% pkg management & deploys
- 10% writing JIRA and support tickets
- 12,5% filling in timesheets
- 15% coaching & reviewing a bot coworker
- 19% doing 2FA, refreshing expired passwords
- give up and spend the remaining 25% doing something meaningful

Timesheets, timesheets, timesheets. Business bureaucracy. Stuff like this is just a way to prevent any real work from actually getting done.

I know im being unreasonable but fuck that noise.

Timesheets were made so that managers can be little dickbags and make a big fuss over the half an hour doing something that someone else asked you to do, instead of something they wanted you to do.

Its also a good way to force employees to become their own managers when you arn't giving them work, so you can have more time to sip tea while they scramble to find out how the fuck they will get their hours for this week with no direction being given

Timesheets are gonna be the death of me. Ugh.....

company policy was to bill in 10 min increments to a contract whose deliverables you were executing on, this was federally mandated. they never told us where to bill the 5+ hours of meetings per week we had on "technology". every time i asked i was told i would be "gotten back to"

I actually like where I currently work, sure it has problems and some office politics. The work is not always exciting but what makes it good is not having someone breathing down my neck about timesheets, noone cares if the hours you work are not exactly business hours and a bunch of other stuff.
What I really like though is having a boss who backs my judgement. If I refuse to commit to timelines or work without being given the information I need he'll support me. I've had too many yes men as bosses which always ends up with the devs coping all the blame when everything goes belly up.

Time sheets. I'm not a fan of our task management system, you don't check out jobs or tasks like moving cards on a kanban board, it's more of a loose, calendar-based setup. We're also in a small, open office so it can be difficult to remember to log things in the software when you could tell the person opposite you that their task is finished. On top of that a lot of the time it takes me longer than the scheduled time to get a job finished as I'm learning a lot of new stuff, so digitally documenting things like that worry me a little. I don't want to look like I can't hack it just because a job takes me longer than my much-more-experienced colleagues.
I should note that I understand it's all incredibly useful data to the company, but I hate doing it and it's very easy to forget or ignore.

Walked in to work with an email subject "timesheets" and a calendar appointment to "explain".

Well. That's me in a pissy mood all day. Guess what's coming ...

Arse. Arse. Arse.

One manager at the Client company tells us that unless we submit weekly timesheets we wont get paid.
We are not their employees, nor do we have an agreement with them for full time work.

" Whole thought process is to structure the engagement better ,so that we can implement better governance and provide better visibility."

 Anyone understand what is being said above? Jargon.

Timesheets and Formations:

Every week, I'm supposed to fill out a form detailing how much time I've spent on which projects... I'm a research engineer assigned to a single project, so I'll always fill every day with 8 hours on the same project, because if it yields to less than 39h the website gets mad at you (even though I'm paid on days, not hours).
I get why it's here, I just don't get why it's my responsibility to declare which project's budgets should be liable for my salary.

As for the formations, they're always these extremely slow paced, completely obvious type of courses that borderline murder you with boredom. Yes, I know, corruption is bad, can I get back to work?

I really need to get my head out of my ass. I've been pretty useless the last while. My timesheets are a week behind because I'm honestly not sure what I've been doing.

Today in particular I'm tired af though