roee | 10 months ago | on: Hud – The Runtime Code Sensor for Taming Code-Generating AI
Node and Phython for now
roee's comments
roee | 11 months ago | on: Runtime code sensor MCP gives code-generating agentic AI production awareness [video]
"This is what it looks like when agentic AI gets access to real production data.
LLMs are now helping build real software-but without production context, they write code that often doesn’t work in the real world.
They can’t see broken flows, performance bottlenecks, or cascading failures from external dependencies-the real reasons systems go down.
Hud’s runtime code sensor changes that. It runs with your service and automatically captures function-level behavior-no configuration, instrumentation, added logs, dashboards, or maintenance needed.
With Hud’s MCP, that production context becomes available to AI environments like Cursor, Windsurf and Github CoPilot-The result? Code that’s grounded in how your system actually behaves in production."
roee | 5 years ago
I’ve been waiting for this launch!
roee | 13 years ago | on: Top Windows laptops on the market based on big-data frustration analytics
Roee here, creator of the report. That's very good feedback. We'll add it to the next report.
roee | 13 years ago | on: Top Windows laptops on the market based on big-data frustration analytics
No2 is a $400 machine. Whatever do you mean?
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
We actually pay for georeplication on Azure. Here's the official response from them:
"Why didn’t we just fail over? We do have geo-replication for Windows Azure Blobs and Tables, where the data from US South is geo-replicated to keep another replica set of the data in US North. We have chosen at this time not to failover, since we believe we can bring back the primary storage stamp in US South in place. One of the advantages of recovering in place is it avoids losing the Windows Azure Queue data in that stamp, since Windows Azure Queues is not being geo-replicated at this time (we are working towards turning that on)."
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
I'm trying to say we were not visually prepared for this, and that getting designers and coders to work on a weekend is not something fun. I see your sarcasm and get it, but really it's out of place.
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
Good point :)
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
That's right. It's double-bad when things like that happen during the weekend so time-to-reaction is slower. All will be better tomorrow.
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
That's too close to RackSpace. Choose another name :)
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
That's not scapegoating, it's pointing at facts. Sad as they are. When you have a complex web service, you rely on a provider. That provider can go down sometimes, and it takes you with it. Again I'll point to Netflix and AWS, they waited until AWS were back up, they didn't "restore a backup" somewhere else.
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
No one's "blaming" anyone. The expectancy is that cloud providers work their asses off to fix stuff that gets broken, which is the case.
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
It's the entire service, not a bunch of files. When Netflix went down due to AWS outage, could you image them just "restoring a backup" on rackspace and running just like that?
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
We're running on their table storage from web roles and worker roles (their platform-as-a-service)
roee | 13 years ago | on: Our service is down because Msft Azure is down. This is how we chose to react.
When was it? We actually have great experience and great uptime with Azure. It's a very unique case for us.
roee | 13 years ago | on: The State of Windows 8
We will improve the visibility of this, thanks.
roee | 13 years ago | on: The State of Windows 8
It's a very different web service now.
roee | 13 years ago | on: The State of Windows 8
Just to clarify, the vast majority of our audience currently arrives through sites like LifeHacker, MakeUseOf and HowToGeek. "Bloatware" is uncalled for in this case, it usually refers to shit that's trying to make money of you without providing value. Please read my full comment that includes our bias analysis: http://news.ycombinator.com/item?id=4793863
roee | 13 years ago | on: The State of Windows 8
Hi, Roee from Soluto here, please see my full comment: http://news.ycombinator.com/item?id=4793863
roee | 13 years ago | on: The State of Windows 8
Hi, please the detailed comment here: http://news.ycombinator.com/item?id=4793863
page 1