This is what I don't understand about this policy. There's no way a senior has enough spare capacity to be the gate keeper on every PR made by AI below them. So now we are just making it so the senior people use more AI to keep up but now they're to blame for letting it happen.
It sounds like a piss poor deal for seniors unless senior engineer now means professional code reviewer.
That's amazon in a nutshell though. Create conflicting metrics for performance, push credit up and responsibility down, punish everyone below you for not meeting the double standards
> Create conflicting metrics for performance, push credit up and responsibility down, punish everyone below you for not meeting the double standards
This resonates with my experience.
The only thing you forgot is that you can also use the 12^H^H 14 leadership principles to argue whatever you want (and then the opposite of what you argued last month, still using the same leadership principles).
Got a project finished early? Well, you didn't insist on the highest standards. Made sure things were held to a high standard? Well, you weren't biased for action.
Were you a knowledge source for the entire team? Well, you weren't learning and being curious. Did you ask a lot of questions to learn everything? Well, then you weren't "are right a lot".
Did you think big and come up with an architecture that saved Amazon a lot of money? Then you weren't inventing and simplifying. Build something simple to get out out the door quick? Well, you weren't thinking big.
Did you act quickly without consulting others to fix an issue? Well you weren't earning trust. Did you consult people to make sure they were happy with the solution? Well you weren't biased for action.
Very nice, I can imagine someone turning it into a little satirical webpage, which implements a kind of decision tree:
1. Choose from a set of challenge types (e.g. meeting a deadline, reliability)
2. Choose whether the challenge was "met" or "failed".
3. Choose whether you want to make the person look good or bad, by following/ignoring a principle.
4. Results: A list of relevant principles with short rationalizations.
I'm almost tempted to try, except perhaps I should treasure my ignorance.
If a tool like that gets popular enough that most employees are using it for office-politics, it might even start to deflate the whole Leadership Principles thing.
Early in my career I tried very hard to "be concrete, cold, and direct" because that's what I thought a good communicator would do. It was seen as attacking to anyone below me and confusing to anyone above me. I was naive and I suffered for it.
I definitely agree with what you're saying here where these words actually do mean something, but it's completely opaque to those outside the "know". I also have found that there's not any better way to express information to those in the group than in this coded language, even if it makes completely no sense to me.
I wish younger me understood that the way I'm being perceived is the only important thing, not choosing the "best" words to technically describe a situation
This feels like such a valid solution and is how past $dayjobs released things: send to the free users, rollout to Paying Users once that's proven to not blow up.
If your target is security, then _assuming your patch is actually valid_ you're giving better security coverage for free customers than to your paying ones.
Cloudflare is both, and their tradeoffs seem to be set on maximizing security at cost of availability. And it makes sense. A fully unavailable system is perfectly secure.
This is the reason I left the "main" social media and what keeps me from engaging too much with Reddit/HN or any of the other new hotness like Mast, nostr, BlueSky, etc: it's just rage baiting or karma farming
Mastodon is pretty much anti-that. No algorithm. If you don't like something, you just don't follow it. Nothing defaults to the instance/global timeline either and you're free to mute anything.
This hasn't been my observation. Yeah you can mute whatever you want (you can on Twitter and Bluesky also) but the HOA tendencies of Mastodon servers are alive and well. If you're a very online type of person and "live and die" by online social currents then no problem, but for others I'm not sure.
This is a good callout/distinction you're making. How we view the goal of the experience determines our experience itself. The guitar analogy is really good because if your goal was to learn guitar, it's definitely not wasted but if your goal was to learn this one specific song as quickly as possible, I could see how my perspective would be different.
Yes, this is all goal dependent. I can agree with that.
The trouble with the "learn just this one thing" approach is that one is forced to learn said thing at the most basic level because anything beyond that requires all sorts of skills and techniques that are difficult to teach in lesson format. Rather, they're just absorbed as one explores the topic. It's the sort of subconscious / muscle memory stuff a person doesn't even realize they're learning.
So, yes, for the most basic of topics, I can see how removing the effort can make sense. For anything beyond that I feel there is tremendous value in the struggle.
Cannot agree more to this sentiment. I call it "throw away code" and it's always seemed like the easiest to change in the future, and we all know everything is gonna change in the future.
BM25 is definitely a big deal when you're doing FTS. It's one of the reasons I've switched to Arango as my DB for the project I'm working on that needs FTS. The fact it also comes with graphs means I don't need to bang my head against CTEs either.
Not saying Arango can replace Postgres but for my needs, it's a much better fit AND it offers the FTS that I need out of the box.
Arango is sweet! We've actually talked to many people who switched from Postgres to Arango because of its better FTS. This was one of the reasons for creating ParadeDB in the first place. Many of the users who made this switch wished they could have stayed in Postgres without compromising on FTS.
It sounds like a piss poor deal for seniors unless senior engineer now means professional code reviewer.