I don't disagree on the whole. But I think that putting 'trust' in any bot would be silly. However, knowing how right-skewed the bot is and using its blurb as a single data point with that in mind, is better (to me) than just not having it at all.
Hey admins. This one right here...
Iritis/uveitis - My cornea detached due to the heavy pressure inside my eye. The most painful thing EVER.
Kidney stones - Close second
Motorcycle accident at highway speed that jammed gravel into my cranial cavity and left me looking like watermelon-head for 3 months - I'd still rather have this than kidney stones or iritis...
I think we agree. CEO should not be making decisions from a technical point of view, so they should not be second-guessing the technical people.
I'm at the stage of my career that pretty much every job I take, I report directly to the CEO. And the difference between what they should do and what they actually do is why I made my statement at the top of this thread.
Why not consult the people who actually know their stuff?
I mean questioning as in second-guessing the people who actually know stuff. Not asking experts for their honest thoughts.
Don’t you think that management could use your help and advice to make good strategic decisions in the long term?
Management is one thing - C-levels is yet another kettle of fish.
In my experience C-levels rarely want the technical answer to a question, and will be personally insulted / defensive if the answer is something they don't understand. And they will ask their questions in such a way as to insult the expert. Two negative results that don't help the business in any way.
But Dept heads and the PM office will often be able to explain why certain choices were made, and how that aligns with the business needs, without the complexities that cause misunderstanding between two people of such wildly divergent skillsets.
Now if the CEO can also write the code, or run the wetlab instruments, and really does want the nitty-gritty, complex technical answer, that is a different story. And rarely the case in my career.
Long term strategic thinking, experience to understand when trends and short-term solutions would be long-term mistakes, and the ability to avoid directly questioning someone with a skillset they don't have themselves about technical or complex issues.
Go through an intermediary. Like a department head.
The developers, engineers, and architects don't need your help, they need you to set logical long-term goals, hire good department heads, and schmooze with other CEOs in the same space.
We've been married 15 years. If we use a first name to address each other it usually means we are out in public and trying to find one another. And that is only because if I shout 'QD(cutie)' 5 women will turn around thinking it is their SO so it isn't super useful.
If you bugged our house you would think my wife's name is Dear, QD, Darling, Beautiful, or "HOLY SHIT CHECK THIS OUT". There is almost no chance you'd catch either of our real names on that tape.
popos tiling works this way as well.
One vote for not refederating. Please leave hexbear where they are.
On chromium check out deluminate.