The current vibe at Apple is "we want you to be an obedient worker".
[0] https://systems-souls-society.com/what-is-this-the-case-for-...
I know there are still a ton of good people there, but it's a way, way different company now.
The current vibe at Apple is "we want you to be an obedient worker".
[0] https://systems-souls-society.com/what-is-this-the-case-for-...
I know there are still a ton of good people there, but it's a way, way different company now.
This vibe was pervasive at Apple and could be taken more or less for granted, but elsewhere it’s all over the place.
And, like, sure, there are projects and industries where this doesn’t matter. But giving a shit and feeling it can be a major differentiator.
That, and with Ruby, Node, and at least one other language/tool IIRC, when support for those things moved internal, we had to make a bunch of changes to our scripts to handle that change with effectively no warning. That involved checking to see if the third-party plug-in was installed, uninstalling it if so, and then installing the language based on the built-in support. In the meantime, the error messages encountered were not super helpful in understanding what was going on.
I’m hopeful that these types of issues are behind us now that most of the things we care about are internal, but still, it’s been pretty annoying.
I put my hope in mise-en-place - https://mise.jdx.dev
What do people think? One tool per language, or one to rule them all?
However…more than once we've seen language runtimes that used to be available exclusively via plug-ins be migrated to be internal to mise, which broke everyone's setups in strange and hilarious ways, and caused countless hours of debugging.
Less bad overall than using individual runtime version managers for sure. But the next time mise costs us a bunch of hours fixing multiple engineers' setups, I intend to find another solution, even if that means writing my own. It’s burned us nearly one too many times.
Sorry, but despite your best intentions, even those long hours are wrong and unnecessary. It's the leadership's planning skills and inability to take responsibility of the exceptional circumstances. In such a situation good leadership just cuts scope without flinching and reflects to avoid a repeat.
edit: typo
As a hiring manager, I _vastly_ prefer hiring someone that values work-life balance over this grind culture bullshit. YMMV, but in my experience, the folks that care about balance tend to be more focused and productive during the hours they are working.
Of course, exceptional circumstances exist where long hours are required. Not disputing that. But making that the default for the company culture is insane.
I do hope Kagi eventually has enough revenue to offer a more generous free tier, though (and without logging in). I fear it will remain a niche thing otherwise.
One of the worst hires I ever worked with was excellent on paper, came with good credentials, had an impressive resume, and did objectively well on the interview questions.
However, everyone who interviewed him felt uneasy about him. He failed the vibe check, even though he checked all of the boxes and knew all the right things to say. At the time there was a big push for eliminating bias and being and as objective as possible in hiring, so we were lightly admonished for raising questions based on vibes.
When he was hired, it turned out our vibes were justified. He was someone who played games and manipulated his way through his career. He could say the right things and navigate his way through office politics unscathed while causing damage to everything he touched.
Since then I’ve observed a number of situations where decisions that seemed objectively good but came with weird vibes were later revealed to be bad. Some of the most skilled grifters I’ve encountered were brilliant at appearing objectively good but couldn’t pass vibe checks of experienced business people. Some of the most objectively good deals on paper that came with weird vibes later turned out to be hugely problematic.
I think the trap is thinking that vibes and feelings are wrong and should be ignored in favor of pre-selected objective measures. This is good practice when doing a scientific study, but it’s not a good practice when you’re entering a real world situation where an adversarial party can root out those criteria, fake them, and use your objectivity against you.