u/Think_Possible2770

The contractor billing $250/hour works 12 hours a week. He's more productive than every full-time engineer on the team

We hired a contractor to help with a backend migration. His rate was $250/hour. He billed roughly 12 hours a week. The CFO flagged it during a review: "Why are we paying someone $13K a month for part-time work?"

I pulled the numbers. In his first month he closed 34 tickets. The average full-time engineer on the same team closed 19. He didn't attend standup. He wasn't in Slack during business hours. He never went to retro or sprint planning. He just read the tickets, shipped code, and left

His code quality was consistently above average. Fewer revision requests than anyone except our most senior IC. He never introduced a regression in 6 months of work

At one point someone asked him to join the daily standup "for visibility." He said no. He said he'd rather spend that 15 minutes writing code and that he'd send an async update at the end of his working block instead

Management eventually decided not to renew his contract. The reason given was "cultural misalignment." The real reason was that he made a room full of full-time engineers with equity and benefits look slow by comparison, and it was uncomfortable for everyone involved

He now works for our competitor. Same rate. Same hours. Their loss metrics went up after he left. Ours went down

reddit.com
u/Think_Possible2770 — 1 day ago

I write code slower than AI now. I also catch bugs the AI doesn't. My manager only sees the first part

Since January my team started measuring output by PRs per week. Not by choice. A VP installed a tool that tracks commit frequency, PRs merged, and lines changed. Everyone pretends it doesn't affect behavior. It affects everything.

I'm a senior engineer. I read the codebase before I write. I think about edge cases. I review other people's work carefully. I catch things that would break in production but pass every test in staging. Last quarter I caught a race condition in someone else's AI-generated PR that would have corrupted user data for about 800 accounts.

My PR count is the lowest on the team. The dashboard shows this in red. Literally red. My manager mentioned it in our 1:1 last month. "Your output has been lower this quarter." I pointed to the race condition I caught. He said "right, but that doesn't show up in the metrics."

The engineer with the highest PR count ships fast and breaks things regularly. He generates code with Claude, submits it, and moves on. His reviews are superficial. His bugs get caught by people like me. Then he fixes them in another PR, which counts as more output.

He got promoted last cycle. I didn't. His dashboard is green. Mine is red. The metrics are correct. The metrics are also useless.

reddit.com
u/Think_Possible2770 — 6 days ago

I automated my entire job and didn't tell anyone for 6 months. Then my boss found out

I work as a data analyst. For a long time, 60% of my day was just pulling the same boring reports and formatting them. The rest was just answering basic questions about that data

So, I decided to work smarter. I wrote some Python scripts to handle the reports and built a Slack bot to answer the easy questions

Suddenly, my 40-hour work week turned into 4 hours

For the next 6 months, I used that extra time to learn new things and do deep, detailed analysis on projects I actually cared about. I didn't tell anyone; I just kept delivering my usual work on time

Eventually, my manager noticed. Not because I was slacking, but because the extra projects I was doing were actually really good. She asked me, "How do you suddenly have all this time for deep dives?"

I decided to be honest. I told her everything

She was dead silent for about 30 seconds. I thought I was getting fired. Then she looked at me and said, "Can you do this for the other four departments, too?"

Two months later, I got a raise and a promotion. My scripts are now being used across the whole company

reddit.com
u/Think_Possible2770 — 7 days ago