It's really just the font I hate. In the past I've used Reader Mode in Firefox to make it readable, but just now I went into Ublock Origin to change the font to something I like, using the suggestions from this Reddit thread: https://www.reddit.com/r/uBlockOrigin/comments/r4gzzl/how_do...
pluralistic.net##*:style(font-family: Fira Sans !important)
If you like your default browser font, you could instead just unset it:
It's not so much the font as it is the lack of separators for me. There's no lines or anything separating one article from the rest, and when I click continue reading it takes me to the heading of that article in the page for that day rather than a separate page for the article. These two things are specifically what bother me.
I normally hyphenate such expressions when they function as adjectives: "white-collar workers". Obviously I'm a bit "old-fashioned" in that respect. (I may also be old.)
White is modifying collar, not race, in this circumstance, and in this case also affects other workers (as he explicitly says in the article.) The point was that this Taylorism now affected the group of people historically immune to it.
Not sure if it is. The article has a pretty good body of real-world evidence of the supposed curve, and I’ve personally had a colleague let-go because of the information gathered through “bossware.”
> or, more formally, "any target becomes a measurement" (AKA Goodhart's Law).
nit: it's better stated as "any measurement becomes a target".
Reading the article, I had a pang of hope. If it's really as anti-effectual as described, perhaps just everyone needs to buy mouse jiggling dongles and the push behind the immediate trend will lose momentum.
Or really, it's just another step in the corporate-Keynesian make-busy-work economy that has gobbled up most of our productivity gains for decades.
> Successful shitty tech rollouts start with people you can abuse with impunity (prisoners, kids, migrants, etc) and then work their way up the privilege gradient.
There's an election coming up in Sweden.
One of the parties is literally advertising their platform with "more security cameras on our streets" (Moderaterna), and every party is keen to expand police power to have more surveillance and wiretapping without prior criminal suspicions (at least according to the "Election compass" on SVT: https://valkompass.svt.se/2022)
> Mazzoli seems to have either not used his product, or, if he did, did so under conditions where he was in charge of it – using it the way an athlete might use a stopwatch to time their own sprints, and not the way a boss might: to decide whether to dock your pay or fire you.
> This inability to understand the difference between using a technology and having the same technology used against you is endemic to the industry.
I think this is a key failure of understanding for the "tech is neither good nor bad!" camp: just as the Death Star clearly was never going to be used for mining planetoids, it's very clear how workplace surveillance tech will be used to harm workers, if nothing else because of how it is currently being used. Continuing to work on such tech just because it could theoretically be used for non-evil purposes is morally bankrupt, and something the industry needs to establish ethical standards to prevent.
semi-randomly, I was reading about the colonial Spanish mining city of Potosi in the South American Andes today, before opening YNews. The Spanish Viceroy (administrator for the King) oversaw the conscription (slavery) of 1 in 7 adult males each year, over a vast area, to service the poisonous and intensely profitable silver mines. Stories of courage and death predictably follow, while the administrators, unconnected to the daily life in the mines in that region, made record profits, among the largest wealth in Europe at the time (late 1500s). Comments on the social structures that supported that, left as an exercise to the reader.
Consider history; Do you think for one minute, that a Viceroy somewhere, and legions of new administrators, won't inflict endless and strictly enforced conditions on anyone they can find, using software?
Yeah, if tech is developed with the explicit purpose of surveillance on workers, it's definitely not some dubious case where "well maybe it's done with good intentions". Nothing good comes from putting extra mental strain on your workers, showing you don't trust them and being an invasive boss overall.
This stuff is worse than the Death Star. At least that thing made no pretence about helping its targets. I cannot fathom how much my mood has dropped on reading about Bossware. I'd do pretty much anything in my career to avoid it.
I was referring to some material from the no-longer canon Star Wars Extended Universe, where it was referred to during development as the "Imperial Planetary Ore Extractor", and some characters working on its design genuinely believed (due to brainwashing) that the Death Star "was developed to break up dead, lifeless planets to extract the valuable ores and elements within". https://starwars.fandom.com/wiki/Qwi_Xux
Of course, if programmers are raised from a young age and brainwashed into believing that workplace surveillance is innocent / good, that's a different problem than adults who should know better when it comes to the real world results of using the tech they are building.
This made me think about other tech that has no good use. Flamethrowers come to mind. Not the fun ones that Elon will sell you as a gimmick, but the ones that toss sticky flammable liquids at people.
I was listening to someone describe their use in WWII, and he was I suppose trying to defend it by saying that actually most of the people it killed weren't burned at all, but rather killed because they were in enclosed fortifications and apparently flamethrowers produce prodigious amounts of carbon monoxide - basically you'd take a couple breaths and it's over - the carbon monoxide will bind into your blood cells such that even if you immediately step out into fresh air, you're a dead man walking. But at least your corpse will be recognizable for your friends and family I suppose; you won't be burned beyond recognition.
But building a reliable flamethrower is an interesting technical challenge, so I'm sure you can find an engineer who will be willing to give it a go.
Once upon a time, I worked for a shop that did auto insurance. This involves handling a lot of fairly sensitive data about people and datasets about a lot of people, for reasons that boil down to it being incredibly useful data for actuarial purposes.
Bossware, or working machine monitoring software, endpoint monitoring, or whatever turned out to be a key part of making it possible for our data scientists to function. At all. It was the only way we could both protect the incredibly sensitive information about lots of people while allowing analysis work to proceed.
Aside: anyone who wants to talk about doing data analysis without access to the underlying data is cordially invited to explain how to do this to statisticians who only understand R and local Jupyter notebooks.
"But wait!" you protest, "Can't the business work just as well without that sensitive information?". That's a good question! The short answer is no. No, it cannot, and unfortunately there's a great deal of actuarial history behind this.
"But wait!" cry you, "Could you have not simply trusted them?". That's also an excellent question! To which the uncomfortable response runs roughly: how comfortable do you feel with "we trust them" as the primary security controls when some company has your data? Especially when that trust means you might not even know about a breach? How do you think a regulator concerned with privacy would look at "we trust them" as a security and privacy approach?
Unfortunately, I think some forms of bossware serve a purpose. Sometimes it's one of the few options available that enables trust beyond the directly interpersonal.
I think there is certainly a place for audit trails etc, but it again comes back to how that data is used. An access log is an access log, but it's a difference if you analyze it to find people looking at data they have no reason to look at, or if you analyze it to track who spends how long on their toilet break. And a lot of what's offered by current "bossware" clearly falls in the latter category.
I agree. My goal here is to set out that there are important uses for monitoring. Uses important enough that it would be irresponsible to discard the notion entirely.
> Aside: anyone who wants to talk about doing data analysis without access to the underlying data is cordially invited to explain how to do this to statisticians who only understand R and local Jupyter notebooks.
Provision some isolated machines with access to production data, and let the data scientists login remotely. You'll be able to tell who is accessing the data and when, and won't need to install invasive bossware on their systems. It's a fairly straightforward solution. It's one thing to control access to sensitive data. Its another to use that to justify monitoring employees all day, even when they aren't accessing sensitive data.
Now you need to convince them to use this system. You also need to convince them to not use this system, where they're injecting arbitrary code into the sandbox remote machine, to download the data to their local machines where they can work in the way they understand and are comfortable with. Inevitably some person will react badly to the perceived lack of trust or object to what they see as making their job more difficult for no reason.
There are a lot of options for monitoring for that kind of thing. You monitor the remote machine, you monitor the network traffic between it and their local terminal... and the most valuable will be monitoring their local machine to associate with the rest of the access and usage information. Among other things, you need to be able to distinguish between someone using the data scientist's credentials and the data scientist using their own credentials.
Your idea is a wonderful approach! It improves security, privacy, traceability, and auditability. It may not be the same as removing the need for endpoint monitoring, unfortunately.
You can never perfect endpoint monitoring. At the very least, the engineer could see data, go to the bathroom, and write down what they saw on a scrap of paper. As long as eyeballs see data this is possible no mater what software you install on device, or even if you have an armed guard sitting in the office right behind the engineer.
Yeah, do people really want no supervision on employees handling their PII or other sensitive info? I think I would be upset if I found out my info was not even being attempted to be protected while in an employees possession.
I worked as a bioinformatician at a medical device company. We did genetic testing on cancer patients, and had huge amounts of private, personal information on the patients we were testing, because it was necessary to provide the correct clinical determination.
We also didn't have bossware. There were access controls on the data itself, audit trails on who accessed the data, but no software running locally on my personal dev machine looking at what I did at any particular moment.
HIPAA governs the storage, transport, and use of that health information, and we all knew we were criminally liable if the information got out.
Bossware in a HIPAA environment (or other environment where not having leaks in important) can be more of a liability than a boon, because it becomes yet another vector for attack or data leakage. You are in effect sharing all data a machine can access, with the maker of the bossware.
Something with the teeth of HIPAA but for other pieces of personal information could go a long way. It's amazing how differently executives behave when the consequences of data leaks change from "customers could be unhappy if they found out" to "I could personally go to prison".
> It was the only way we could both protect the incredibly sensitive information about lots of people while allowing analysis work to proceed.
Meanwhile this data is getting leaked every other week by other companies. Didn't Equifax leak pretty much all sensitive information for the entire nation. What happened there?
I haven't formed a constructive thought out of all this yet, I'm just frustrated that we'll get surveillance software to allegedly protect data that's already been leaked by a hundred other companies.
Often this will be like the "think of the children" argument. Of course we should be concerned about security and make efforts to protect data, but many times the same people who push surveillance software in the name of security will later turn a blind eye to other security practices or concerns that might be an inconvenience to them. Their concern for security will extend only as far as it gives them power.
It's very often different companies and different systems. It's rarely the companies with mature and well-implemented security, privacy, and governance systems that do Equifax-style data spills.
To draw an imperfect comparison - improving the efficiency of electric car motors does little for those driving dino-juice-mobiles. That we as a society have the tools and ability to do better does not mean that every person and organization adopted them immediately and perfectly.
> anyone who wants to talk about doing data analysis without access to the underlying data is cordially invited to explain how to do this to statisticians who only understand R and local Jupyter notebooks.
Joint distributions and generating functions trained against the production data to generate synthetic data, generally.
> it's very clear how workplace surveillance tech will be used to harm workers
My takeaway is not just that that, but that it will be used to harm businesses as they train their employees to do the measured thing over and above the best thing for the company.
I suspect most people here could envision this as an extension of a "Lines of Code written" based performance metric and intuit the likely outcomes.
Damn, I had some fairly old opinion of Doctorow where I disliked him for some reason or other, but I am definitely revising that. I thought this was a great article.
I am certain “bossware” will accelerate the downfall of already shitty workplaces.
Very happy to hear Amazon is doing away with it. Strongly hope their workers unionize anyway. What kind of employer nickle-and-dimes a worker’s bathroom breaks? Not a good one, that’s for damn sure.
I used to see these job postings on LinkedIn for Crossover for Work. I was intrigued by the claim of $400yr salary. Glad I didn’t end up working there. Thanks but no thanks, I am not going to work actively oppressing already downtrodden workers. A quick search turned up this fascinating article as well: https://medium.com/@whistler_12777/heres-why-crossover-is-a-...
Fuck bossware. Fuck people who work to actively oppress others. Humanity for all, value of life for each and every person out there.
There are some strict time-keeping requirements for bathroom use when it comes to certain contracts, like government ones. It wasn't too bad, but I forget the specifics. It was like it had to be less than 5 minutes, or you use your 15 minute breaks or lunch for anything longer.
100% - At my last company we had an unlimited sick policy. Wonderful for everyone - don't even question staying home if you're remotely ill. Well, it was wonderful until one employee was sick every Friday and Monday and some. We ended up having to adjust the company policy for two weeks sick time and beyond that required a doctors note. The employee continued their pattern and once they hit their two weeks of sick time off they couldn't provide a doctors note for further time off and ended up getting let go after continuing to call in sick. The company had benefits covering if folks needed counseling, substance abuse issues, etc... which were offered to the employee but they never took advantage of it.
You didn't have an unlimited sick policy. You had an undocumented limit. Documenting it lets people know where they stand and protects them in the event they need to take sick time but the boss wants to punish them for it anyway. It also means there's one standard for everyone, rather than people being treated in a discriminatory fashion (you get three weeks, but Samantha gets one).
But isn't this how it always goes? There's an informal policy because writing up every single thing in a contract is tedious for both parties. Then someone comes up and figures "hey, free vacation, I'd be stupid not to take advantage".
So, they do take advantage for a while, until everyone realizes they're a jerk, so now everyone has to go through the new "process". Because they can't just be fired "for taking sick leave", which "is their right".
It is also a response to handful of people who (rightly) want to get paid for their 3-5 minutes each clock in to open a shop. When you are negotiating 5 minutes this way, then the corporate negotiates 5 minutes that way, and pretty soon it is a legal contract. Of course the corporate should pay for the minutes to open the shop, and some would fix this on the first discussion, but others would pull in the lawyers, because hey that's our culture.
Extrapolating here ... employee wants 5 minutes of bathroom breaks because it was not in contract and the manager abused it, so when the 5 minutes gets written into the contract, then the manager can still abuse it by writing you up for a 6 minute break, or just refuse to help you out today because he did not have a good experience with you or someone else yesterday.
We are losing the human touch due to both-sided legalese in everything.
They file for reasonable accommodation and the idiots who get concerned about your bathroom time have to be quietly told to stand down because you have special permission to poo.
It can get more absurd as well. There’s an unlimited about of goldbricking and bullshit that people are capable of.
Exactly. Suddenly your imaginary worry about someone's 10 minutes of lost productivity is a class action lawsuit under accessibility legislation that will probably burn you for 1000x that cost or more and leave your reputation, ironically, in the toilet.
Or being female and unlucky with the effects of your cycle.
Or just having a rough day because something you ate was bad.
It's one thing if there's an ongoing pattern of long, unexplained breaks and someone's line manager has a discreet word about it and asks if there is anything they need to know. However routinely messing with things like breaks or availability of kitchen and bathroom facilities is surely one of the most counterproductive policies an employer could adopt. Nothing says we respect and value our people like treating them as subhuman!
Bathroom breaks would have to get extreme before management has the slightest place in bringing it up as an issue. Anyway, if someone is getting their work done, why does it matter how many breaks they take?
Sometimes people do abuse the system. Sometimes they have a real medical issue. Sometimes they're being treated badly at the office and they're just desperate to get out of that environment and don't know how to tell anyone or get help. It's not always obvious what is happening or why.
Any of these situations can mean someone isn't getting their work done. Their colleagues might be left to pick up the slack, which isn't fair on them either. Any of the people involved might start to worry or get upset about the situation, which can make things worse.
Whatever is going on it's management's responsibility to figure it out and then deal with it professionally and with appropriate discretion and sensitivity. The difficult part is figuring out what that looks like when the situation could be delicate and there might be anything from very personal medical issues to criminal behaviour involved.
Yeah I think that type of policy is mindlessly impossible by Legislative branches under the guise of eliminating "waste" no pun intended. When in reality all those policies do is eat into the mental bandwidth of government works and contractors. There are good regulations and than just dumb ones. And you might ask what law exactly is the Legislative passing but its not laws its appointees to executive positions that run larger organizations with an agenda with actually understanding the organizations mission or purpose
Everyone on the likes to pretend that rules and regulations are either a) a boondoggle net-negative exercise in cost cutting b) "wRiTtEn In BlOoD" depending on whether they like the procedure or regulation in question.
Reality is often far more mundane and dysfunctional. It's frequently just speculative bike shedding and ass-covering, exactly the kind of "pointing out exploits" stuff the HN crowd loves to engage in when it comes to policy as though organizational policy was a firewall to configure.
Here's how it probably went down: Some people were hammering out the language of a contract and some bike-shedder replied to all pointing out that breaks, work stoppages, lunch, etc, etc, were all being counted but bathroom breaks weren't and that potentially created an exploit to the proposed system of cost/time/whatever tracking. No party had the balls to take responsibility and say "this is silly, we'll cross that bridge if/when we get to it" bathroom breaks wound up incorporated that into their formula. So thanks to some bike-shedder trying to "contribute" and nobody's willingness to take any risk whatsoever (by going on the record brushing aside a petty concern that could come back to bite them) everyone has to track their piss breaks. And to be fair, all these people are doing exactly what they are incentivized to do (!!!). And these aren't the kind of things you can roll back later because then you have to explain why you're a) deviating from established way of doing things and b) accepting some risk in doing so which nobody wants to do for a variety of reasons that have been discussed at length and are outside the scope of this comment.
Source: This crap happens like quarterly in my workplace.
Edit: of course there's other potential complications that can effect these kinds of things but you get the gist.
I have written many government contracts and I can tell you that there are no federal timekeeping requirements that would mandate that level of granularity.
Some contractors record a lot more detail than their contract requires. I've worked on government contracts. One workplace had a timekeeping system for DOD and a separate one for the corporate overlord. The latter was much more detailed. It was a pain to fill out multiple time cards.
I can imagine somebody somewhere spent their whole days in the bathroom and management in its infinite wisdom, instead of (or in addition to) firing the dude instituted this sort of smoothbrained policy.
This is the unintended consequence of anti discrimination laws (and other laws, like those protecting unions, that defeat at-will employment). Easiest way to fire shitty employees is to document a bunch of technical rule violations. That will create a rock solid paper trail that will stand up in court. Otherwise, they will claim some kind of discrimination and it’s your word about their performance against theirs calling you a racist/sexist/whatever.
You talk as if the corporations havent kept squeezing more labor out of their employees throughout 20th century. Regardless of any laws and regulations. They would keep doing it even if anti discrimination laws did not exist. They may be using that for an excuse now. They would use another excuse to make people work until death if there weren't any such laws.
That's some pretzel logic there. They can't arbitrarily implement/enforce rules without first disclosing them, and it looks bad in a court of peers if they start doing this haphazardly. I would actually say it's easier for them to get away with this in an at-will environment without these rules.
"Position was eliminated" works pretty well (in the US).
It’s great that you think that, but what I described is what the government does (because of civil service protections) and what every sane HR department with a high legal risk workforce does. Any US employment lawyer would advise that you follow this practice.
What world do you live in where anti-discrimination laws aren't already aren't already utilized by the employers you've referenced? It's really hard to get fired as a US Federal Government or Union employee (based on what I've seen from both in a Midwest state, for United Auto Workers) and the EEOC has had historically strong support for employees for the entities I've cited.
Private entities will do what they've always done and my original comment succinctly describes the default outcome. Nothing has changed.
Unless you also happen to be recruiting for that same position, or if your local legislation asks that you prioritise relocating your current employees in other jobs over firing them if their position disappears.
The goal is to keep it out of court or some other tribunal.
Without a contract, discrimination law is the sole course of action to fight an adverse employer situation.
Eliminating a position leaves a company open for problems, particularly if it isn’t true. Much easier to determine that you didn’t charge vacation time correctly or violated a series of minor/moderate rules.
Attempting to circumvent anti discrimination laws by documenting and firing over technical violations only for the class you aren't allowed to discriminate against doesn't improve the legal situation vs simply discriminating more straightforwardly and firing without cause. Firing for cause rather than without can avoid severance payout though.
In theory but most plaintiffs employment lawyers (working on contingency) aren’t going to invest that much time and money for a run of the mill anti discrimination lawsuit.
I knew a lawyer that did workers comp and that's how he ran his firm. He kept a private file on every employee since they started to cover his ass waiting for when he wanted one gone.
This is the result of managers who have no idea how to do the tasks of the employees they are "managing". E.g., non-technical manager managing technical employees who uses silly metrics like LOC because he/she has no idea how to evaluate the employee's performance.
Also, upper management somehow feel that their middle and lower managers can be trusted to act like adults while the people who do the actual work cannot be.
The proper solution is getting rid of management, and letting workers get their jobs done.
It’s not about management, it’s about convincing a jury that knows absolutely nothing about your company and industry except what two lawyers argue to it.
That’s interesting. Do you have a reference for that?
With workplace control seeming to predate worker protection by a century, you wouldn’t expect that. But it’s always exciting when intuitions get subverted. I’d love to read more of how the historian who proposed this put together their argument. Do you have a link handy?
> and other laws, like those protecting unions, that defeat at-will employment
This is backwards. Union membership is at its all time low and at-will employment has mostly taken over. A union would be the best tool to curb "boss-ware".
Union membership is down but anti-discrimination laws are as strong as ever. I was just saying that in companies that are unionized, there is a strong incentive for management to turn to rigid rules and documentation of minor transgressions.
Read some of his young adult fiction, then get all gag-me-with-a-spoon over the coming of age stuff. (But then stay for the occasional afterward by Bruce Schneier…)
You may enjoy Terry Gilliam’s The Zero Theorem.
Peloton will eventually start climbing the STAC ladder (it’s literally their only remaining move). Between that, permanent covid mitigations and the office-space downsizings of the late 2020’s, Gilliam’s vision will be complete!
He makes good points and has a clear set of beliefs that he applies consistently, especially on topics like this, but gets a little overbearing if you follow closely.
Yea, I suffer from serious oppression and inequity narrative fatigue. I couldn't really get past the first few paragraphs. Sure there is inequity between workers and their management. But first off, it's not always tilted towards management. There are many indexes on which we can measure how one party fares over another. But anyone who is moved to write about inequity only assumes a single index and that management is always oppressive and employees are always helpless and oppressed.
Secondly, the longer I have been a participant of society and markets, I've come to realize that power imbalances are as affected by how much the participants stand up for themselves in the face of power grabs as it is how much other participants grab. But again, when inequity is described, those that grab are universally criticized for grabbing and those that allow it are never offered advice or encouragement on how to either resist or walk away. I believe the latter would be much healthier for society and markets.
Pretty close - but "souping" is when you add some random ingredient that destroys the negatives but creates an interesting effect when developing the photos. You can use vinegar, lemon juice, vodka, bleach, any number of chemicals that create different effects;
In the context of the article, it seems the consultants would take copious notes (the negatives) and then go back and 'soup' them in order to have something interesting to present even though it's an unrealistic picture of the office.
> Now, thanks to "luxury surveillance," you can get the same experience in your middle-class home with your Google, Apple or Amazon "smart" camera. Those cameras climbed the curve, going from prisons to schools to workplaces to homes.
All thanks to Big Tech, and by the looks of it if we don't do something to counter against this, we will also own nothing and we will be very happy under the eyes the technocratic elite.
it's ironic to me how the typical boss measures productivity in emails, chats and other things that are not real work, making things, solving problems...
its like even the basis by which they measure work, is not work. but since thats all they ever do, they have no other frame of reference.
And I didn't have to because I had a nice boss but wfh made me uneasy. I made up the need in my head that I had to be not "away" while working. So I did it out of habit ... not too strict though.
I feel like life finds a way even if it went down this path. People will create bots that randomize opening up a list of programs you use and make various gestures to throw off any tracking tool.
I’m less worried about the Orwellian bossware and more about the Huxleyian warning of an abundance of so much information that bosses can hardly decipher what work is even being done.
Yes. And boses don't want to admit that they have no idea how to measure employee productivity, because that would mean that their own productivity is bad. Now maybe there is hope that the boses boss could detect lack of work of those teams, but he may also be afraid of saying the truth.
I agree but we already wage this never-ending tug of war against advertisements and "viruses", we don't need another one. But hey, off we go, all in the name of "employee productivity"
I find it so weird. Aren't there any bosses that say "Yeah, fuck you we're not doing that." That's the point of a boss. If I were in charge of a bunch of programmers and a mandate came down from on high to rate programmers based on commits or keystrokes, my first response would be "Eat shit." and my second response would be "No, really, I'm not treating my people like dogs. Eat shit."
...and they'd pip you out in a few months, and you'd leave without a good reference.
In reality, you'd realize it was horrible, but orders are orders, so most people would do it. If they found it particularly objectionable, they'd just look for another job in the meantime, but most folks who are not financially independent wouldn't take a stand for it.
people over leveraged in their personally lives don't seem to be able to take risks at work for the greater good. all it takes is 6 months of runway cash and i think more people would say "eat shit" instead of blindly following orders to help protect themselves
Middle management has to educate upper management on why certain metrics are bad. I do it all the time. Most recent one was length a PR was open. Some of my better devs opened PRs earlier and left them open for feedback longer, and I didn't want them penalized, so I communicated (with data) to management that it was a bad metric and we no longer measure it.
I disagree. The point of a boss is to squeeze as much productivity as possible from contributors in order to meet business goals. If they do that as a humane understanding collaborator or as a micromanaging tyrant depends on two factors: what kind of person they are and how much leeway does upper management allow. If a boss is of the 'telling their boss to eat shit' variety, they're usually not going to stay a boss for long..
I’ve recently watched Brazil, and the film has one of the most chilling dystopian views I’ve ever seen because it’s easy to see yourself as part of the machine doing your best just trying to get by.
Similarly, I can see how the people working in this software slipped into this- they identified a need in the market with WFH, tried prototypes that were well received on the market, and keep iterating. Many of them legitimately are interested in time tracking and optimization, but of course the market for personal tools like that is very small and lots of employers want to pay you for this because they want more productive employees. Meanwhile the people buying them don’t really know what they are buying, they want to believe they have found a solution to the problem they are terrified of, employees pretending to work and milking them. And the employees exposed to it aren’t in a position of power to change it. And next thing you know we have a dystopian monster with enough funding to be responsible for people’s jobs itself, where no one individual has incentives to buck the curve or much ability to fight back.
What’s the solution then? Doctorow mentions unions, and I’d agree that could work. I think there must be another faction to join that doesn’t ruin you, something to compete with the monolith in case the monolith gets sick in this way. Being able to quit and find somewhere else only works if that somewhere else is mostly differentiated by the fact that it doesn’t do these programs you disagree with- many people will put up with this and worse if there is a large pay differential between it and the next option, or if they would have to move and uproot themselves. And if a government gets sick in this way it might not let you quit the country. You have to be able to form collective groups that can bargain with the behemoth, like a union, or political party, or other action that relies on people for it’s power and not capital. That’s one reason why money in politics is so worrying to me, because the way I see it, it messes with this crucial release valve of political action.
<<Mazzoli seems to have either not used his product, or, if he did, did so under conditions where he was in charge of it – using it the way an athlete might use a stopwatch to time their own sprints, and not the way a boss might: to decide whether to dock your pay or fire you.
And author covered it as well. The technology is interesting and COULD be applied appropriately, but management class seems to be going for low hanging fruits and easy solutions completely undermining what could be a useful tool if used appropriately. The problem, and not a small one at that, is that the management class, in US at least, had a free ride for the past few decades. They only had to threaten with a stick and that was enough. They only know how to use a hammer.
I absolutely agree on Brazil. It is so easy to forget our jobs have impact on the world outside.
Why don't bosses just fire their managers and hire better ones than contract some software? It should be impossible to milk your employer if you are expected to be contributing. Anyone on your team will see right away you are full of shit if you are actually full of shit. If they can get the job done half assed, and people are none the wiser, then good for that employee figuring out how to optimize their time while still delivering acceptable performance that no one is complaining about.
>The bossware problem is a boss problem, in other words.
I think this is basically the core. Bossware, like all technology is essentially about increasing efficiency. If your boss is shit, this technology is going to make them far more effective at being shit.
They aren't just going to do all the traditional things that make them shit - unclear goals, over-rewarding presenteeism, being sexist, racist or misogynist. Now they're going to do all those things but a lot more effectively.
Maybe in general this is a good thing, it's going to increase the gap between good bosses and bad bosses and that will in the end cause the good bosses to outperform the bad bossess and the bad bosses' will be identified, or at the least the companies that have bad bosses will be outperformed.
I would say the problem of this bossware is actually worse in schools and prisons - because those environments lack the same feedback paths that regulate this.
I actually don't think this would be a good thing even for a good boss, because a good boss simply wouldn't use this surveillance bullshit in the way a good boss simply wouldn't sexually harass the intern.
Also, I would disagree that shitty bosses are responsive to their own bad management consequences. Remember that at Blizzard a manager harassed a report to the point of suicide[edit: to be clear, literally passed around explicit pictures of the report through the company, the report killed themselves around that time, so this is allegedly]-- what're the consequences for that manager? They are probably still managing somewhere.
I believe in many states it's illegal for you to be recorded at work. I'm not sure how so many places are getting around this. If the claim is that it's audio vs video, then I say that's a bunk argument. A) we can reconstruct some audio from video (lip reading software), and B) a lot of what would have been "verbal" conversations now happen in text chats, recorded by cameras perfectly in the clear.
Not to mention that I'm always a bit nervous typing passwords into a computer under the eyes of recording machines.
> I believe in many states it's illegal for you to be recorded at work.
That doesn't seem right where are you getting that? A workplace is probably not considered "public" so a third party might be restricted on recording you there. But your employer isn't a third party here so you're straight back into og labor relations and what does your contract say and what does your union allow etc.
Curious how this affects contact centres? They monitor everything agents do down to the millisecond. And "All calls are recorded for training and quality purposes."
Big difference if you use automated means and whether you introspect on how work is performed rather than look at the final product. I have seen places where running reports of LOCs or commits is strictly forbidden to avoid lawsuits.
I'm currently reading "The Tyranny of Metrics" which provides a decent analysis of how over-measuring things that don't have anything to do with the real goal often serves as a deterrent to real progress.
What managers want to know is how much do their workers contribute to the success of the company. What they measure is how much time do workers spend doing X. They're completely glossing over the middle step of how does the time spent doing X contribute to the success of the company, which is usually taken as some kind of linear equation.
Over-measurement is often worse than not measuring anything at all.
> Over-measurement is often worse than not measuring anything at all.
Yes. Not only is "time spent" or "code written" or "features implemented" or even "user engagement" a lossy metric in the best of cases but it can literally end up doing the exact opposite of what you intended. Campbell's & Goodhart's laws are often cited. The trap I see in software companies is a hyperfocus on quantifiable short term wins, entirely glossing over the value created by longer term cultivation of quality. One can see projects where code cleanliness, documentation, testing, CI, and performance have been effectively disincentivised, even though, in the short, mid, and long-term, you will see gains. Such gains, however, are less visible and less quantifiable to the kinds of people who define and foster the metric regimes.
A narrative I observe variations of:
Universe X:
- Programmer A implements feature in one week. They get a admiration and a raise.
- One year later: Programmer B implements feature in 3 weeks, because they had to use Programmer A's shoddy and inconsistent API.
Universe Y:
- Programmer A implements feature in two weeks. Less admiration and no raise.
- One year later: Programmer B implements feature in 1 week, because they were able to use Programmer A's better implemented interface.
Hopefully it's obvious which universe is preferable and produced a net-win. ...
Bad metric regimes are unforuntately not _obviously_ bad when you're inside their machinations. They really need to be dug into to see the fallacies.
One has to look no further than Meta/Facebook for the absolute deteriment caused by overzealous performance reviews and a fixation of experimental upticks in user engagement. It is a bad metric regime.
The universe X example has some merit too. The developer got a raise, the business was excited enough to get this feature done ahead of schedule that someone actually put in the effort to push through a raise, and the total cost for this was one man-week of extra work a year later - basically a drop in the bucket, budget-wise.
You're focusing too much on the specifics of the hypothetical rather than the point of the hypothetical. If you can't get out to the abstraction, then in universe X, programmer B-Z all spend 3 weeks on a feature, and in universe Y, programmer B-Z all spend 1 week on a feature. So we've got an extra man year being burned, all to save a man week upfront. Extend to whatever point short of breaking the analogy you care to.
You never want to built anything shoddily, but there is a lot of value in doing minimum scope. Testing, clean code, etc shouldn't be negotiable in most shops, but scope can be really trimmed down in a lot of scenarios.
Universe Z:
- Programmer X implements feature A in 1 week with tiny scope
- Feature B is mothballed and never gets built
Universe A:
- Programmer X implements feature in 2 weeks
- One year later: This functionality is broken apart into a well defined microservice with additional responsibilities. This needs a total rewrite as a v2 API.
Universe B:
- Programmer implements a feature in 1 week
- One month later with that extra week they were able to squeeze in an unrelated enhancement to the system that delivered .5% extra revenue during Black Friday.
I find most of the productivity metrics fail because you're squeezing the wrong end of the process. You want to spend the most time making sure you're doing what matters and has value, and then it will almost always be worth the time. This makes people feel engaged, which will lead to a lot more productivity than when you're pushing them to build something they don't care about.
If you really wanted to get into waste, how about the building to spec process?
Spec universe: engineer makes thing. bean counters believe they will be out of business if others see how thing is made and copywright their code. another engineer wants to make the same thing. a second engineer has to be brought in to write up a spec. the other engineer now tries to reinvent this wheel from basically a telephone game description on how it should work and behave. as a result any time an engineer needs a wheel you need a second engineer to describe it to you so you can reinvent the wheel.
open source universe: engineer makes thing. second engineer forks thing.
Universe Y is fine if the company is certain to survive for one year but it is quite possible that slow development of features will mean that in Universe Y there is no Programmer B to benefit from the beautiful API.
I think this was covered in "Thinking Fast and Slow", but when our brains encounter a hard problem, we often substitute the answer for an easy question. I think this process is at play in the dynamics you list above.
"How does the time spent doing X contribute to the success of the company?" is a hard question. It has incredible value and every company should spend a great deal of time considering it.
"How much time do workers spend doing X?" is an easy question, and so we have used its answer as the answer to the hard question.
in 2015 I made a change that stopped 90% of the tickets that rolled into my team's queue. The remaining 10% were complicated real customer issues. Our entire department was closed 6 months later, because I assume our ticket completion was so low, and we were so slow to fix issues. :/
It's not even over-measuring, it's measuring the wrong thing, because the thing you actually want to know isn't (easily) measurable.
The whole thing is down to poor management(-culture). Good managers already know who their top performing team members are. They don't need these tools. Measuring LOC or time spend sitting at the desk is in my view attempting to compensate for lack in management skills. It's like advertising agencies that can't sell ads without AdSense. Boss-ware is an attempt by poor managers to make up for a lack of skills by applying something that looks science from a distance.
<< The irony, of course, is that bossware is now coming for execs, and, what's more, they lack the engineering skills to optimize their work so they can get a high score and do the job, so they have to settle for just getting the score – and hang the job itself.
I will believe it when I see it in action. If there is one thing that remain constant is the golden rule ( "He who has gold makes the rules" ). And boss class has the gold.
I can't recall the name of it but there was a pre-pandemic startup for remote teams where it took a picture of you at your desk every few minutes to share with your team, supposedly to achieve less lonely remote-only workplaces. They marketed it as pro-worker, lol.
Has a similar experience with upwork once where the contractor (who are screen recorded by upwork to make sure they're "working") would just spend large amounts of time scrolling up and down on the IDE looking at source code - literally hours - to look busy and keep the meter rolling.
If you can't measure output, there is no point in measuring input.
You eat a banana. It's delicious and nutritious. Cool.
You read about a fellow who ate a banana. Ah, such a fond reference.
You read about your banana-research employees. Taste, nutrition and fond references are furthest from your mind. You only care about your sales numbers.
There's no value in thinking all day about how bananas are delicious. Before you can eat the banana, it has to be produced and shipped. That process does not even involve thinking that bananas are delicious, so that kind of thinking isn't abstracted in the production process, it's simply irrelevant.
I disagree. If you ignore the actual value your product provides to the final consumer "this banana is delicious", you'll come up with solutions that diminish that value. The only reason why blending whole bananas (peel and all), and sending that slop in an unrefrigerated shipping container isn't even considered as an option is an understanding of what the banana-buyers want.
Nobody is proposing ignoring what people will buy. What I said is that literally thinking "this banana is delicious" does not achieve anything toward the actual delivery of any bananas for consumption. It is the end of the production story, not a part of the process, so it is not abstraction to leave it out. Set up a process for sampling batches of bananas if you want, but the value of that isn't for an employee to think "this banana is delicious" 100 times per day. That is confusing consumption with production. There's a good reason why production doesn't include consumption.
206 comments
[ 2.4 ms ] story [ 224 ms ] thread/s
If the issues are tin-foil, please point us at the articles that debunk the issues described..
Reality is stranger than fiction.
nit: it's better stated as "any measurement becomes a target".
Reading the article, I had a pang of hope. If it's really as anti-effectual as described, perhaps just everyone needs to buy mouse jiggling dongles and the push behind the immediate trend will lose momentum.
Or really, it's just another step in the corporate-Keynesian make-busy-work economy that has gobbled up most of our productivity gains for decades.
There's an election coming up in Sweden.
One of the parties is literally advertising their platform with "more security cameras on our streets" (Moderaterna), and every party is keen to expand police power to have more surveillance and wiretapping without prior criminal suspicions (at least according to the "Election compass" on SVT: https://valkompass.svt.se/2022)
> Mazzoli seems to have either not used his product, or, if he did, did so under conditions where he was in charge of it – using it the way an athlete might use a stopwatch to time their own sprints, and not the way a boss might: to decide whether to dock your pay or fire you.
> This inability to understand the difference between using a technology and having the same technology used against you is endemic to the industry.
I think this is a key failure of understanding for the "tech is neither good nor bad!" camp: just as the Death Star clearly was never going to be used for mining planetoids, it's very clear how workplace surveillance tech will be used to harm workers, if nothing else because of how it is currently being used. Continuing to work on such tech just because it could theoretically be used for non-evil purposes is morally bankrupt, and something the industry needs to establish ethical standards to prevent.
Consider history; Do you think for one minute, that a Viceroy somewhere, and legions of new administrators, won't inflict endless and strictly enforced conditions on anyone they can find, using software?
https://upload.wikimedia.org/wikipedia/commons/2/21/1776_Pot...
Of course, if programmers are raised from a young age and brainwashed into believing that workplace surveillance is innocent / good, that's a different problem than adults who should know better when it comes to the real world results of using the tech they are building.
I was listening to someone describe their use in WWII, and he was I suppose trying to defend it by saying that actually most of the people it killed weren't burned at all, but rather killed because they were in enclosed fortifications and apparently flamethrowers produce prodigious amounts of carbon monoxide - basically you'd take a couple breaths and it's over - the carbon monoxide will bind into your blood cells such that even if you immediately step out into fresh air, you're a dead man walking. But at least your corpse will be recognizable for your friends and family I suppose; you won't be burned beyond recognition.
But building a reliable flamethrower is an interesting technical challenge, so I'm sure you can find an engineer who will be willing to give it a go.
I like the addendum, "...but nor is it neutral"
Bossware, or working machine monitoring software, endpoint monitoring, or whatever turned out to be a key part of making it possible for our data scientists to function. At all. It was the only way we could both protect the incredibly sensitive information about lots of people while allowing analysis work to proceed.
Aside: anyone who wants to talk about doing data analysis without access to the underlying data is cordially invited to explain how to do this to statisticians who only understand R and local Jupyter notebooks.
"But wait!" you protest, "Can't the business work just as well without that sensitive information?". That's a good question! The short answer is no. No, it cannot, and unfortunately there's a great deal of actuarial history behind this.
"But wait!" cry you, "Could you have not simply trusted them?". That's also an excellent question! To which the uncomfortable response runs roughly: how comfortable do you feel with "we trust them" as the primary security controls when some company has your data? Especially when that trust means you might not even know about a breach? How do you think a regulator concerned with privacy would look at "we trust them" as a security and privacy approach?
Unfortunately, I think some forms of bossware serve a purpose. Sometimes it's one of the few options available that enables trust beyond the directly interpersonal.
Provision some isolated machines with access to production data, and let the data scientists login remotely. You'll be able to tell who is accessing the data and when, and won't need to install invasive bossware on their systems. It's a fairly straightforward solution. It's one thing to control access to sensitive data. Its another to use that to justify monitoring employees all day, even when they aren't accessing sensitive data.
There are a lot of options for monitoring for that kind of thing. You monitor the remote machine, you monitor the network traffic between it and their local terminal... and the most valuable will be monitoring their local machine to associate with the rest of the access and usage information. Among other things, you need to be able to distinguish between someone using the data scientist's credentials and the data scientist using their own credentials.
Your idea is a wonderful approach! It improves security, privacy, traceability, and auditability. It may not be the same as removing the need for endpoint monitoring, unfortunately.
We also didn't have bossware. There were access controls on the data itself, audit trails on who accessed the data, but no software running locally on my personal dev machine looking at what I did at any particular moment.
HIPAA governs the storage, transport, and use of that health information, and we all knew we were criminally liable if the information got out.
Bossware in a HIPAA environment (or other environment where not having leaks in important) can be more of a liability than a boon, because it becomes yet another vector for attack or data leakage. You are in effect sharing all data a machine can access, with the maker of the bossware.
Something with the teeth of HIPAA but for other pieces of personal information could go a long way. It's amazing how differently executives behave when the consequences of data leaks change from "customers could be unhappy if they found out" to "I could personally go to prison".
Meanwhile this data is getting leaked every other week by other companies. Didn't Equifax leak pretty much all sensitive information for the entire nation. What happened there?
I haven't formed a constructive thought out of all this yet, I'm just frustrated that we'll get surveillance software to allegedly protect data that's already been leaked by a hundred other companies.
Often this will be like the "think of the children" argument. Of course we should be concerned about security and make efforts to protect data, but many times the same people who push surveillance software in the name of security will later turn a blind eye to other security practices or concerns that might be an inconvenience to them. Their concern for security will extend only as far as it gives them power.
To draw an imperfect comparison - improving the efficiency of electric car motors does little for those driving dino-juice-mobiles. That we as a society have the tools and ability to do better does not mean that every person and organization adopted them immediately and perfectly.
Joint distributions and generating functions trained against the production data to generate synthetic data, generally.
My takeaway is not just that that, but that it will be used to harm businesses as they train their employees to do the measured thing over and above the best thing for the company.
I suspect most people here could envision this as an extension of a "Lines of Code written" based performance metric and intuit the likely outcomes.
I am certain “bossware” will accelerate the downfall of already shitty workplaces.
Very happy to hear Amazon is doing away with it. Strongly hope their workers unionize anyway. What kind of employer nickle-and-dimes a worker’s bathroom breaks? Not a good one, that’s for damn sure.
I used to see these job postings on LinkedIn for Crossover for Work. I was intrigued by the claim of $400yr salary. Glad I didn’t end up working there. Thanks but no thanks, I am not going to work actively oppressing already downtrodden workers. A quick search turned up this fascinating article as well: https://medium.com/@whistler_12777/heres-why-crossover-is-a-...
Fuck bossware. Fuck people who work to actively oppress others. Humanity for all, value of life for each and every person out there.
Rant over. Thanks for the link.
I had a teacher in high school who would respond the same way (more or less) whenever someone would ask to use the restroom:
> If you ever have a job that needs you to ask to use the restroom, find a better job.
The right answer is always to deal with the individuals who are the problem, but somehow it always becomes rules that make life worse for everyone.
So, they do take advantage for a while, until everyone realizes they're a jerk, so now everyone has to go through the new "process". Because they can't just be fired "for taking sick leave", which "is their right".
This is why we can't have nice things.
Extrapolating here ... employee wants 5 minutes of bathroom breaks because it was not in contract and the manager abused it, so when the 5 minutes gets written into the contract, then the manager can still abuse it by writing you up for a 6 minute break, or just refuse to help you out today because he did not have a good experience with you or someone else yesterday.
We are losing the human touch due to both-sided legalese in everything.
They file for reasonable accommodation and the idiots who get concerned about your bathroom time have to be quietly told to stand down because you have special permission to poo.
It can get more absurd as well. There’s an unlimited about of goldbricking and bullshit that people are capable of.
Or being female and unlucky with the effects of your cycle.
Or just having a rough day because something you ate was bad.
It's one thing if there's an ongoing pattern of long, unexplained breaks and someone's line manager has a discreet word about it and asks if there is anything they need to know. However routinely messing with things like breaks or availability of kitchen and bathroom facilities is surely one of the most counterproductive policies an employer could adopt. Nothing says we respect and value our people like treating them as subhuman!
Any of these situations can mean someone isn't getting their work done. Their colleagues might be left to pick up the slack, which isn't fair on them either. Any of the people involved might start to worry or get upset about the situation, which can make things worse.
Whatever is going on it's management's responsibility to figure it out and then deal with it professionally and with appropriate discretion and sensitivity. The difficult part is figuring out what that looks like when the situation could be delicate and there might be anything from very personal medical issues to criminal behaviour involved.
Everyone on the likes to pretend that rules and regulations are either a) a boondoggle net-negative exercise in cost cutting b) "wRiTtEn In BlOoD" depending on whether they like the procedure or regulation in question.
Reality is often far more mundane and dysfunctional. It's frequently just speculative bike shedding and ass-covering, exactly the kind of "pointing out exploits" stuff the HN crowd loves to engage in when it comes to policy as though organizational policy was a firewall to configure.
Here's how it probably went down: Some people were hammering out the language of a contract and some bike-shedder replied to all pointing out that breaks, work stoppages, lunch, etc, etc, were all being counted but bathroom breaks weren't and that potentially created an exploit to the proposed system of cost/time/whatever tracking. No party had the balls to take responsibility and say "this is silly, we'll cross that bridge if/when we get to it" bathroom breaks wound up incorporated that into their formula. So thanks to some bike-shedder trying to "contribute" and nobody's willingness to take any risk whatsoever (by going on the record brushing aside a petty concern that could come back to bite them) everyone has to track their piss breaks. And to be fair, all these people are doing exactly what they are incentivized to do (!!!). And these aren't the kind of things you can roll back later because then you have to explain why you're a) deviating from established way of doing things and b) accepting some risk in doing so which nobody wants to do for a variety of reasons that have been discussed at length and are outside the scope of this comment.
Source: This crap happens like quarterly in my workplace.
Edit: of course there's other potential complications that can effect these kinds of things but you get the gist.
Whomever wrote that contract was a doofus.
"Position was eliminated" works pretty well (in the US).
Private entities will do what they've always done and my original comment succinctly describes the default outcome. Nothing has changed.
Unless you also happen to be recruiting for that same position, or if your local legislation asks that you prioritise relocating your current employees in other jobs over firing them if their position disappears.
Without a contract, discrimination law is the sole course of action to fight an adverse employer situation.
Eliminating a position leaves a company open for problems, particularly if it isn’t true. Much easier to determine that you didn’t charge vacation time correctly or violated a series of minor/moderate rules.
This has absolutely nothing to do with anti discrimination law.
Local food co-op. Very modern hippy. Nice place.
Every employee has a dossier on file. Every time a rule is broken it goes into the dossier.
If, for whatever reason, you are fired. The dossier is cited as legal justification.
I guess this is perfectly rational from a businessy perspective, and a common tactic. But still.
Also, upper management somehow feel that their middle and lower managers can be trusted to act like adults while the people who do the actual work cannot be.
The proper solution is getting rid of management, and letting workers get their jobs done.
https://hbr.org/2011/12/first-lets-fire-all-the-managers
https://www.inventium.com.au/learned-fired-managers/
With workplace control seeming to predate worker protection by a century, you wouldn’t expect that. But it’s always exciting when intuitions get subverted. I’d love to read more of how the historian who proposed this put together their argument. Do you have a link handy?
This is backwards. Union membership is at its all time low and at-will employment has mostly taken over. A union would be the best tool to curb "boss-ware".
You may enjoy Terry Gilliam’s The Zero Theorem.
Peloton will eventually start climbing the STAC ladder (it’s literally their only remaining move). Between that, permanent covid mitigations and the office-space downsizings of the late 2020’s, Gilliam’s vision will be complete!
He makes good points and has a clear set of beliefs that he applies consistently, especially on topics like this, but gets a little overbearing if you follow closely.
Secondly, the longer I have been a participant of society and markets, I've come to realize that power imbalances are as affected by how much the participants stand up for themselves in the face of power grabs as it is how much other participants grab. But again, when inequity is described, those that grab are universally criticized for grabbing and those that allow it are never offered advice or encouragement on how to either resist or walk away. I believe the latter would be much healthier for society and markets.
https://www.kjsmall.com/projects/film-soup-tips-tricks
In the context of the article, it seems the consultants would take copious notes (the negatives) and then go back and 'soup' them in order to have something interesting to present even though it's an unrealistic picture of the office.
All thanks to Big Tech, and by the looks of it if we don't do something to counter against this, we will also own nothing and we will be very happy under the eyes the technocratic elite.
They say it's all anonymized but it's really easy to correlate back to users by playing with settings.
its like even the basis by which they measure work, is not work. but since thats all they ever do, they have no other frame of reference.
And I didn't have to because I had a nice boss but wfh made me uneasy. I made up the need in my head that I had to be not "away" while working. So I did it out of habit ... not too strict though.
https://github.com/arkane-systems/mousejiggler
I’m less worried about the Orwellian bossware and more about the Huxleyian warning of an abundance of so much information that bosses can hardly decipher what work is even being done.
In reality, you'd realize it was horrible, but orders are orders, so most people would do it. If they found it particularly objectionable, they'd just look for another job in the meantime, but most folks who are not financially independent wouldn't take a stand for it.
Middle management has to educate upper management on why certain metrics are bad. I do it all the time. Most recent one was length a PR was open. Some of my better devs opened PRs earlier and left them open for feedback longer, and I didn't want them penalized, so I communicated (with data) to management that it was a bad metric and we no longer measure it.
I disagree. The point of a boss is to squeeze as much productivity as possible from contributors in order to meet business goals. If they do that as a humane understanding collaborator or as a micromanaging tyrant depends on two factors: what kind of person they are and how much leeway does upper management allow. If a boss is of the 'telling their boss to eat shit' variety, they're usually not going to stay a boss for long..
Similarly, I can see how the people working in this software slipped into this- they identified a need in the market with WFH, tried prototypes that were well received on the market, and keep iterating. Many of them legitimately are interested in time tracking and optimization, but of course the market for personal tools like that is very small and lots of employers want to pay you for this because they want more productive employees. Meanwhile the people buying them don’t really know what they are buying, they want to believe they have found a solution to the problem they are terrified of, employees pretending to work and milking them. And the employees exposed to it aren’t in a position of power to change it. And next thing you know we have a dystopian monster with enough funding to be responsible for people’s jobs itself, where no one individual has incentives to buck the curve or much ability to fight back.
What’s the solution then? Doctorow mentions unions, and I’d agree that could work. I think there must be another faction to join that doesn’t ruin you, something to compete with the monolith in case the monolith gets sick in this way. Being able to quit and find somewhere else only works if that somewhere else is mostly differentiated by the fact that it doesn’t do these programs you disagree with- many people will put up with this and worse if there is a large pay differential between it and the next option, or if they would have to move and uproot themselves. And if a government gets sick in this way it might not let you quit the country. You have to be able to form collective groups that can bargain with the behemoth, like a union, or political party, or other action that relies on people for it’s power and not capital. That’s one reason why money in politics is so worrying to me, because the way I see it, it messes with this crucial release valve of political action.
And author covered it as well. The technology is interesting and COULD be applied appropriately, but management class seems to be going for low hanging fruits and easy solutions completely undermining what could be a useful tool if used appropriately. The problem, and not a small one at that, is that the management class, in US at least, had a free ride for the past few decades. They only had to threaten with a stick and that was enough. They only know how to use a hammer.
I absolutely agree on Brazil. It is so easy to forget our jobs have impact on the world outside.
Why don't bosses just fire their managers and hire better ones than contract some software? It should be impossible to milk your employer if you are expected to be contributing. Anyone on your team will see right away you are full of shit if you are actually full of shit. If they can get the job done half assed, and people are none the wiser, then good for that employee figuring out how to optimize their time while still delivering acceptable performance that no one is complaining about.
I think this is basically the core. Bossware, like all technology is essentially about increasing efficiency. If your boss is shit, this technology is going to make them far more effective at being shit.
They aren't just going to do all the traditional things that make them shit - unclear goals, over-rewarding presenteeism, being sexist, racist or misogynist. Now they're going to do all those things but a lot more effectively.
Maybe in general this is a good thing, it's going to increase the gap between good bosses and bad bosses and that will in the end cause the good bosses to outperform the bad bossess and the bad bosses' will be identified, or at the least the companies that have bad bosses will be outperformed.
I would say the problem of this bossware is actually worse in schools and prisons - because those environments lack the same feedback paths that regulate this.
Also, I would disagree that shitty bosses are responsive to their own bad management consequences. Remember that at Blizzard a manager harassed a report to the point of suicide[edit: to be clear, literally passed around explicit pictures of the report through the company, the report killed themselves around that time, so this is allegedly]-- what're the consequences for that manager? They are probably still managing somewhere.
Not to mention that I'm always a bit nervous typing passwords into a computer under the eyes of recording machines.
That doesn't seem right where are you getting that? A workplace is probably not considered "public" so a third party might be restricted on recording you there. But your employer isn't a third party here so you're straight back into og labor relations and what does your contract say and what does your union allow etc.
How do they evaluate people for promotion if you aren't allowed to monitor anyone's performance in any way?
What managers want to know is how much do their workers contribute to the success of the company. What they measure is how much time do workers spend doing X. They're completely glossing over the middle step of how does the time spent doing X contribute to the success of the company, which is usually taken as some kind of linear equation.
Over-measurement is often worse than not measuring anything at all.
Yes. Not only is "time spent" or "code written" or "features implemented" or even "user engagement" a lossy metric in the best of cases but it can literally end up doing the exact opposite of what you intended. Campbell's & Goodhart's laws are often cited. The trap I see in software companies is a hyperfocus on quantifiable short term wins, entirely glossing over the value created by longer term cultivation of quality. One can see projects where code cleanliness, documentation, testing, CI, and performance have been effectively disincentivised, even though, in the short, mid, and long-term, you will see gains. Such gains, however, are less visible and less quantifiable to the kinds of people who define and foster the metric regimes.
A narrative I observe variations of:
Universe X:
- Programmer A implements feature in one week. They get a admiration and a raise.
- One year later: Programmer B implements feature in 3 weeks, because they had to use Programmer A's shoddy and inconsistent API.
Universe Y:
- Programmer A implements feature in two weeks. Less admiration and no raise.
- One year later: Programmer B implements feature in 1 week, because they were able to use Programmer A's better implemented interface.
Hopefully it's obvious which universe is preferable and produced a net-win. ...
Bad metric regimes are unforuntately not _obviously_ bad when you're inside their machinations. They really need to be dug into to see the fallacies.
One has to look no further than Meta/Facebook for the absolute deteriment caused by overzealous performance reviews and a fixation of experimental upticks in user engagement. It is a bad metric regime.
Universe Z: - Programmer X implements feature A in 1 week with tiny scope - Feature B is mothballed and never gets built
Universe A: - Programmer X implements feature in 2 weeks - One year later: This functionality is broken apart into a well defined microservice with additional responsibilities. This needs a total rewrite as a v2 API.
Universe B: - Programmer implements a feature in 1 week - One month later with that extra week they were able to squeeze in an unrelated enhancement to the system that delivered .5% extra revenue during Black Friday.
I find most of the productivity metrics fail because you're squeezing the wrong end of the process. You want to spend the most time making sure you're doing what matters and has value, and then it will almost always be worth the time. This makes people feel engaged, which will lead to a lot more productivity than when you're pushing them to build something they don't care about.
Spec universe: engineer makes thing. bean counters believe they will be out of business if others see how thing is made and copywright their code. another engineer wants to make the same thing. a second engineer has to be brought in to write up a spec. the other engineer now tries to reinvent this wheel from basically a telephone game description on how it should work and behave. as a result any time an engineer needs a wheel you need a second engineer to describe it to you so you can reinvent the wheel.
open source universe: engineer makes thing. second engineer forks thing.
"How does the time spent doing X contribute to the success of the company?" is a hard question. It has incredible value and every company should spend a great deal of time considering it.
"How much time do workers spend doing X?" is an easy question, and so we have used its answer as the answer to the hard question.
The whole thing is down to poor management(-culture). Good managers already know who their top performing team members are. They don't need these tools. Measuring LOC or time spend sitting at the desk is in my view attempting to compensate for lack in management skills. It's like advertising agencies that can't sell ads without AdSense. Boss-ware is an attempt by poor managers to make up for a lack of skills by applying something that looks science from a distance.
I will believe it when I see it in action. If there is one thing that remain constant is the golden rule ( "He who has gold makes the rules" ). And boss class has the gold.
If you can't measure output, there is no point in measuring input.
You eat a banana. It's delicious and nutritious. Cool.
You read about a fellow who ate a banana. Ah, such a fond reference.
You read about your banana-research employees. Taste, nutrition and fond references are furthest from your mind. You only care about your sales numbers.
Abstraction=progressive numbness.
“I’m extremely happy with the progress you made this month, but HR says you worked zero hours this week.”
“I couldn’t figure out how to use the corporate laptop. Sorry about that.”