506 karma · joined May 19, 2020
I assure you, it wasn't random. It was punitive. ;)
I have someone who we lured to the team by offering 4 weeks off in the first 2 months of his employment so he could do a pre-planned trip. Didn't require any special approvals because it's just an SOP.
I have someone who regularly takes 2-3 days off every month, because he works in concentrated bursts of energy, then needs to decompress.
And of course, I have one person who NEVER takes time off, because they always have so much to do and are afraid to let a ball drop. This leads to overwhelm, and a ball drops anyhow. So I need to force them to take time off.
As with all things, it's not just the mechanism, but the environment that mechanism exists within. It needs to be deployed alongside strong accountability mechanisms - planning, goaling, 1:1s, team health assessments, and performance reviews - otherwise it can be abused, or it can be hard to say 'no' to a request, or it can be hard to know when people aren't taking time they need.
But if you've done that, it's an incredible tool.
[0]:https://github.com/privacycg/private-click-measurement/issue...
Tens of thousands of developer hours went into making the Meta family of apps and advertising systems respect ATT, including working directly with Apple engineers to iterate on the privacy-preserving alternatives to pixel tracking in the context of the in-app browser. Whatever they may have said in the public sphere, when it came to actual compliance they followed not just the letter of the new requirements, but the spirit of them.
If this isn't an easy win for them, it will show just how much of an impact public perception has on the outcomes of legal cases.
If you’d like to chat, reach out.
It's almost more impressive that people know who it is without saying the name.
What would it take to programmatically port/transpile the core of Erlang's ecosystem to Elixir?
Pick the killer app to serve as the root node (Phoenix?) and walk back to the leaves (OTP, popular libraries, etc). Do a 1-time cutover of literally everything. Fork/port ERTS (incl BEAM) to make Elixir-native and rebrand it. Etc.
While I generally agree that "rewriting as bad" there is something to be said about the importance of _ease_ when bootstrapping and scaling an ecosystem. You're either stealing mindshare from an established ecosystem, or you're capturing new minds as they come in.
IMO Elixir/OTP is too radically different from other very-large ecosystems to benefit from transfer learning for junior/mid-level people (great similarity w/other smaller fringe ones, like Ruby, Clojure, etc, but that won't get us there), and the most senior people fall into the "it's all the same at the end of the day" trap and don't put in the energy absent some strong business driver. So you really need to reduce even the shallowest cognitive bumps to get escape velocity.
"It's paid!"
"It's not multi-platform!"
"It doesn't support my language!"
Dear Zas Editor creator:
Good on you for creating something that solves your problems and challenges you intellectually.
Good on you for putting yourself out there by making it public.
Good on you and for making your efforts sustainable by charging real money for it.
Good on you for taking the first step, and shipping before it's "perfect".
Good on you for taking feedback graciously.