> It’s not only new projects putting strain on the grid though. The report found that an estimated 13 percent of US cloud consumption, totaling more than 3 gigawatts, comes from so-called "zombie" workloads—abandoned test environments and unused applications that continue to draw power without doing any useful work.
Containerized sandbox environments for AI can be incredibly wasteful. If those sandboxes are kept available so the user gets sub-second access that is a continual user of RAM, and thus overall computing resources. We built the first version of https://www.aha.io/builder/overview using a typical containerized environment - just like you see with products like Replit - but were appalled at the inefficiency and waste. We rebuilt it from the ground-up to use shared architecture instead with Javascript-level isolation, and almost zero waste. Using shared computing instead of containers means instant startup time, and (almost) zero resource consumption when not active. You still consume disk to store the artifacts, but there is no ongoing RAM or CPU.
I think a reckoning is coming for container-based AI systems too. We are seeing tokens trend towards reflecting the actual cost, and I think the same will be true of containerized runtime environments too.
It makes me wonder if remote-first companies will have an advantage in an AI-first world because they must be more intentional about communication. By their very nature remote teams use more written communication and more intentional, and documented, processes. Perhaps the RTO mandates will turn out to be the biggest organizational mistake?
> Why are you asking the token predictor about the tokens it predicted?
I am surprised with this response because it implies this is not an extremely valuable technique. I ask LLMs all the time why they did or output something and they will usually provide extremely useful information. They will help me find where in the prompting I had conflicting or underspecified requirements. The more complex the agent scenario, the more valuable the agent becomes in debugging itself.
Perhaps in this case the problem with hooks is part of the deterministic Claude Code source code, and not under the control of the LLM anyway. So it may not have been able to help.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than 700,000 users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
* Devops engineers with Ruby experience. We focus on the "dev" and all of our operations driven by code.
Aha! is profitable, you can work from anywhere in North or South America, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
I am surprised at the amount of hate for Stack Overflow here. As a developer I can't think of a single website that has helped me as much over the last ten years.
It has had a huge benefit for the development community, and I for one will mourn its loss.
I do wonder where answers will come from in the future. As others have noted in this thread, documentation is often missing, or incorrect. SO collected the experiences of actual users solving real problems. Will AI share experiences in a similar way? In principle it could, and in practice I think it will need to. The shared knowledge of SO made all developers more productive. In an AI coded future there will need to be a way for new knowledge to be shared.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than 700,000 users worldwide. We are looking for:
* Experienced Rails security engineer to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
Aha! is profitable, you can work from anywhere in North or South America, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
Typescript. I imagine most people writing Rails applications are also writing typescript for front-end code, so being able to use the same muscle memory for Ruby typing seems high desirable. That is the thing that stood out to me when I saw this site: it looks like they are taking the very positive lessons from Typescript and applying them to Ruby.
I agree with other posters here. I don't need everything typed - Ruby's duck typing is an awesome feature - but I do wish that some of the more important interfaces in our code were more strongly self-documenting and enforced.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than 700,000 users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
* Devops engineers with Ruby experience. We focus on the "dev" and all of our operations driven by code.
Aha! is profitable, you can work from anywhere in North or South America, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than 700,000 users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
* Devops engineers with Ruby experience. We focus on the "dev" and all of our operations driven by code.
Aha! is profitable, you can work from anywhere in North or South America, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than 700,000 users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
* Devops engineers with Ruby experience. We focus on the "dev" and all of our operations driven by code.
Aha! is profitable, you can work from anywhere in North or South America, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than a million users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
Aha! is profitable, you can work from anywhere in North America, South America or New Zealand, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
It is real. I am the CTO and co-founder of Aha!, and also personally interview every engineer we hire.
A human reviews every job application we get, but unfortunately we can't respond to them all - we get thousands - but most of the applications are not related to the position requirements at all. I can tell you that if your resume matches what we are looking for then we typically schedule an interview within a few days. I see that you posted this same comment previously. Commenting was already locked by HN by the time I saw it then.
Why do I keep posting on HN? It works. The profile of engineers we have hired for our team, and the sorts of engineers who read HN has a great overlap. There are other things we look at too. Your Github profile is really important: people who contribute to open source have demonstrated their ability to work on a distributed remote team, but even more importantly it gives you a way to show that you can tackle interesting problems in interesting ways.
The seamless integration between one type of object and another is really impressive. The way that the blocks in the roofline perfectly work regardless of the height of the roof is a great example.
How is this possible? Is it some kind of procedural geometry that fills in the available space?
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than a million users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
Aha! is profitable, you can work from anywhere in North America, South America or New Zealand, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
I think the original author is drawing the wrong conclusion here. Sully may have had the stick all the way back, but that doesn't mean it was wrong. The lowest energy way to land is to try to prevent the aircraft from landing. So when you are in the flare, the technique is to pull back on the stick to keep the aircraft in the air a few feet above the runway, until you have no more elevator authority, and the aircraft will settle onto the runway with the least amount of energy. Exactly what you want in a off-field landing too.
As my glider instructor put it: those last few seconds before touchdown are the prime rib of flying. Keep pulling back on the stick and make it last.
In fact if you look at the Wikipedia article that the OP linked to it suggests that Sully was unhappy that the aircraft was not responding to his full back stick:
> However, Sullenberger said that these computer-imposed limits also prevented him from achieving the optimal landing flare for the ditching, which would have softened the impact.
Aha! is the #1 tool for product managers to plan strategy and roadmaps. We serve more than a million users worldwide. We are looking for:
* Experienced full-stack Rails and security engineers to work on the Aha! product. Our application is built in Ruby on Rails, with React on the frontend for rich client-side experiences.
Aha! is profitable, you can work from anywhere in North America, South America or New Zealand, and we offer excellent benefits. We use our own product to manage our work (which is especially rewarding) and we deploy continuously.
Our entire team has always been 100% remote - in North American timezones so we can collaborate during the work day.
> It’s not only new projects putting strain on the grid though. The report found that an estimated 13 percent of US cloud consumption, totaling more than 3 gigawatts, comes from so-called "zombie" workloads—abandoned test environments and unused applications that continue to draw power without doing any useful work.
Containerized sandbox environments for AI can be incredibly wasteful. If those sandboxes are kept available so the user gets sub-second access that is a continual user of RAM, and thus overall computing resources. We built the first version of https://www.aha.io/builder/overview using a typical containerized environment - just like you see with products like Replit - but were appalled at the inefficiency and waste. We rebuilt it from the ground-up to use shared architecture instead with Javascript-level isolation, and almost zero waste. Using shared computing instead of containers means instant startup time, and (almost) zero resource consumption when not active. You still consume disk to store the artifacts, but there is no ongoing RAM or CPU.
I think a reckoning is coming for container-based AI systems too. We are seeing tokens trend towards reflecting the actual cost, and I think the same will be true of containerized runtime environments too.