Comment Re: It does it poorly (Score 1) 86
No, they designed it right. You are supposed to *walk your bike across the street*, not ride it across.
No, they designed it right. You are supposed to *walk your bike across the street*, not ride it across.
Exactly! THIS is what all the hype is really about (but is not well explained). Software, world wide, is almost a 1 trillion dollar business. AI *if it never did anything else useful - ever* can accelerate that trillion dollar business (slated to be 2.2 trillion within a decade) from profit margins of 60% to 90% or more. Hundreds of billions a year, just in the US, in additional revenues and profits. And accelerating over time as software gets cheaper, better, faster; and the AIs get cheaper, better, faster as well. And all we need to do to get that is build a few, several hundred billion dollar data centers? Basically a one time cost? Sign me up!
And on top of that, AI can speed drug development, basic materials research, provide cheap personal assistants for anyone that wants one, operate autonomous vehicles, improve agriculture, and operate autonomous robots that toil alongside us in factories.
And that's just what I can think of off the top of my head.
I also assume it is coding assistance. But $150K in tokens / year is the cost (not salary) of another engineer making about $110K. Assuming that LMB is paid roughly that, I would say that if he is doing the work of 3 people, the company is coming out WAY ahead on that deal.
If he is doing the work of 2, it's break even, if more than 3, the company is making bank with this arrangement.
In addition, there are other benefits too - more intangible. Like better morale - seeing stuff come together faster is very satisfying for a SW engineer. Faster, smoother implementation of features helps the 'flow' - leading to better software coming together faster. Better architecting - because AI is doing more of the low level coding and 'shoveling coal' as I call it - leads to more focus by the SW engineer on the overall design. That leads to finding and fixing the holes in that design faster.
Tough to measure, but adding to the benefits.
I think the quote from the original Blade Runner said it best:
"You're either Cop, or you're little people"
Because of a draft policy that someone "not in the know" got hold of, informing the public. The immediate and widespread outcry then causes the policy to change back quietly before going into effect, driving the irate drafters back into dark spaces - convinced they are now going to have to wait almost a YEAR (the horror!) before trying to arm police drones again.
Darn meddling kids!
Exactly. Best put as "Life is pain. Anyone tells you different is trying to sell you something."
Kudos Ledow! Nice! Just one piece of advice though - if you are thinking seriously about disconnecting from the Grid, please look into all the ramifications thoroughly. In many municipalities being Grid-tied is a requirement for a building to be considered "livable" - you don't want your home condemned on a technicality. And that's just one factor - there are others I'm sure I don't even know about.
I plan to do what you've done - probably more in a one-shot than grown over years - and I'll always keep a Grid tie regardless of how well energy independence works out - never hurts to have a Plan B (or C and D for that matter).
Indeed - I bought United Health on their big dip - it's up more than 35% since then
So, let me see if I understand correctly:
Your leadership gave you access to a new tool, without any training on how to use it.
A budget to only spend $45 worth of "work" from it. Each. Per month.
Assuming you make about 90K in yearly salary that works out to roughly 1 hour of your time. So if you can use the tool, only spend $45 in tokens, and get MORE than one hours worth of saving from it (magically, without any training in it mind you), you are WAY ahead.
"And we blew through that in 2 days" - what did your management expect? I mean actually, what were their expectations? That they could spend $45 a month and double your output? Wouldn't that be a treat!
Yet another key part of this arrangement is scale - GE has 450 workers in this "pool", so, on average, there is plenty of coverage for all the work GE needs doing.
Smaller employers cannot make use of this - with a smaller pool of say 50 workers, there will be many times when the workers availability (and unavailability) will leave gaps in the work schedule.
Also, the employer must, to some degree, be able to "batch" the work, and not have hard deadlines, so that having more labor at some times and less at others can still be useful. Probably would not be possible on a car/aircraft/etc. assembly line.
At Case Western University, USA.
I "speak" 11 programming languages. So that means I have the brain of a 12 year old!
Wait, that didn't come out right....
I'm old enough to remember that back in college, engineering majors were still gently being push to try to learn German (being dubbed the "lingua Franca" of engineering at the time).
And almost old enough to remember riding dinosaurs. Good times!
If that is the case, then it all makes a whole lot more sense. There is no need for cost-efficiency when dealing with military equipment - the only question to answer is does it do what is needed for the GD system? And if what is needed is processing tracking data and generating firing solutions locally, without multiple trips back and forth to orbit, then making it work is the key, not cost or complexity (to some degree, even the DoD has limited funds).
About what I expect: Bottom line is, if the battery company warrantees them for 10 years, and is planning to BE around in 10 years (i.e. buy from an "established big name player") then I fully expect them to last a good bit longer than 10 years.
Whom the gods would destroy, they first teach BASIC.