deepGem
Now that their minds are free from routine and boilerplate work, they will start asking more 'whys' which will be very good for the organization overall.
Take any product - nearly 50% of the features are unused and it's a genuine engineering waste to maintain those features. A junior dev spending 3 months on the code base with Claude code will figure out these hidden unwanted features, cull them or ask them to be culled.
It'll take a while to navigate the hierarchy but they'll figure it out. The old guard will have no option but to move up or move out.
But voice is not a huge traffic funnel. Text is. And the verdict is more or less unanimous at this time. Gemini 3.0 has outdone ChatGPT. I unsubscribed from GPT plus today. I was a happy camper until the last month when I started noticing deplorable bugs.
1. The conversation contexts are getting intertwined.Two months ago, I could ask multiple random queries in a conversation and I would get correct responses but the last couple of weeks, it's been a harrowing experience having to start a new chat window for almost any change in thread topic. 2. I had asked ChatGPT to once treat me as a co-founder and hash out some ideas. Now for every query - I get a 'cofounder type' response. Nothing inherently wrong but annoying as hell. I can live with the other end of the spectrum in which Claude doesn't remember most of the context.
Now that Gemini pro is out, yes the UI lacks polish, you can lose conversations, but the benefits of low latency search and a one year near free subscription is a clincher. I am out of ChatGPT for now, 5.2 or otherwise. I wish them well.
Because they want to feel superior as the ‘this was my idea and you executed on my idea’ nonsense. Their answers to most ‘why are we doing this ?’ ‘trust me bro’. I am perhaps generalizing and there are outlier product managers who have earned the ‘trust me bro’ adage, but most haven’t.
This PM behaviour will never change. Engineers have said enough is enough and are now taking over product roles, in essence eliminating the communication gap.
Why does the LLM need to understand anything. What today's chatbots have achieved is a software engineering feat. They have taken a stateless token generation machine that has compressed the entire internet's vocabulary to predict the next token and have 'hacked' a whole state management machinery around it. End result is a product that just feels like another human conversing with you and remembering your last birthday.
Engineering will surely get better and while purists can argue that a new research perspective is needed, the current growth trajectory of chatbots, agents and code generation tools will carry the torch forward for years to come.
If you ask me, this new AI winter will thaw in the atmosphere even before it settles on the ground.
This is a very interesting point. So if BLS suddenly became more accurate, all the agencies have to re-tune their own biases and corrections => Could lead to short term discrepancies.
What one sees as inefficiency is actually efficient from a totally different lens.
Or incentivize companies to report accurate data pretty fast. Payroll management systems can be plugged in real time, but that costs money and yeah small businesses are not going to be happy. So incentivization works better than punishment I think.
I get it and yeah my tone is very exaggerated. I don't think anyone in BLS should be fired and whoever is suggesting that does not understand how public institutions work.
I am just curious why there is so much of a discrepancy. This has been pretty much the status quo in BLS for a long time. They issue numbers and then they revise them later. However, you'd expect the revision to be moderately within an error %age.
Also how will this retroactive change help everyone involved. Ok, the new job numbers reflect a gloomier past (or a more vibrant past) how is that even helping everyone who is so focused on 'what's going to happen tomorrow'.
I retract my stance about BLS being intentionally corrupt - that's uncalled for.
The data covers the period from March 2024 to March 2025 and trims the average monthly jobs gains seen during this period (roughly the last 10 months of Joe Biden's presidency and the first two months of Trump's) from a monthly average of 147,000 to about 71,000.
50% error. This is more or less consistent. How can a department have this error % and still have their job. I understand the data collection mechanism is not the most sophisticated, but even accounting for that, this consistent error % is not to be overlooked.
I wonder why there is such lack of accountability from firms whose data pretty much feeds the world's economy.
Some of the alternatives I am about to consider:
1. Diffusion with sparse attention layers. 2. Hierarchical diffusion - next token diffusion combined with higher order chunk diffusion.
Still figuring out the code and I would love any feedback on these approaches.
The negativity posted in this article is a hand wavy at best.
tl;dr nVidia is using constrained supply to maximise datacenter GPUs. Consumer GPUs are collateral damage and nVidia understands that. You can't blame a company for maximising profit.
Case in point https://www.digitimes.com/news/a20241122PD200/nvidia-tsmc-ca...
Substrate (CoWoS) is TSMC’s 2.5-D “sandwich” assembly method. So nVidia is blocking all of this capacity for datacenter GPUs.
The melting cables claim is a bit overblown as well.
From o3
• Yes, the 16-pin 12 VHPWR/12 V-2×6 power plug used on RTX 40- and 50-series boards really has a track-record of occasional “melting” events. • The root cause is almost always high contact resistance created by a half-seated or bent connector; once that pin pair sees 35-40 A it heats up and chars the plastic housing. gamersnexus.net
• The problem is rare (low-single-digit failure rates in large user surveys) but visually dramatic, which is why it dominates headlines. gamersnexus.net
• PCI-SIG and Nvidia have already revised the design (12 V-2×6, ATX 3.1), yet isolated incidents are still being reported on new RTX 5090 cards, proving the fix is not bullet-proof. tomshardware.com
• Calling this “planned obsolescence” is a stretch; it is more an example of an aggressive power spec colliding with real-world tolerances and user handling.
Even though the language is very simple, the writing is quite convoluted.
You train a VLA (vision language action) model for a specific pair of robotic arms, for a specific task. The end actuator actions are embedded in the model (actions). So let's say you train a pair of arms to pick an apple. You cannot zero shot it to pick up a glass. What you see in demos is the result of lots of training and fine tuning (few shot) on specific object types and with specific robotic arms or bodies.
The language intermediary embedding brings some generalising skills to the table but it isn't much. The vision -> language -> action translation is, how do I put this, brittle at best.
What these guys are showing is a zero shot approach to new tasks in new environments with 80% accuracy. This is a big deal. Pi0 from Physical Intelligence is the best model to compare I think.
Here's one :)
Too much water also erodes your body of salts. If you already are on a low salt diet this could be a problem. For us Indians eating mountain loads of salt, this is a non issue.
Essentially, engineering the complete human body and mind including the nervous system. Seems highly intractable for the next couple of decades at least.
May be that's the problem - that there is no one rallying individual for Waymo. They should just spin it off and make it an independent private company and retain % ownership.
I somehow feel Google will be way better if it's run like Berkshire, the CEO just focuses on capital allocation and let's the managers do their jobs in their respective companies - YT, Waymo, search, cloud, deepmind.
I'm not sure that culture can dissipate in Google at this juncture.