392 karma · joined December 10, 2016
"je ne sais quoi", i.e. "I don't know (exactly) what", or an intangible but essential quality. :)
e.g. https://blog.pragmaticengineer.com/project-management-at-big...
Similarly the article on OKRs describes small but critical adjustments from the OKRs cannon (Measure What Matters) that only scale-ups and Big Tech seem to know about. Everyone else too often tries to:
1. Cascade OKRs down from the top, sometimes outside Product & Engineering (in teams that are more process- than project-based like sales), killing team-level autonomy in the process.
2. Write Objectives for time consuming activities, rather than having a non-OKR work / BAU section that captures it. This makes it much harder for other teams to rely on OKRs to understand the context of what’s changing and to have key cross-team alignment conversations.
3. Focus on OKR tracking and scoring, possibly through a dedicated tool. This misses the point that the primary value of a plan is in the planning, not the deliverable, and risks making OKRs a performance management tool (at which point teams discuss KRs endlessly to sandbag rather than setting stretch goals and moving on).
But when you say the local implementation looks both overkill and misguided compared to what works at other tech shops, people point to the OKR book as what drives their own implementation. :)
> We’re maintaining mistral-medium, which we are not updating today.
As a French speaker, I parse this to mean: "we're not releasing a new version of mistral-medium today, but there are no plans to deprecate it."
edit: but they renamed the endpoint.
Second, whether DNA can or cannot remain confidential is yet to be seen, but feasibility is certainly orthogonal to whether it ought to be, which is the point at hand.
Third, whether you believe it's a breach of privacy to leak part of your relatives' DNA is besides the point. It's their decision to make, since it's their personal data and deemed confidential under most privacy frameworks, and therefore a breach.
Would you say that building a “toy solver” for hold em could be a fun way to learn or improve with a language? I’d be curious to see how much work is needed to approximate the shape of the real GTO charts and common bet sizes.
“There are three ways to make a living in this business: be first; be smarter; or cheat. Now, I don't cheat. And although I like to think we have some pretty smart people in this building, it sure is a hell of a lot easier to just be first.”
Not sure about cheating being off-limit given the crypto debacle…