I’m going to be #authoring a book in the coming weeks. First time in this process. Looking for #publisher candidates who would be interested. Subject is non-fiction — business leadership, economics, organizational psychology and the emergence of #AI. Any recommendations?
Sam Briesemeister
- 86 Followers
- 114 Following
- 420 Posts
Engineering leader working on something in #Kubernetes. Stealth startup currently. Formerly AWS, Mesosphere/D2IQ, Samsung.
Consultant in #devops, software engineering, business intelligence & #analytics.
@[email protected]
@randahl given what he told the Japanese about surprises and secrets, I’m starting to wonder if he should be removed from office for disassociative personality disorder.
@praetor no shame intended in any sense. I too have spun side projects in various languages for fun, C occasionally too. And occasionally also deciding to reimplement it on another language for some theoretical advantage. Not sure that’s ever paid off though.
@praetor it’s ok. Give in. Just a little bit. You won’t regret it… until you do, and then you’ll either adopt rust, or go back to something where you can use a language that hurts less.
A developer who just writes code, without understanding the system they’re working on deeply, is a liability. An engineer who understands the system can prevent risks.
The recent production outages at AWS, supposedly induced by AI-generated code, tell you that they’re using it the wrong way, in this context.
But there’s a reason I don’t hire people who just write code. I need systems thinkers who love to collaboratively innovate.
@RonJeffries by that argument, shouldn’t a board seek a new CEO within a quarter, after each layoff?
@nina_kali_nina not long ago, I was "wtf did they do to my icon spacing" years old...
tim@jerry so, put differently… short term incentives screw up all kind of analyses… but in effect, in this industry, revenue projections look good when you have capital and expertise to quickly deploy and integrate new gen platforms, but they’re so power hungry that access to power infrastructure is also a competitive supply chain concern.
No power: no GPUs. No talent to quickly operationalize: bad customer experience. No capital: get left behind on older generation.