If genuine, this finger pointing is an interesting approach to a security vulnerability. Last time I read such arguments was 20 years ago from a different firm in California and it was not to their advantage.
Great idea. I had been thinking about pretty much the same but perhaps targeted at executives and perhaps including AI/Cloud.
I usually feel to many people wildly through around terms they hardly understand, in the belief they cannot possibly understand. That’s so wrong, every executive should understand some of what determines button line. It’s not like people skip economics because it’s hard.
Would love to perhaps contribute sometime next year. Stared and until then good luck - perhaps add a donation link!
Thanks! I completely agree. For more than ten years consulting, training and architecting systems for clients across government and enterprise, I have seen the same pattern. Long before "big data", "cloud" and now with "AI" and "GenAI" these buzzwords have often been misunderstood by most of the C-suite. In my entire career, explaining the basics and setting the right expectations has always been the hardest part.
I really like your idea of targeting executives and connecting it to real business outcomes. Getting decision makers to truly understand the fundamentals behind the technology would make a huge difference.
I hope the next generation learns to love "C" and Algorithms again. I have rediscovered my appreciation for C recently, even though Go is my main professional programming language.
You’d be surprised how much trust people place in legal departments, balance sheet strength and talent capacity. All things for which I had to turn down superior technical proposals in the past. The old saying „Nobody gets fired for buying IBM“ still runs strong.
Free e-signatures are a great idea, have you considered getting a foundation to back the project and maybe taking out some indemnity insurance, perhaps raising a dispute fund?
Financial institutions and governments don’t spot crime because of incomplete information at individual firms. We help them understand federated learning and how to effectively collaborate and not just talk about it. All code is open source, so you can always help out ;-)
This is awesome and I wish more of this were happening. Hardware home labs are the best way to learn. I gained most of my Linux/FreeBSD skills at home.
It feels with cloud computing a generation of computer scientists kind of missed out on the experience.
That’s nailing it really well: “willfully ignoring” is precisely what’s happening all around me. Me talking about small focused AI models, there you have everyone raving about AGI.
Energy use and privacy issues of cloud vs local inference discussions end on how awesome the power of GPUs are and the jobs too.
GPU backed finance with depreciation schedules past useful life seems OK for anyone chasing some short term gain.
Even the job market is troubled, you can hardly tell a relevant candidate from an irrelevant one because everyone is an AI expert these days - hallucinations seem to make lying more casual.
It’s pretty clear to me there is a collective desire to ignore the problems to sell more GPU, close the next round, get that high paying AI job.
Part of me wishes humans would show the same dedication to fight climate change…
I wonder if the buying customers of Nvidia are going to find the self’s left with the overcapacity. Certainly people are waking up to LLM challenges and as budgets focus more on useful applications, smaller language models, how much of that demand will remain.
Also, depreciation schedules beyond useful life of an asset may not be fraud but I’d call it a bit too creative for my liking.
It's been a while since I've used CloudWatch myself. How would you expect this? IE would you lean more towards having a lambda/firehose that forwards events to to the API (which is [public](https://tailstream.io/docs/api) by the way!) or would you expect some kind of agent / connector to run that automatically pulls the logs from CloudWatch?
I do not have any specific perspective on how this is best done. I believe being able to run inside a closed environment might be preferable, logs do contain pretty sensitive stuff. Perhaps a container that pulls from CloudWatch might be an option?
P.S.: where did you see this discussion?