I've heard that at companies that did stack ranking, managers of groups with high performers would actually seek out poor performers who didn't care about their ranking from other groups, to add to their group so that they wouldn't have to give a poor mark to their own people. These poor performers became hot commodities. Talk about gaming the system...
I've seen this happen. The best part is when attrition is bad enough in some cycle that the poor performers stick around... and now the managers are really in trouble!
It can be difficult for line managers to fire their entire team.
> These poor performers became hot commodities. Talk about gaming the system...
Couple iterations of that and you'll have people who are hired and/or paid extra for the purpose of being a "fuse" that protects the high performers during layoffs by being first to get fired.
I wonder how I could signal my willingness to be a H2F candidate. I could see doing this, for example, to make a few bucks in pre-retirement: 1. Get hired as the sacrificial lamb, 2. Do nothing (or the bare minimum) for 11 months, 3. Start interviewing again one month before I know I’ll be stack-rank fired, 4. Get hired as another sacrificial lamb at a different company that does stack ranking, 5. Goto 2.
Everybody wins. I get a salary for doing nothing. Hiring manager protects his team from a cruel system. High-and-medium-performing coworkers are secure in their jobs. Recruiters meet their hiring goals.
My joke (?) proposal for a contracting business was "Scapegoat Solutions". You're a manager somewhere with a project which is of course late, over budget, crappy quality? Your bonus, or even ass, could be on the line? Never fear - just contract us to "work" on your project for a quarter, we'll drink a little coffee, play some Kicker, twiddle some files in your SCM, then you ceremonially fire us while bewailing the outlandish harm we did to your otherwise well-managed project, explain to your Lords & Masters that it will take months to right the ship... Obviously we're blacklisted as "No Hire" for your company - at least until the next time you need our well-remunerated services...
I had a roommate that had a real business doing such a thing. If a company/person fucks up and needs to apologise but are unable/unwilling for $REASONS, that's where my roommate would step in and literally apologise for them. He would even be provided with name cards and in some instances, underlings to look like an important person.
I tried very hard (google & wiki) to look for an English term but I failed. It's 謝罪代行 in Japanese. Literally Apology as a Service.
Fascinating! So the recipient of the apology is generally unaware that it has been outsourced? Or do they still find it soothing, as bereft family do with professional mourners?
I wonder when something similar will appear for e-commerce.
It seems to me that the process of dealing with customer complaints is pretty well tested and routine at this point. Apologize, either eat the loss (if the problem is serious or not worth the hassle) or spin some BS story (if it's not), then politely ask the customer to rescind their negative review on the e-commerce platform - and if the customer is not cooperating with that last step (which is the most important one for the vendor), continue through pressure, begging and offering freebies.
I feel the whole dance could be outsourced to a professional "customer complaints service", and improved effectiveness would let even more bad sellers thrive with near-perfect review scores for even longer.
Sorry for a tangent to a tangent, but I keep hearing this being said all the time as something negative - even though it's obvious, natural, and how everyone says it should be. Some ways of promoting this arrangement include statements like:
- There's no "I" in "team"
- Team productivity matters more than individual productivity
- Most valuable employees are force multipliers for their team
- Being 2x multiplier for a team of 5+ beats being a 10x engineer
Etc.
How do people saying these things (and this is nearly everyone, it's the industry zeitgeist) think it works in practice? That you can skill up in being "a force multiplier for a team"? That you can grow your team multiplication factor from 1x to 2x to 3x to ... in isolation, and then slot yourself into any team to give them an instant bonus?
No, any kind of force multiplication is achieved through working relationships. The fuzzy stuff. Two people equally competent in their field and with equivalent EQ aren't freely swappable between the teams, because they don't have identical personalities, quirks and habits. Force multiplication involves people working together for some time, molding themselves to fit each other.
In the process, people working well together grow to know and like, or at least respect, each other. They become each other's "first on the list for X", or "example of how to do Y". Which is exactly how "it's about who you know" works in practice.
I think that the extent to what you say is true depends on who has hiring power. The farther removed from the actual team hiring decisions are made, the less someones ability to work effectively matters. If you can convince some MBAs you’re a 10X programmer, it may not matter than you’ve left behind a stream of teams that disliked working for you. If all hiring decisions are made by a team lead with no subject master expertise, you end up in a similar situation. It’s ultimately the case that it comes down to convincing the person who will hire you that you’ll act as you described, but in tons of companies the person you’re convincing isn’t actually the person who has the insight necessary to judge what you’ve said.
Great vocabulary word, and perfect description of the activity. "Half-lies [...], told [...] as a fantasy, suppressing unpleasant parts of the truth.
I respect OP (TeMPOraL), he(?) has a long track record of great comments and insights on HN. I always look forward to his comments. But what he is describing is kind of a fantasy that we tell ourselves to get through the unpleasantness. Or more accurately, it's how the working world works in theory, but not in practice. "Team productivity" "Individual as force multiplier" these are phrases straight out of the employee handbook. It's how the company pretends career development works. And a lot of people believe it!
How it actually works is like High School. There are cliques. There are in-groups and out-groups. If you're part of the in-group, you're going places. Your individual performance sometimes matters, sometimes doesn't. Your actual teamwork and team accomplishments sometimes matter, sometimes don't. If you're in the out-group, nothing you do matters. You could be Ken Thompson but if you're not in the right clique, your career is going nowhere.
I've seen it almost everywhere I've worked. A low or medium performer manages to charm his way into the right clique, get liked by the right exec, and his career skyrockets, despite spotty actual work output. Despite their projects failing, despite their direct reports quitting. All the way up to Director level at FAANG--the sky is the limit. All because they got into the in-group and befriended the right people. I've seen top performers stagnate and quit out of frustration, because despite both great individual output and team success, the VP just didn't like the guy, and that was that. There's no way around it. I had a boss who picked favorites and villains. If you were the Golden Boy, you could do no wrong, and you were on track for promotion purely for being in her favor. If you were the unlucky villain, you could do no right and ended up just being a punching bag.
The actual corporate world in practice is nothing like the optimistic and egalitarian employee handbook. It's 80's High School again with jocks and cheerleaders and dweebs and losers.
> But what he is describing is kind of a fantasy that we tell ourselves to get through the unpleasantness. Or more accurately, it's how the working world works in theory, but not in practice.
I think I've failed to communicate clearly that I don't buy into the fantasy. I mostly agree with your description, though I think reality is somewhat better on average than High School. The "school dynamics" at workplace are moderated a bit, as the market adds a degree of back-pressure to which adults are more sensitive than teenagers - basically, someone has to do some things right at least some of the time, or else companies go under and people lose their livelihoods.
My point is that you (the generic you) can't at the same time extol teamwork, being a force multiplier, etc., and also complain that the working world is about "who you know" and not "what you do". Those are two sides of the same coin. Strong teamwork requires people to adjust to each other, and over time this does create an in-group of sorts. People learn to trust each other, and become "better than random" choices for each other for future opportunities.
If the professional world wants to double-down on humanity, team-building, collaboration, then it must also find a way to live with how the humane, social aspects actually work - people build relationships, webs of trust, and tend to favor those connections strongly, because they're the known quality, the variance-reducing, safe alternative to random outsiders. Conversely, if the professional world wants to double down on blind fairness as a principle, then it must stop with the "good team work > individual competence" mantra. I don't think you can have both - they're fundamentally opposed.
And personally, I haven't made up my mind on which perspective I prefer. (Or even my reasoning here is sound.)
How is this not a fraud on the part of the company that hires-to-fire? They have no intention of actually following through on the employment contract.
I was thinking about specifically asking people, whether already hired or those about to, to become "sacrificial parts"[0]. The difference between this and "hire to fire" would be that in my scenario, these sacrificial employees would enter the deal voluntarily, fully aware of their purpose. Extra compensation would be there to offset both the immediate hassle of searching for a new job and damage to work history on the resume of such sacrificial employee.
Circa 2006 I saw a friend who was a manager do exactly this. There wasn't stack ranking. He just kept a low performer on his team to sacrifice to the RIFs when they came through.
The bad thing is that this is predictable behavior and management still does it. Should the suggestion get grouped into the 5% of low performers? This is clearly damaging to overall work morale and company goals. And not to an insignificant part.
What would you give for that performance? I cannot see anything that would benefit the company. Not even employment costs, because employees certainly price that in.
> It feels like Rust’s design guides you towards good abstractions and software designs.
> The compiler is very picky, but once code compiles it gives you the confidence that it will work reliably.
> Sometimes I had trouble making the compiler happy with the design I was trying to use, and then I realized the design had fundamental issues!
I experience a similar sentiment all the time when writing Rust code (which for now is admittedly just toy projects). So far it's felt like the compiler gives you just enough freedom to write programs in a "correct" way.
I don't really do unsafe/lower-level coding, so I can't speak to much there however.
I've seasoned my cast iron pan many times. I don't think it ever beats teflon, though it gets to a point where things wash off of it pretty easy with just water and a chainmail ringer.
As others have mentioned, there are a ton of off-the-shelf solutions that would have been more than adequate for this.
My question is, why didn't he go for any of the existing solutions when setting them up would've still been faster than rolling his own DB-in-a-JSON-file solution?
I'm not a business guy, but if Apple's going all-in on ARM processors, and then they expand into the server market (which the article speculates on), could we potentially see Apple opening a new product branch devoted to competing in the Cloud space with AWS, Azure, and GCP?
Imagine developing apps on an ARM-powered macbook, deploying onto ARM-powered servers owned by Apple, specifically for applications to be used on MacOS & iOS devices.
I've been using Invision's Freehand tool [0] for whiteboarding in online meetings (also it's free). It's mostly worked about as well as a virtual whiteboard could be. It also allows for collaboration so everyone can draw on the same whiteboard at the same time.
The issue with that though is that if someone could read/write code, they would probably choose to be a SWE instead of a tech writer.
I'm not sure why this is, but I suspect that it's an combination of higher pay and an interest in writing code over writing documentation.
In my experience I would say that a good SWE will attempt to write good documentation, as having to answer questions in the future about how stuff works over and over takes more time than just documenting things properly the first time.
I don't think adding Postgres support would be that far fetched, have a look at https://github.com/infostreams/db/tree/master/bin/drivers/my... for example to see the meat of the load & save operations. You'd have to implement it twice though, once for local servers, and once for remote servers (via ssh).
