Basically every company I’ve worked for has had some sort of rubric like this. I don’t think that’s inherently bad, it can be quite good for consistency.
I have quit companies that made their performance review systems too onerous/frequent/intense. It’s exhausting to constantly be justifying your existence and having to sell yourself instead of doing the real work.
At one point I was at a 50/50 ratio of time spent documenting/justifying my work vs doing my work, and that was miserable. My level of anxiety reduced my job performance, which created a very unhealthy cycle. Pressure creates diamonds but it also suffocates and crushes most things.
That’s why seeing things like in-context sampling in the article make me suspicious. I don’t think I would be happy at all being interrupted as I’m in flow state to be asked if I could be more productive. I also feel some of this like speed (“time to 10th PR”) or working on new stuff is creating bad incentives.
Fundamentally the most important metric is how hard your boss will fight for you. The second most important metric is whether you can meaningfully discuss areas of improvement honestly and safely with your boss.
If either of those two are out of whack you should question whether to make a change. If I’m missing those I’m not going to be able to do my best work, so it cuts both ways.
Yes, I’ve worked in companies that use DX. Generally you get a survey once a quarter, and you can see some basic stats like how many PRs/code reviews are happening.
My company leadership does not use these as a one size fits all metric. In fact, the code review & PR stats never even show up in performance reviews. Mainly, they are used to improve systems around dev productivity. Like, we see that generally, we’re shipping less PRs and the survey shows people think it’s getting slow to merge changes. That is an opportunity to look at where our systems are holding us back.
I think broad stats are also probably still useful too. For example, there have been times that I’m reviewing more code than everyone on the team combined. I WANT my manager to know that’s happening and figure out how to even the workload. Or, why is my team shipping like 2-3 times as many PRs as a similar team with similar headcount? It’s not immediately a PIP or something, but it’s highly likely something odd is happening. Could leadership improve direction & focus, make priorities more obvious?
The problem with this feature is that the agents could realize the phone was being wiped. For the duress pin to be 100% effective, it would have to log in normally to a default install.
> Increased tactile stimulation of the hind legs causes an increase in levels of serotonin.This causes the locust to change colour, eat much more, and breed much more easily. [1]
You could jump on a train from NL and be in Belgium in 15 minutes, get a "bootleg" physical copy of the diary and head back to NL. No one is suing for that.
In Baarle-Nassau you can walk a few hundred meters and cross the border multiple times https://en.wikipedia.org/wiki/Baarle-Nassau. Or even walk within a house and cross the border.
Watch his lecture series on YouTube. We you started programming, you had to adapt your brain to the way of thinking of computer programs. Think of this as an continuation of that evolution, were you acquire new methods of reasoning that can abstract many apparently different problems into the same concept.
In a different comment thread, someone mentioned the book, Category Theory for Programmers. Here's the Releases page with PDF files (click to open the Assets section). https://github.com/hmemcpy/milewski-ctfp-pdf/releases
There are several versions with code examples in Haskell, OCaml, ReasonML, and Scala. These are all typically associated with functional programming and category theory. However, category theory is a much wider and deeper subject than any specific language, and deals with mathematical objects and concepts relevant to (more or less) all of programming.
Meanwhile in Germany I see, quite literally, 12 traffic signs on a 100m stretch of road. I'm pretty sure that looking at all those signs adds up to a few seconds at least.
In dbus, it seems the feature is intended for two processes to know they can access the same shmem and other system resources. I'm struggling to understand in which circumstances would that be useful.
Creating an excuse for creating a machine-id to associate with network traffic. Sometimes, it is enough to have a plausible enough sounding reason to write down on paper, but you have to look at what something actually is. Any red blooded hacker knows there's what a tool is meant to be used for, and then there's what it can be used for. Less is more.
reply