The move came after 404 Media published an investigation into how Proton CEO Andy Yen was aggressively pushing AI across Proton despite security concerns and the culture of fear he has created.
Everyone needs metrics and targets, otherwise it is just dicking around and nothing useful gets done.
The problem it that tech bros only half listened in social sciences class and choose the dumbest metrics and targets. Agile completely killed waterfall and specification development. In turn, using the equivalent of ignorance of the masses ticket systems on Jira. The worst of all worlds with commits, PRs and lines of code as metrics and a vacuous tick mark on user stories as goals. No wonder software development has been hell for decades.
Software developers need to stop designing in the code and go back to designing on paper against specifications and unit tests. Thinking has always been the main work of a software developer, not just writing code. As for the AI side of the problem, the purpose of code is not just to be written, but to be read and understood by humans. AI coding trashes the ontological purpose for the existence of code.
Middle managers like to set targets and goals because it counts towards their bonus, and it looks less like they’ve got their dick in their hand when the boss comes calling.
No one “needs” anything to do their job. A brief is helpful, a deadline is worth taking note of, but anything else is just interfering with people who are genuinely there to just do the job.
Most productive jobs i ever had? The ones where i was asked to do something and then allowed to do it.
As to the latter part of your message, it feels like you’re just trying to process something so i think I’ll just leave you to it. It’s a bit too non-specific to respond to though.
People need a metric shitton of things to do their job well. When you’re told what to do, that’s a goal. If you’re told a deadline to fulfill, that’s a metric.
I understand that people have taken the words in an exclusively derogatory mode. But you need minimum those two things to do any job. Else you’re just a nepo dickhead who gets paid for parading around an office and you’re the piece of shit interfering with the people who actually do have jobs to do.
People need a metric shitton of things to do their job well
That’s hyperbole. There’s a lot of things that would help a great deal, but can he done without.
When you’re told what to do, that’s a goal
No, thats a brief. A goal is “the dashboard released on time”
If you’re told a deadline to fulfill, that’s a metric
That’s a goal. A metric is “1000 lines of code” or “300 sprint points”
But you need minimum those two things to do any job
Nope. That job where a team of 3 was running like 5 websites was self-run. The CEO came to us with questions and briefs and the rest of the team made requests, and we prioritised them and did them in the most efficient order possible.
paid for parading around an office and you’re the piece of shit interfering with the people who actually do have jobs to do.
Sounds like management to me. Nothing produced but complaints, meetings and powerpoints.
Middle managers like to set targets and goals because it counts towards their bonus, and it looks less like they’ve got their dick in their hand when the boss comes calling.
It’s the same problem all over. Capitalism. You have people who don’t do work keeping the benefits from the work.
Most people aren’t going to give themselves stupid or useless metrics. Software people aren’t going to impose “tokens used” or “lines of code” metrics on themselves. They know those are stupid.
Everyone needs metrics and targets, otherwise it is just dicking around and nothing useful gets done.
The problem it that tech bros only half listened in social sciences class and choose the dumbest metrics and targets. Agile completely killed waterfall and specification development. In turn, using the equivalent of ignorance of the masses ticket systems on Jira. The worst of all worlds with commits, PRs and lines of code as metrics and a vacuous tick mark on user stories as goals. No wonder software development has been hell for decades.
Software developers need to stop designing in the code and go back to designing on paper against specifications and unit tests. Thinking has always been the main work of a software developer, not just writing code. As for the AI side of the problem, the purpose of code is not just to be written, but to be read and understood by humans. AI coding trashes the ontological purpose for the existence of code.
Middle managers like to set targets and goals because it counts towards their bonus, and it looks less like they’ve got their dick in their hand when the boss comes calling.
No one “needs” anything to do their job. A brief is helpful, a deadline is worth taking note of, but anything else is just interfering with people who are genuinely there to just do the job.
Most productive jobs i ever had? The ones where i was asked to do something and then allowed to do it.
As to the latter part of your message, it feels like you’re just trying to process something so i think I’ll just leave you to it. It’s a bit too non-specific to respond to though.
People need a metric shitton of things to do their job well. When you’re told what to do, that’s a goal. If you’re told a deadline to fulfill, that’s a metric.
I understand that people have taken the words in an exclusively derogatory mode. But you need minimum those two things to do any job. Else you’re just a nepo dickhead who gets paid for parading around an office and you’re the piece of shit interfering with the people who actually do have jobs to do.
That’s hyperbole. There’s a lot of things that would help a great deal, but can he done without.
No, thats a brief. A goal is “the dashboard released on time”
That’s a goal. A metric is “1000 lines of code” or “300 sprint points”
Nope. That job where a team of 3 was running like 5 websites was self-run. The CEO came to us with questions and briefs and the rest of the team made requests, and we prioritised them and did them in the most efficient order possible.
Sounds like management to me. Nothing produced but complaints, meetings and powerpoints.
It’s the same problem all over. Capitalism. You have people who don’t do work keeping the benefits from the work.
Most people aren’t going to give themselves stupid or useless metrics. Software people aren’t going to impose “tokens used” or “lines of code” metrics on themselves. They know those are stupid.