Show HN: OpenYabby, voice-controlled multi-agent orchestrator for Claude Code
3 by idovmamane | 0 comments on Hacker News.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New Show Hacker News story: Show HN: Command Center, the AI coding env for people who care about quality
Show HN: Command Center, the AI coding env for people who care about quality
7 by Darmani | 0 comments on Hacker News.
Hi HN! We’re Jimmy and Ray. Jimmy is a Thiel Fellow with a Ph. D. from MIT who has worked on programming tools for 15 years; Ray became VP of Sales at a $2B company when he was 19 and has built side-businesses vibe-coding. Last year, we set to answer the question “If AI can write code 100x faster, then why aren’t you shipping 100x faster?” What we learned shocked us — even fairly nontechnical people and solo founders told us they were spending more than half of their development time reading the AI-written code. And much of the rest of the time was spent either de-slop-ping it, or wishing they had done so. As luck turns out, our last two products were a tool that quickly onboards people to large codebases ( https://ift.tt/eGbzfoW ) and trainings that taught deep concepts of code quality to CEOs, YC founders, and engineers at top companies ( mirdin.com ), so we were extremely well-positioned to solve these problems. Command Center is an agentic coding environment focused on quality. With a few keypresses, you can start building 3 features at once and soon have 3 diffs ready, each consisting of 2000 changed lines across 50 files…. This is normally the point where you think “Crap, what now?” With Command Center, at this point you simply click “Refactor,” and watch the vibed slop turn into readable robustness. Then you click “Generate Walkthrough,” and then suddenly, to read a 2000 line diff, instead of scrolling up and down trying to make sense of it, you just press the right arrow key 200 times. See something you don’t like? Click on line 37, type “Do this and all other network fetches in the background Cmd+Enter,” and you have a few more agents getting your code into final shape. Click or type “Commit,” “Push,” “Create PR” — you just shipped a high quality, non-slop feature We’re striving to be the best at every step of the pipeline, but can just try Command Center in pieces wherever you feel your current workflow is weakest. We have users who do all their coding in Zed or the Codex app, and then jump over to Command Center for a walkthrough when it finishes running. There’s even a skill that will pop open a Command Center walkthrough from the environment of your choice. Or you can just keep Command Center running while you do your work elsewhere, and if your AI deletes anything, you have Command Center’s snapshots to the rescue. We launched quietly last year and have been refining since. The quality and usability have kept going up, and Command Center is now ready for a lot more attention. Since our quiet launch, we’ve seen at least a dozen other agentic coding environments appear….approximately all of which have the same feature set focused on the part which is already easy (generating the first version of the code) and with at best a shoddy answer to the hard part (everything that comes after). Command Center’s focus is making the hard parts easy. Here’s what our users have to say: “[The refactorings] give your LLM taste. I’ve never seen an LLM write code this good before.” — Doug Slater, Staff Engineer, Climavision “With Command Center walkthroughs, I can get through a 400-line diff in less than half the time.” — Prateek Kumar, Platfor Engineer, Sumo Logic This product is not for everyone. If you’re someone who preaches “the prompt is the source, the code is the compiler output,” then you probably won’t enjoy Command Center. But if you want to uphold traditional engineering discipline while also shipping 20 PRs a day, then this is the environment for you.
7 by Darmani | 0 comments on Hacker News.
Hi HN! We’re Jimmy and Ray. Jimmy is a Thiel Fellow with a Ph. D. from MIT who has worked on programming tools for 15 years; Ray became VP of Sales at a $2B company when he was 19 and has built side-businesses vibe-coding. Last year, we set to answer the question “If AI can write code 100x faster, then why aren’t you shipping 100x faster?” What we learned shocked us — even fairly nontechnical people and solo founders told us they were spending more than half of their development time reading the AI-written code. And much of the rest of the time was spent either de-slop-ping it, or wishing they had done so. As luck turns out, our last two products were a tool that quickly onboards people to large codebases ( https://ift.tt/eGbzfoW ) and trainings that taught deep concepts of code quality to CEOs, YC founders, and engineers at top companies ( mirdin.com ), so we were extremely well-positioned to solve these problems. Command Center is an agentic coding environment focused on quality. With a few keypresses, you can start building 3 features at once and soon have 3 diffs ready, each consisting of 2000 changed lines across 50 files…. This is normally the point where you think “Crap, what now?” With Command Center, at this point you simply click “Refactor,” and watch the vibed slop turn into readable robustness. Then you click “Generate Walkthrough,” and then suddenly, to read a 2000 line diff, instead of scrolling up and down trying to make sense of it, you just press the right arrow key 200 times. See something you don’t like? Click on line 37, type “Do this and all other network fetches in the background Cmd+Enter,” and you have a few more agents getting your code into final shape. Click or type “Commit,” “Push,” “Create PR” — you just shipped a high quality, non-slop feature We’re striving to be the best at every step of the pipeline, but can just try Command Center in pieces wherever you feel your current workflow is weakest. We have users who do all their coding in Zed or the Codex app, and then jump over to Command Center for a walkthrough when it finishes running. There’s even a skill that will pop open a Command Center walkthrough from the environment of your choice. Or you can just keep Command Center running while you do your work elsewhere, and if your AI deletes anything, you have Command Center’s snapshots to the rescue. We launched quietly last year and have been refining since. The quality and usability have kept going up, and Command Center is now ready for a lot more attention. Since our quiet launch, we’ve seen at least a dozen other agentic coding environments appear….approximately all of which have the same feature set focused on the part which is already easy (generating the first version of the code) and with at best a shoddy answer to the hard part (everything that comes after). Command Center’s focus is making the hard parts easy. Here’s what our users have to say: “[The refactorings] give your LLM taste. I’ve never seen an LLM write code this good before.” — Doug Slater, Staff Engineer, Climavision “With Command Center walkthroughs, I can get through a 400-line diff in less than half the time.” — Prateek Kumar, Platfor Engineer, Sumo Logic This product is not for everyone. If you’re someone who preaches “the prompt is the source, the code is the compiler output,” then you probably won’t enjoy Command Center. But if you want to uphold traditional engineering discipline while also shipping 20 PRs a day, then this is the environment for you.
New ask Hacker News story: Ask HN: How do you cope when your startup contracts?
Ask HN: How do you cope when your startup contracts?
5 by jasonephraim | 0 comments on Hacker News.
The same general situation has happened to me twice now and I am wondering if it’s something I can break free from or if it’s just the nature of the Startup beast - or what. There seems to be some kind of bubble that starts drying up investment in a startup where I am a technical lead. Both times, things seem to be going well and then 2 years in there are rounds of layoffs due to factors outside my/product’s control where the result is the same. I end up as the last tech generalist. It falls to me to write as much of the code as I can, manage (if any are left) engineers in my department, running support basically on my own, owning a large part of the product roadmap, working with the customers on support and implementations, working with integration partners, plus a slowly expanding list of responsibilities as new stuff falls on reduced teams. I pick up new domains pretty quick (finance, insurance, compliance), switch contexts well. I’ve always been the person who just figures it out - someone who takes ownership of something and just does it. But, instead of being rewarded, I just get to keep my job while absorbing the work of others less fortunate. During these contractions, the work never shrinks. Same clients, same integrations, same support volume (for now). Something else I’ve noticed is the scrutiny goes up - not down. I think a big factor is you have founders and upper managers stepping in to be more engaged or attempting to cover gaps. This causes all sorts of issues. After this last round of cuts, the company offered me a revised title and job description that focused on managing the department that now was essentially just me down from 6 a year ago. It was full of responsibilities like “leading team to meet targets”. I did kind of want to accept it since it is the sort of role I was hired for and would help in a job search later. Regardless, I couldn’t because I am basically the team. It felt like a trap (or at least, wishful thinking that has been proven as much time and time again due to factors beyond my control.) I could just leave, but the job market and economy look scary as hell. It took me 8 months to find a role last time. This is primarily due to my experience and background. I’ve been involved in engineering, product, support, sales, customer success, integrations and user comms. I look like someone who could/did do everything but that comes off as someone who owned nothing. The reality is I owned way way too much as things evolved. Three things I am trying to think through and could use some help with: 1. Is it just the companies and bad luck? Am I picking startups in industries or with offerings that are just vulnerable to VC trends and hype? They both seemed like great opportunities, and I completely understand there is always risk - but the current/former result as it pertains to my role and situation once cuts were made is surprisingly identical. 2. Should I stand my ground? I have a habit of trying to work things out and get scrappy. During the last contraction, I spoke out to the president of the company that I wanted to sit down and look at our team’s responsibilities and projects that were being used/sold and see what was essential, could be covered, etc. That never happened - should I have been more firm and demanded it versus just absorbing it? 3. Ignoring the company, should I lean into the role and try to develop it? Should I accept I am an amazing generalist “jack of all trades, but master of none” and make it a more deliberate role/career? I know these sort of people are needed, but no company can really put out a role description for them. I’m seeing AI helps cover a growing amount of the gaps that I can’t dedicate the time to developing. I also have enough experience and knowledge to know AI is a tool and needs to be closely guided and applied in focused/appropriate areas. (Case in point - I’ve spent the last two hours fighting it from going off the rails in our Go golden test framework because it wants to ignore our test patterns). I’m curious if others out there have found similar issues with Startups. Also, if there are other “Red Mage” technical folks that have a hard time in the job market because they’ve been asked to cover such wide areas?
5 by jasonephraim | 0 comments on Hacker News.
The same general situation has happened to me twice now and I am wondering if it’s something I can break free from or if it’s just the nature of the Startup beast - or what. There seems to be some kind of bubble that starts drying up investment in a startup where I am a technical lead. Both times, things seem to be going well and then 2 years in there are rounds of layoffs due to factors outside my/product’s control where the result is the same. I end up as the last tech generalist. It falls to me to write as much of the code as I can, manage (if any are left) engineers in my department, running support basically on my own, owning a large part of the product roadmap, working with the customers on support and implementations, working with integration partners, plus a slowly expanding list of responsibilities as new stuff falls on reduced teams. I pick up new domains pretty quick (finance, insurance, compliance), switch contexts well. I’ve always been the person who just figures it out - someone who takes ownership of something and just does it. But, instead of being rewarded, I just get to keep my job while absorbing the work of others less fortunate. During these contractions, the work never shrinks. Same clients, same integrations, same support volume (for now). Something else I’ve noticed is the scrutiny goes up - not down. I think a big factor is you have founders and upper managers stepping in to be more engaged or attempting to cover gaps. This causes all sorts of issues. After this last round of cuts, the company offered me a revised title and job description that focused on managing the department that now was essentially just me down from 6 a year ago. It was full of responsibilities like “leading team to meet targets”. I did kind of want to accept it since it is the sort of role I was hired for and would help in a job search later. Regardless, I couldn’t because I am basically the team. It felt like a trap (or at least, wishful thinking that has been proven as much time and time again due to factors beyond my control.) I could just leave, but the job market and economy look scary as hell. It took me 8 months to find a role last time. This is primarily due to my experience and background. I’ve been involved in engineering, product, support, sales, customer success, integrations and user comms. I look like someone who could/did do everything but that comes off as someone who owned nothing. The reality is I owned way way too much as things evolved. Three things I am trying to think through and could use some help with: 1. Is it just the companies and bad luck? Am I picking startups in industries or with offerings that are just vulnerable to VC trends and hype? They both seemed like great opportunities, and I completely understand there is always risk - but the current/former result as it pertains to my role and situation once cuts were made is surprisingly identical. 2. Should I stand my ground? I have a habit of trying to work things out and get scrappy. During the last contraction, I spoke out to the president of the company that I wanted to sit down and look at our team’s responsibilities and projects that were being used/sold and see what was essential, could be covered, etc. That never happened - should I have been more firm and demanded it versus just absorbing it? 3. Ignoring the company, should I lean into the role and try to develop it? Should I accept I am an amazing generalist “jack of all trades, but master of none” and make it a more deliberate role/career? I know these sort of people are needed, but no company can really put out a role description for them. I’m seeing AI helps cover a growing amount of the gaps that I can’t dedicate the time to developing. I also have enough experience and knowledge to know AI is a tool and needs to be closely guided and applied in focused/appropriate areas. (Case in point - I’ve spent the last two hours fighting it from going off the rails in our Go golden test framework because it wants to ignore our test patterns). I’m curious if others out there have found similar issues with Startups. Also, if there are other “Red Mage” technical folks that have a hard time in the job market because they’ve been asked to cover such wide areas?
New Show Hacker News story: Show HN: Courtside – TUI for NBA Games
Show HN: Courtside – TUI for NBA Games
8 by nolanfogarty | 3 comments on Hacker News.
Hi HN, I made this after seeing a few similar projects on the front page. NBA API endpoints are public and there’s a pretty robust python package ( https://ift.tt/1AvOxXq ) that I referenced for the endpoint structure to build an sdk in go. used BubbleTea and LipGloss for styling. It was a bit tricky to test the live endpoints but I watched Friday’s Final game with this and it worked pretty well playball - https://ift.tt/jhi35Uv faceoff - https://ift.tt/5h3vEXK
8 by nolanfogarty | 3 comments on Hacker News.
Hi HN, I made this after seeing a few similar projects on the front page. NBA API endpoints are public and there’s a pretty robust python package ( https://ift.tt/1AvOxXq ) that I referenced for the endpoint structure to build an sdk in go. used BubbleTea and LipGloss for styling. It was a bit tricky to test the live endpoints but I watched Friday’s Final game with this and it worked pretty well playball - https://ift.tt/jhi35Uv faceoff - https://ift.tt/5h3vEXK
New Show Hacker News story: Show HN: I Derived a Pancake
Show HN: I Derived a Pancake
40 by bkazez | 7 comments on Hacker News.
After 25 years of making other people's pancake recipes - always yearning for more tang, more fluff, and more predictability - I decided to derive the pancake recipe from the chemistry. You mark checkboxes for what you have on hand (ricotta, sour cream, kefir, buttermilk, yogurt, cottage cheese, lemon, cream of tartar, etc.) and it computes the best recipe based on targets for acid, fat, salt, sugar, and CO2. My particular favorite are the yeast-raised lemon ricotta kefir pancakes - the best I've ever had. The math is done in a small pure-ESM library: ingredient composition to component masses and acid moles, a stoichiometry layer, and a bisection solver for the target deficits. I'm not a chemist, so if something is off, tell me and I will fix it!
40 by bkazez | 7 comments on Hacker News.
After 25 years of making other people's pancake recipes - always yearning for more tang, more fluff, and more predictability - I decided to derive the pancake recipe from the chemistry. You mark checkboxes for what you have on hand (ricotta, sour cream, kefir, buttermilk, yogurt, cottage cheese, lemon, cream of tartar, etc.) and it computes the best recipe based on targets for acid, fat, salt, sugar, and CO2. My particular favorite are the yeast-raised lemon ricotta kefir pancakes - the best I've ever had. The math is done in a small pure-ESM library: ingredient composition to component masses and acid moles, a stoichiometry layer, and a bisection solver for the target deficits. I'm not a chemist, so if something is off, tell me and I will fix it!
New ask Hacker News story: Ask HN: Are we as society going to let LLM companies take all the values?
Ask HN: Are we as society going to let LLM companies take all the values?
3 by randomdev123 | 1 comments on Hacker News.
I am not that young, but I'm not that old. I used to be a child, and thought that the adults already figured things out and I can be at peace. One of my realization of me getting older is the realization that there are no adults in the room anymore, or that I am now, an adult, who, also the same like other adults, we actually don't know shit about anything, none of us do. I think LLM is a useful technology. But since the dawn of LLMs, I've been trying to imagine what the world will look like if we take LLM to its logical conclusion. It seems to me, despite of all its benefits, LLM is a sword too sharp for all of us to handle. Its not gonna be sunshines and rainbows. A couple things I'm thinking about below, and these are all just societal impact, not even environmental ones: - Young people lost their career ladders. Capitalism doesn't work anymore. We have permanent underclass. And maybe worldwide scale societal unrest, in which violence will be the norm. - People stop creating music, stop writing blogs, stop doing experiments or any other cool stuffs and share it on the internet because LLM companies can just pirate the shit out of it without paying anything back. - Mediocrity in everything. We have this Suno shit claiming that people don't like the process of creating music because its so tedious so lets just prompt it away. Berklee has a class to make AI music. Yup. People claim that its okay to consume mediocre stuffs, because we don't need the highest grade of codebase, of design, of music for our day to day life. - People stop socializing and connecting to another human beings. For example, art is a way for people to connect to other's art. Software engineering is a lot of communication, discussing tradeoffs with other engineers. But now you can just prompt your way away, even things as simple as writing emails. - All the values (measured by money) created in this world is sucked by the LLM owners/producers. Oh you have a beautiful music you just created? Too bad, its mine now. Oh, you just created an art? Its my art now, and I will charge society money to recreate this art that I just acquired. Oh, you have a land somewhere? I can just buy it, money is cheap for me, after all I suck all the values that society created. There are no other values worthy of monetary compensation other than LLM training/research. These "researchers" don't need to practice music, don't need to practice art, don't need to practice law, don't need to practice coding, they can just be an LLM researchers/producers/owners and they get all the values that the other professions created. - All the above caused economic stagnation. People don't feel the need to pay other human beings, because everything is just a prompt away. - All the above caused stagnation of progress, or even winding down of progress. What else? If truly this is the logical conclusion of LLM, then it seems to me that the mission of this generation is to destroy AI as Ronnie Chieng said is not really off the mark. Maybe I am an LLM doomer, but help me out here HN, because I'm just a dumb adult.
3 by randomdev123 | 1 comments on Hacker News.
I am not that young, but I'm not that old. I used to be a child, and thought that the adults already figured things out and I can be at peace. One of my realization of me getting older is the realization that there are no adults in the room anymore, or that I am now, an adult, who, also the same like other adults, we actually don't know shit about anything, none of us do. I think LLM is a useful technology. But since the dawn of LLMs, I've been trying to imagine what the world will look like if we take LLM to its logical conclusion. It seems to me, despite of all its benefits, LLM is a sword too sharp for all of us to handle. Its not gonna be sunshines and rainbows. A couple things I'm thinking about below, and these are all just societal impact, not even environmental ones: - Young people lost their career ladders. Capitalism doesn't work anymore. We have permanent underclass. And maybe worldwide scale societal unrest, in which violence will be the norm. - People stop creating music, stop writing blogs, stop doing experiments or any other cool stuffs and share it on the internet because LLM companies can just pirate the shit out of it without paying anything back. - Mediocrity in everything. We have this Suno shit claiming that people don't like the process of creating music because its so tedious so lets just prompt it away. Berklee has a class to make AI music. Yup. People claim that its okay to consume mediocre stuffs, because we don't need the highest grade of codebase, of design, of music for our day to day life. - People stop socializing and connecting to another human beings. For example, art is a way for people to connect to other's art. Software engineering is a lot of communication, discussing tradeoffs with other engineers. But now you can just prompt your way away, even things as simple as writing emails. - All the values (measured by money) created in this world is sucked by the LLM owners/producers. Oh you have a beautiful music you just created? Too bad, its mine now. Oh, you just created an art? Its my art now, and I will charge society money to recreate this art that I just acquired. Oh, you have a land somewhere? I can just buy it, money is cheap for me, after all I suck all the values that society created. There are no other values worthy of monetary compensation other than LLM training/research. These "researchers" don't need to practice music, don't need to practice art, don't need to practice law, don't need to practice coding, they can just be an LLM researchers/producers/owners and they get all the values that the other professions created. - All the above caused economic stagnation. People don't feel the need to pay other human beings, because everything is just a prompt away. - All the above caused stagnation of progress, or even winding down of progress. What else? If truly this is the logical conclusion of LLM, then it seems to me that the mission of this generation is to destroy AI as Ronnie Chieng said is not really off the mark. Maybe I am an LLM doomer, but help me out here HN, because I'm just a dumb adult.
New Show Hacker News story: Show HN: Nightwatch, The open-source, read-only AI SRE
Show HN: Nightwatch, The open-source, read-only AI SRE
2 by egorferber | 0 comments on Hacker News.
nightwatch is a local-first, read-only layer on top of your monitoring. it groups alert storm into incidents, flags noisy checks and has an agent that can investigate for you live systems. You can e.g. jump from the incident into the agent directly. the reason for this weekend project is that we had a kubernetes upgrade that went wrong, and at some point a rollback wasn't possible anymore, so it had to be fixed live during the night while several problems came together. We run a lot of different systems, on-prem and several Kubernetes clusters, and in a situation like that you spend most of the time just figuring out what is actually broken and where. So i thought that it would be pretty cool to have eyes in the dark in each system that can talk to your "brain". so the idea is to put a baby owl into each environment. Each owl runs where the systems live, keeps that environment's credentials local, and only dials outbound to a central brain, so there is no inbound hole into prod. It exposes a set of read-only skills, and the agent uses them to gather evidence and form a root-cause hypothesis, so the on-call engineer starts with a head start instead of from zero. read-only for now, i don't trust it near prod yet and honestly neither should you. llocal-first for easy self-hosting and to keep credentials on your side. the clustering and recommendations run fully offline with no llm at all. the agent needs a tool-calling llm, you can point it at a remote one, or self-host one (ollama etc.) if you want to stay fully offline. for non selfhosters: before every remote llm call, nightwatch strips real secrets (unrestorable) and swaps identifiers like ips, hostnames and paths for reversible placeholders, so the model only sees masked data while real values are restored only in the proposed commands and tool calls Would love if you try it in your Systems
2 by egorferber | 0 comments on Hacker News.
nightwatch is a local-first, read-only layer on top of your monitoring. it groups alert storm into incidents, flags noisy checks and has an agent that can investigate for you live systems. You can e.g. jump from the incident into the agent directly. the reason for this weekend project is that we had a kubernetes upgrade that went wrong, and at some point a rollback wasn't possible anymore, so it had to be fixed live during the night while several problems came together. We run a lot of different systems, on-prem and several Kubernetes clusters, and in a situation like that you spend most of the time just figuring out what is actually broken and where. So i thought that it would be pretty cool to have eyes in the dark in each system that can talk to your "brain". so the idea is to put a baby owl into each environment. Each owl runs where the systems live, keeps that environment's credentials local, and only dials outbound to a central brain, so there is no inbound hole into prod. It exposes a set of read-only skills, and the agent uses them to gather evidence and form a root-cause hypothesis, so the on-call engineer starts with a head start instead of from zero. read-only for now, i don't trust it near prod yet and honestly neither should you. llocal-first for easy self-hosting and to keep credentials on your side. the clustering and recommendations run fully offline with no llm at all. the agent needs a tool-calling llm, you can point it at a remote one, or self-host one (ollama etc.) if you want to stay fully offline. for non selfhosters: before every remote llm call, nightwatch strips real secrets (unrestorable) and swaps identifiers like ips, hostnames and paths for reversible placeholders, so the model only sees masked data while real values are restored only in the proposed commands and tool calls Would love if you try it in your Systems