some people really seem to think that shitting on the ones who actually do the job solves anything

A BRAND NEW CAR (emoji) 🚗

Another row and column to make an actual bingo card

Return to office mandate and a slice of cold pizza.

Weirdly, after a certain percentage of useless meetings (that should have been an email) it does become more productive to make the AI "do the job": not because it's actually efficient, but an AI is never interrupted for a pointless meeting for hours.

When you work on the same thing for 8 hours a day for years and then suddenly management decides that they need "detailed time tracking."

They just gave you a new job without additional compensation. New responsibilities, no new title, no raise, etc.

Then—months later—they realize that everyone's spending at least half an hour, regularly to figure out how they're spending their time. Some bean counter adds up how much that costs in real money and then—out of nowhere—management decides they don't need detailed time tracking anymore.

I imagine this is a problem mostly for people who do all of their time tracker recording at the end of the week or month or whatever billing period they have. This requires a lot more thinking and time, and thus becomes a problem, compared to just filling it in at the end of the day.

Just a guess though.

Might solve overtime since you always record it, or do you? If you record the overtime you spend on internal projects it's gonna have a bad impact on your ratio of client work to internal work. What you spend 20% of your time on internal projects, your colleagues only spend 10% there - but I work 50h/week instead of 40, but no one looks on this.

Another problem is when your company doesn't have any work for you and you gonna figure out where to book the 8h of doing nothing but waiting for work that day.

Yeah working with timesheets sure is fun work.

We clash! While we try to squeeze every last bit out of our hardware and tools, you are trying to keep us in check and not installing random shit because it might make us 0.1% faster

This. Sometimes it's enough for one person to be OoO and suddenly you can code in silence, work is being done, standups go from 1 hour to 10 minutes. No extra stupid tasks randomly handed out.

I wish that person at my project had at least 3x more paid vacations.

Ingo

You're getting job interviews?

After a point in your career you either learn the skills and get the experience to understand how to plan projects and end up on those groups writing the definitions, or you remain an IC and just code what was given to you.

In the "right" use case, story points should just represent relative effort.

The hours dont matter, its more about ranking how challenging a task is, in order to help the manager rank the priority of tasks.

You should have typically 2~3 metrics:

1. Points, which represent relative effort of the task to the other tasks you are also ranking.

2. Value, how much value does doing this task provide, how important is it

3. Risk, how risky is it that this might break shit though if you make these changes (IE new features typically are low risk since they just add stuff, but if you have to modify old stuff now your risk goes up)

If you have a good integration testing system automated, Risk can be mostly removed since you can just rely on your testing framework to catch if something is gonna explode.

Then your manager can use a formula with these values to basically rank a priority order for every ticket you now scored, in order to assess what the next thing is that is best to focus on.

Story points are evil because they were intended to help teams set achievable goals but are almost never used as such. Once a manager catches wind of this practice, they will bastardize it into a pile of shit most high. Scrum doesn’t prescribe this practice so ditch it. Reject it and move to something only the team members will understand. If you move to relative animal sizes or some shit and you meet your goals, managers can fuck right off.

The point is that if story points=hours, you should just fucking use hours from the beginning.

That depends on your team composition. Decoupling story points and hours means that the points indicate the complexity of the task; each developer might take a different amount of time to deliver that depending on their ability and expertise in that part of the system. The points give you a simple metric to show how much complexity the team have left to deliver, and tasks get assigned to whoever is best placed to deliver them at the time.