Readit NewsIf you know a "customer" of yours (an individual employee) is only going to be with you until they either change jobs or go on Medicare, then it seems the name of the game then is to make sure that nothing catastrophic happens to them until you can hand them off to someone else.
In which case, they should definitely go on ozempic. Even if the effects of ozempic immediately come off after usage, it's a short-term enough solution that benefits the insurance company, no?
The problem is, prediabetic and folks who may have crossed 7.0 A1C once, and just overweight folks with docs who are willing to play fast and loose are demanding it. Skipping metformin and other first line treatment options that are way cheaper. For those folks, complications might be the next guys problem.
And god forbid I try and provide fresh fruit and beverages on that budget…
Why is Zhou pronounced that way?!
Right, but in this case they only give you one of the two numbers. Imagine being told that your TV had an aspect ration of ":16", and you just have to magically know what the other number means in the context. And sometimes ":16" actually means ":4", because quadratic mumble mumble, and sometimes the number is scaled according to some other "how big it seems to humans" factor; all of which you also just have to know in context.
Microsoft's revitalization occurred only after Steve Ballmer was ousted and Satya Nadella pushed out much of the old guard who were set in their ways.
I took a class co-taught by TBL called Linked Data Ventures (6.898). There was an effort to seed a Semantic Web startup ecosystem with project teams formed in the class. IIRC one of the groups did get funded and was eventually acquired, but not using Semantic Web/Linked Data.
Regardless, it was an amazing experience having TBL review our little demo app.
A human expert needs to identify the need for software, decide what the software should do, figure out what's feasible to deliver, build the first version (AI can help a bunch here), evaluate what they've built, show it to users, talk to them about whether it's fit for purpose, iterate based on their feedback, deploy and communicate the value of the software, and manage its existence and continued evolution in the future.
Some of that stuff can be handled by non-developer humans working with LLMs, but a human expert needs who understands code will be able to do this stuff a whole lot more effectively.
I guess the big question is if experienced product management types can pick up enough coding technical literacy to work like this without programmers, or if programmers can pick up enough enough PM skills to work without PMs.
My money is on both roles continuing to exist and benefit from each other, in a partnership that produces results a lot faster because the previously slow "writing the code" part is a lot faster than it used to be.
The one key point is that I am keenly aware of what I can and cannot do. With these new superpowers, I often catch myself doing too much, and I end up doing a lot more rewrites than a real engineer would. But I can see Dunning Kruger playing out everywhere when people say they can vibe code an entire product.