News for hackers. Stuff that matters.
Re:Invasive, secretive “bossware” tracking workers by hirundo on Thursday July 02, 2020 @10:52PM (#23720619)
My boss has us using a bossware SaaS app that tracks our work with exquisite detail. It's called GitHub. The tracking consists of our trail of commits to various repos. (Along with the resulting error logs and tickets.) He can see exactly what we're doing for the project and when. In fact he has a team that "peer reviews" the tracking data line by line and are not shy about pointing out deficiencies.

To track other things, like time on task or web surfing habits, would not even be redundant, just superfluous.

Re:Invasive, secretive “bossware” tracking workers by posedge on Friday July 03, 2020 @05:33AM (#23722498)
People who truly think this is any useful kind of metric are probably the ones who think # lines of code written = productive work. Or, as Bill Gates put it so nicely, they are measuring the progress on the aircraft by its weight.
Re:Invasive, secretive “bossware” tracking workers by m463 on Friday July 03, 2020 @10:32AM (#23724377)
Re:Invasive, secretive “bossware” tracking workers by peacemaker on Friday July 03, 2020 @10:17AM (#23724248)
Counting lines of code is definitely not a useful metric, however, you can extract a lot of information via the Github API that I believe can help with managing a tech team. It's exactly why I created getdevinsight.com as I think too many managers rely on bad metrics like lines of code and we can do better.
Re:Invasive, secretive “bossware” tracking workers by norswap on Monday July 06, 2020 @03:27PM (#23751743)
Perhaps one should look at the work being done instead of "relying on metrics"? Just a suggestion...
Re:Invasive, secretive “bossware” tracking workers by posedge on Saturday July 11, 2020 @09:27AM (#23802047)
"When a measure becomes a target, it ceases to be a good measure" - Goodheart's law.

Give people a metric - any metric - and they will (conciously or otherwise) start optimizing that instead of the actual goal.

Re:Invasive, secretive “bossware” tracking workers by peacemaker on Tuesday July 07, 2020 @11:53AM (#23760469)
Easier said than done when you've a large, busy team to manage alongside lots of other work.

Besides, if you're a non-technical leader it can be difficult to understand how things are going unless you have some kind of metrics to track.

Re:Invasive, secretive “bossware” tracking workers by koheripbal on Friday July 03, 2020 @08:07AM (#23723267)
There's nothing as effective as a good manager.

A good manager can often sense when someone is not doing their job, or has disconnected.

In one case, a good manager came to me and asked me to check the "bossware" software to see if a certain employee was working while "working from home".

...turns out they were not. So we terminated them.

Good manager + bossware = Efficient process.

Re:Invasive, secretive “bossware” tracking workers by scoot_718 on Friday July 03, 2020 @08:46AM (#23723494)
Yeah, that's good management, only detect after the problem has gotten too big, and then deal with it in the most useless way possible. Go team.
Re:Invasive, secretive “bossware” tracking workers by rbrtl on Friday July 03, 2020 @09:13AM (#23723686)
How was the manager a good manager here?

They didn't "sense" anything, they just asked you to show them some stats on a dashboard. They didn't approach the person for an explanation or conversation.

This manager totally removed the human from the person struggling with their job. That makes them a good robot.

Re:Invasive, secretive “bossware” tracking workers by kuzimoto on Friday July 03, 2020 @06:47PM (#23728287)
Just to give them the benefit of the doubt, we don't know if this is the first or tenth time this employee was slacking off, or what action (if any) had already taken place to improve things.

I can additionally imagine that koheripbal was not privy to any information regarding that employee's performance besides that one thing.

Re:Invasive, secretive “bossware” tracking workers by throwaway_pdp09 on Friday July 03, 2020 @08:20AM (#23723323)
He could have been sleeping days and working nights etc. Surely you look at their actual ouput and judge from that, unless I'm missing something.
Re:Invasive, secretive “bossware” tracking workers by neves on Friday July 03, 2020 @10:12AM (#23724189)
Excellent way to treat people with personal problems like depression, health problems or a failing marriage. This is really an efficient society that I don't to live on.
Re:Invasive, secretive “bossware” tracking workers by gorgoiler on Friday July 03, 2020 @01:19AM (#23721240)
If ones job is to break rocks, it’s hardly bossware to track how many fractures one has committed today?
Re:Invasive, secretive “bossware” tracking workers by warent on Friday July 03, 2020 @01:26AM (#23721267)
This is very poetic and as amusing as it is depressing
Re:Invasive, secretive “bossware” tracking workers by MaxBarraclough on Friday July 03, 2020 @08:28AM (#23723372)
Right. If a manager has no means of gauging the progress of those they're meant to manage, they can't do any managing, pretty much by definition.

From the article:

> Bossware typically lives on a computer or smartphone and has privileges to access data about everything that happens on that device.

It's a question of intrusiveness and granularity. Git commits are plainly not 'bossware'.

It's not wise for a manager to use git commits as their sole estimator of progress, but that's another question entirely.

Re:Invasive, secretive “bossware” tracking workers by Tarq0n on Friday July 03, 2020 @10:39AM (#23724424)
Managers always have a means of gauging progress: asking the people doing the work.
Re:Invasive, secretive “bossware” tracking workers by MaxBarraclough on Friday July 03, 2020 @11:13AM (#23724697)
True enough. I should have said it's not an unreasonable thing for a manager to look at. It's not that it would be impossible to get by without management looking at git commits, and as you indicate, it's not a substitute for communication.
Re:Invasive, secretive “bossware” tracking workers by koheripbal on Friday July 03, 2020 @10:22AM (#23724294)
Exactly. Some jobs don't produce easily trackable work product.

So the only option is to track whether they're working or not.

Re:Invasive, secretive “bossware” tracking workers by onion2k on Thursday July 02, 2020 @11:38PM (#23720815)
You can modify both the author date and the commit date on a commit if you need to. Git log is not trustworthy spying tool.
Re:Invasive, secretive “bossware” tracking workers by quadrifoliate on Friday July 03, 2020 @12:22AM (#23720990)
While I know this is possible and have done it sometimes for fun, I would never spend any appreciable amount of time doing it at a job.

If you are at the point where you need to modify commit timestamps to satisfy some micromanager, it's highly likely that there are other things wrong with them that will lead to you searching for a new job fairly soon.

Re:Invasive, secretive “bossware” tracking workers by ric2b on Friday July 03, 2020 @03:37PM (#23726816)
You would if you knew it was being tracked and you otherwise liked the job, you'd even automate it. Let's not kid ourselves.
Re:Invasive, secretive “bossware” tracking workers by quadrifoliate on Friday July 03, 2020 @06:35PM (#23728227)
* you knew it was being tracked

* you otherwise liked the job

All I was saying is that these two are very likely mutually exclusive.

Sure, it's hypothetically possible that I have a micromanage-y boss who only tracks my commit times and nothing else. But really? That's the same boss who's going to mentally think you're "not a team player" because you left an hour early for your son's birthday party. That's the same boss who's going to obsessively tracks how many vacation days you "accrued" and insist on you coming in when you're sick if you don't have any left. Let's not kid ourselves.

Re:Invasive, secretive “bossware” tracking workers by czbond on Friday July 03, 2020 @12:02AM (#23720905)
Commits should really be signed. The first time I learned of this was when a malicious update was supposedly pushed to Tesla firmware.

https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work

Re:Invasive, secretive “bossware” tracking workers by yjftsjthsd-h on Friday July 03, 2020 @01:27AM (#23721277)
If I'm signing commits, I can sign any commit I want with any time I want, no?
Re:Invasive, secretive “bossware” tracking workers by inetknght on Friday July 03, 2020 @02:17AM (#23721478)
If others are signing commits too, good luck changing history!
Re:Invasive, secretive “bossware” tracking workers by OJFord on Friday July 03, 2020 @03:30AM (#23721833)
If it's already shared history it would be too late anyway - thread is about lying when you authored/committed.

Not really sure what the benefit in cheating your boss would be though? You still had to do the work at some time. Maybe you work extra hard one day but push only the first half of your commits, then give yourself a day off where all you do is check in at the end to push the fake-timed other half of them?

It'd probably be easier to find an 'unlimited holiday' job that pays you for output rather than keeping your seat warm.

Re:Invasive, secretive “bossware” tracking workers by Znafon on Friday July 03, 2020 @06:36AM (#23722827)
I think only tags should be signed, Torvalds has a good discussion about signing commits vs signing tags at http://git.661346.n2.nabble.com/GPG-signing-for-git-commit-t...
Re:Invasive, secretive “bossware” tracking workers by threentaway on Friday July 03, 2020 @01:06AM (#23721178)
You can even require signed commits in GitHub.
Re:Invasive, secretive “bossware” tracking workers by mobiledev2014 on Thursday July 02, 2020 @11:26PM (#23720769)
Every morning I rebase my local changes from the previous day and push them at roughly the same time. I suggest everyone do the same!

I might switch to doing it once a sprint :)

Re:Invasive, secretive “bossware” tracking workers by choward on Friday July 03, 2020 @12:15AM (#23720957)
Why not at the end of the day in case something happens to your computer?
Re:Invasive, secretive “bossware” tracking workers by mobiledev2014 on Friday July 03, 2020 @12:58AM (#23721145)
Sounds like my employer's problem.

...but also because I'm a weird night owl and don't like my employer to see me slacking off all day then doing work at 1am.

Re:Invasive, secretive “bossware” tracking workers by looperhacks on Friday July 03, 2020 @12:17AM (#23720969)
Doesn't the author date stay unchanged by a rebase?
Re:Invasive, secretive “bossware” tracking workers by gen220 on Friday July 03, 2020 @12:32AM (#23721028)
You can doctor author dates pretty trivially. git commit --date=
Re:Invasive, secretive “bossware” tracking workers by qznc on Friday July 03, 2020 @06:51AM (#23722886)
Our workers council (Betriebsrat in german) required certain features in our internal Bitbucket to be disabled to prevent such tracking.
Re:Invasive, secretive “bossware” tracking workers by microcolonel on Friday July 03, 2020 @07:53AM (#23723199)
You disabled code reviews and commit timestamps?
Re:Invasive, secretive “bossware” tracking workers by to11mtm on Friday July 03, 2020 @01:26PM (#23725787)
It's this interesting thing in Germany.

I'm sure I'm getting details a little wrong here, but basically if you're paying someone a certain salary to do a task, you aren't allowed to know how long it took to do it.

Microsoft Word has an example of this: The 'Total Editing time' tracking feature is disabled in Germany (and likely other countries.)

Re:Invasive, secretive “bossware” tracking workers by microcolonel on Friday July 03, 2020 @03:23PM (#23726708)
If I'm understanding this correctly from you, you mean that in the sense that if they complete the task in the time allotted, there shall be no record of specifically how much of the deadline it took up?

That seems like a decent managerial practice for some types of workplace, and it's definitely the model I have for my direct reports; but doing it by law seems like a bit of a shortcut for some reason to my anglo brain.

Re:Invasive, secretive “bossware” tracking workers by to11mtm on Friday July 03, 2020 @04:47PM (#23727450)
I -think- that's the general intent.

I also think it's an aspect that should be explored more. Sometimes people forget that the time to complete a task does not always correlate with the cognitive load of completing a task.

I've seen orgs where 'top producers' on a team slowly get loaded up more and more, eventually having 50-100% more points on a sprint than their peers on the team. They usually wind up 50-100% more drained at the end of the day too, and it winds up impacting their quality of life.

Re:Invasive, secretive “bossware” tracking workers by qznc on Friday July 03, 2020 @10:53AM (#23724529)
I believe their attacker model is a manager who can look at statistics on a web page. Not a developer who can do git-checkout. :)
Re:Invasive, secretive “bossware” tracking workers by lrem on Friday July 03, 2020 @03:56AM (#23721975)
Never spent six hours to figure out a one-line fix?
Re:Invasive, secretive “bossware” tracking workers by steelframe on Saturday July 04, 2020 @10:40AM (#23732512)
I know someone who spent about three months on a 10-line fix, which was primarily a configuration tweak. As part of that process, they had to discover and describe emergent properties of an architecture that formed organically over several years from multiple teams building components that interacted with one another in non-trivial ways. They ended up getting a promotion due to that code’s incredible impact.
Re:Invasive, secretive “bossware” tracking workers by loa_in_ on Friday July 03, 2020 @07:17AM (#23723012)
Still, I'd very much write the reasoning down in the commit log. My commit logs sometimes were essay-long