An interesting observation: I’ve stopped using the LLM-powered autocomplete in my IDE.

At first, it was one of the key features for me. It felt extremely convenient: you start writing a function in your code, and the LLM completes it based on common sense or the context from the open tabs.

But the most interesting thing is that back when LLM autocomplete was useful and in demand, I had already written a script that could go through the source files, let me select what I needed, and prepare the context to feed into an LLM chat so it could tell me what to add or fix. I worked like that for about six months.

And even that is gone now.

These days it’s easier to open a CLI interface with a coding agent, without even launching the IDE. You describe what you need, use @ to point it to the files it should inspect or modify, and that’s it. Everything is changing at an absolutely insane speed.

Basically, the only things I still use an IDE for are nice Git diff visualization, step-by-step debugging, and the ability to click on functions and jump into their implementation. In other words, code navigation. And even that functionality is only needed in about 5-10% of my work.

It’s interesting to think what comes next.

What I mean is that I have an all-products subscription from JetBrains because I program in several languages at once: Java, Scala, Python, TypeScript, and Rust. But the question is: why keep paying for it?

Sure, once every 2-3 months, some unclear issue appears, and debugging helps find it. On the other hand, I’ve already tried another approach: I give an LLM agent the path to the log of what is happening in the program. If it doesn’t have enough information to solve the problem, I ask it to add more logs, then I describe the problem again and ask it to understand from the logs what needs to be fixed.

And of course, it’s very convenient to ask an LLM to write tests. That really is useful. If the tests fail, it looks at what it changed in the code and what it broke. When the LLM starts going in circles, I directly tell it: cover this with tests and read the logs to understand how everything works. Very convenient.

One of my latest techniques is using a plan.md file. When I ask it to solve a complex task, I first ask it to create a work plan and write it into plan.md. Then I simply ask it to complete one task from that file at a time. And step by step, through small tasks, the LLM eventually gets to the result.

Overall, I think the industry is changing a lot.

Share your experience: how has your approach to programming changed? I’d be interested to hear how things have changed for others.

But please don’t reply if you have never programmed before and have just discovered vibe coding. I’ve been programming myself since 1990, which means I wrote my first program 36 years ago...

An interesting observation: I’ve stopped using the LLM-powered autocomplete in my IDE.

At first, it was one of the key features for me. It felt extremely convenient: you start writing a function in your code, and the LLM completes it based on common sense or the context from the open tabs.

But the most interesting thing is that back when LLM autocomplete was useful and in demand, I had already written a script that could go through the source files, let me select what I needed, and prepare the context to feed into an LLM chat so it could tell me what to add or fix. I worked like that for about six months.

And even that is gone now.

These days it’s easier to open a CLI interface with a coding agent, without even launching the IDE. You describe what you need, use @ to point it to the files it should inspect or modify, and that’s it. Everything is changing at an absolutely insane speed.

Basically, the only things I still use an IDE for are nice Git diff visualization, step-by-step debugging, and the ability to click on functions and jump into their implementation. In other words, code navigation. And even that functionality is only needed in about 5-10% of my work.

It’s interesting to think what comes next.

What I mean is that I have an all-products subscription from JetBrains because I program in several languages at once: Java, Scala, Python, TypeScript, and Rust. But the question is: why keep paying for it?

Sure, once every 2-3 months, some unclear issue appears, and debugging helps find it. On the other hand, I’ve already tried another approach: I give an LLM agent the path to the log of what is happening in the program. If it doesn’t have enough information to solve the problem, I ask it to add more logs, then I describe the problem again and ask it to understand from the logs what needs to be fixed.

And of course, it’s very convenient to ask an LLM to write tests. That really is useful. If the tests fail, it looks at what it changed in the code and what it broke. When the LLM starts going in circles, I directly tell it: cover this with tests and read the logs to understand how everything works. Very convenient.

One of my latest techniques is using a plan.md file. When I ask it to solve a complex task, I first ask it to create a work plan and write it into plan.md. Then I simply ask it to complete one task from that file at a time. And step by step, through small tasks, the LLM eventually gets to the result.

Overall, I think the industry is changing a lot.

Share your experience: how has your approach to programming changed? I’d be interested to hear how things have changed for others.

But please don’t reply if you have never programmed before and have just discovered vibe coding. I’ve been programming myself since 1990, which means I wrote my first program 36 years ago...

An interesting observation: I’ve stopped using the LLM-powered autocomplete in my IDE.

At first, it was one of the key features for me. It felt extremely convenient: you start writing a function in your code, and the LLM completes it based on common sense or the context from the open tabs.

But the most interesting thing is that back when LLM autocomplete was useful and in demand, I had already written a script that could go through the source files, let me select what I needed, and prepare the context to feed into an LLM chat so it could tell me what to add or fix. I worked like that for about six months.

And even that is gone now.

These days it’s easier to open a CLI interface with a coding agent, without even launching the IDE. You describe what you need, use @ to point it to the files it should inspect or modify, and that’s it. Everything is changing at an absolutely insane speed.

Basically, the only things I still use an IDE for are nice Git diff visualization, step-by-step debugging, and the ability to click on functions and jump into their implementation. In other words, code navigation. And even that functionality is only needed in about 5-10% of my work.

It’s interesting to think what comes next.

What I mean is that I have an all-products subscription from JetBrains because I program in several languages at once: Java, Scala, Python, TypeScript, and Rust. But the question is: why keep paying for it?

Sure, once every 2-3 months, some unclear issue appears, and debugging helps find it. On the other hand, I’ve already tried another approach: I give an LLM agent the path to the log of what is happening in the program. If it doesn’t have enough information to solve the problem, I ask it to add more logs, then I describe the problem again and ask it to understand from the logs what needs to be fixed.

And of course, it’s very convenient to ask an LLM to write tests. That really is useful. If the tests fail, it looks at what it changed in the code and what it broke. When the LLM starts going in circles, I directly tell it: cover this with tests and read the logs to understand how everything works. Very convenient.

One of my latest techniques is using a plan.md file. When I ask it to solve a complex task, I first ask it to create a work plan and write it into plan.md. Then I simply ask it to complete one task from that file at a time. And step by step, through small tasks, the LLM eventually gets to the result.

Overall, I think the industry is changing a lot.

Share your experience: how has your approach to programming changed? I’d be interested to hear how things have changed for others.

But please don’t reply if you have never programmed before and have just discovered vibe coding. I’ve been programming myself since 1990, which means I wrote my first program 36 years ago...

An interesting observation: I’ve stopped using the LLM-powered autocomplete in my IDE.

At first, it was one of the key features for me. It felt extremely convenient: you start writing a function in your code, and the LLM completes it based on common sense or the context from the open tabs.

But the most interesting thing is that back when LLM autocomplete was useful and in demand, I had already written a script that could go through the source files, let me select what I needed, and prepare the context to feed into an LLM chat so it could tell me what to add or fix. I worked like that for about six months.

And even that is gone now.

These days it’s easier to open a CLI interface with a coding agent, without even launching the IDE. You describe what you need, use @ to point it to the files it should inspect or modify, and that’s it. Everything is changing at an absolutely insane speed.

Basically, the only things I still use an IDE for are nice Git diff visualization, step-by-step debugging, and the ability to click on functions and jump into their implementation. In other words, code navigation. And even that functionality is only needed in about 5-10% of my work.

It’s interesting to think what comes next.

What I mean is that I have an all-products subscription from JetBrains because I program in several languages at once: Java, Scala, Python, TypeScript, and Rust. But the question is: why keep paying for it?

Sure, once every 2-3 months, some unclear issue appears, and debugging helps find it. On the other hand, I’ve already tried another approach: I give an LLM agent the path to the log of what is happening in the program. If it doesn’t have enough information to solve the problem, I ask it to add more logs, then I describe the problem again and ask it to understand from the logs what needs to be fixed.

And of course, it’s very convenient to ask an LLM to write tests. That really is useful. If the tests fail, it looks at what it changed in the code and what it broke. When the LLM starts going in circles, I directly tell it: cover this with tests and read the logs to understand how everything works. Very convenient.

One of my latest techniques is using a plan.md file. When I ask it to solve a complex task, I first ask it to create a work plan and write it into plan.md. Then I simply ask it to complete one task from that file at a time. And step by step, through small tasks, the LLM eventually gets to the result.

Overall, I think the industry is changing a lot.

Share your experience: how has your approach to programming changed? I’d be interested to hear how things have changed for others.

But please don’t reply if you have never programmed before and have just discovered vibe coding. I’ve been programming myself since 1990, which means I wrote my first program 36 years ago...

An interesting observation: I’ve stopped using the LLM-powered autocomplete in my IDE.

At first, it was one of the key features for me. It felt extremely convenient: you start writing a function in your code, and the LLM completes it based on common sense or the context from the open tabs.

But the most interesting thing is that back when LLM autocomplete was useful and in demand, I had already written a script that could go through the source files, let me select what I needed, and prepare the context to feed into an LLM chat so it could tell me what to add or fix. I worked like that for about six months.

And even that is gone now.

These days it’s easier to open a CLI interface with a coding agent, without even launching the IDE. You describe what you need, use @ to point it to the files it should inspect or modify, and that’s it. Everything is changing at an absolutely insane speed.

Basically, the only things I still use an IDE for are nice Git diff visualization, step-by-step debugging, and the ability to click on functions and jump into their implementation. In other words, code navigation. And even that functionality is only needed in about 5-10% of my work.

It’s interesting to think what comes next.

What I mean is that I have an all-products subscription from JetBrains because I program in several languages at once: Java, Scala, Python, TypeScript, and Rust. But the question is: why keep paying for it?

Sure, once every 2-3 months, some unclear issue appears, and debugging helps find it. On the other hand, I’ve already tried another approach: I give an LLM agent the path to the log of what is happening in the program. If it doesn’t have enough information to solve the problem, I ask it to add more logs, then I describe the problem again and ask it to understand from the logs what needs to be fixed.

And of course, it’s very convenient to ask an LLM to write tests. That really is useful. If the tests fail, it looks at what it changed in the code and what it broke. When the LLM starts going in circles, I directly tell it: cover this with tests and read the logs to understand how everything works. Very convenient.

One of my latest techniques is using a plan.md file. When I ask it to solve a complex task, I first ask it to create a work plan and write it into plan.md. Then I simply ask it to complete one task from that file at a time. And step by step, through small tasks, the LLM eventually gets to the result.

Overall, I think the industry is changing a lot.

Share your experience: how has your approach to programming changed? I’d be interested to hear how things have changed for others.

But please don’t reply if you have never programmed before and have just discovered vibe coding. I’ve been programming myself since 1990, which means I wrote my first program 36 years ago...

I’m choosing between Qwen3.6 27B and Qwen3.6 35B A3B for an AI agent that helps users solve everyday household tasks.

Right now I’m using Qwen3.6 27B via OpenRouter, but sometimes it takes around 10 seconds just to start responding to a simple "Hello!", even with streaming enabled.

My servers are hosted in the US, so I was thinking about switching to DeepInfra, but the traceroute to DeepInfra looks pretty long from my server.

Does anyone know a fast API provider for servers in the US where inference starts quickly! Ideally within 1–2 seconds for the first streamed token?

Also, which model would you choose for this type of household AI agent: Qwen3.6 27B or Qwen3.6 35B A3B?

I’m choosing between Qwen3.6 27B and Qwen3.6 35B A3B for an AI agent that helps users solve everyday household tasks.

Right now I’m using Qwen3.6 27B via OpenRouter, but sometimes it takes around 10 seconds just to start responding to a simple "Hello!", even with streaming enabled.

My servers are hosted in the US, so I was thinking about switching to DeepInfra, but the traceroute to DeepInfra looks pretty long from my server.

Does anyone know a fast API provider for servers in the US where inference starts quickly! Ideally within 1–2 seconds for the first streamed token?

Also, which model would you choose for this type of household AI agent: Qwen3.6 27B or Qwen3.6 35B A3B?

I’m choosing between Qwen3.6 27B and Qwen3.6 35B A3B for an AI agent that helps users solve everyday household tasks.

Right now I’m using Qwen3.6 27B via OpenRouter, but sometimes it takes around 10 seconds just to start responding to a simple "Hello!", even with streaming enabled.

My servers are hosted in the US, so I was thinking about switching to DeepInfra, but the traceroute to DeepInfra looks pretty long from my server.

Does anyone know a fast API provider for servers in the US where inference starts quickly! Ideally within 1–2 seconds for the first streamed token?

Also, which model would you choose for this type of household AI agent: Qwen3.6 27B or Qwen3.6 35B A3B?

looking for a few QA-minded people who like poking around unfinished software and finding what breaks. it’s an early web app plus a windows desktop app. I’m not trying to promote it or get customers here, I just need honest beta feedback from people who are used to testing rough products.

Main things I’d like checked are signup/login, onboarding, the web app flow, windows install and first launch, chat experience, file/document uploads, confusing screens or wording, slow parts, broken flows, weird edge cases, and anything that feels unreliable or unclear.

The app is still in beta, so I’m not looking for polished reviews or praise. I need practical bug reports and blunt UX feedback. If this kind of beta-testing request is allowed here, comment or DM me and I’ll send access/details privatly.

looking for a few QA-minded people who like poking around unfinished software and finding what breaks. it’s an early web app plus a windows desktop app. I’m not trying to promote it or get customers here, I just need honest beta feedback from people who are used to testing rough products.

Main things I’d like checked are signup/login, onboarding, the web app flow, windows install and first launch, chat experience, file/document uploads, confusing screens or wording, slow parts, broken flows, weird edge cases, and anything that feels unreliable or unclear.

The app is still in beta, so I’m not looking for polished reviews or praise. I need practical bug reports and blunt UX feedback. If this kind of beta-testing request is allowed here, comment or DM me and I’ll send access/details privatly.

looking for a few QA-minded people who like poking around unfinished software and finding what breaks. it’s an early web app plus a windows desktop app. I’m not trying to promote it or get customers here, I just need honest beta feedback from people who are used to testing rough products.

Main things I’d like checked are signup/login, onboarding, the web app flow, windows install and first launch, chat experience, file/document uploads, confusing screens or wording, slow parts, broken flows, weird edge cases, and anything that feels unreliable or unclear.

The app is still in beta, so I’m not looking for polished reviews or praise. I need practical bug reports and blunt UX feedback. If this kind of beta-testing request is allowed here, comment or DM me and I’ll send access/details privatly.

looking for a few QA-minded people who like poking around unfinished software and finding what breaks. it’s an early web app plus a windows desktop app. I’m not trying to promote it or get customers here, I just need honest beta feedback from people who are used to testing rough products.

Main things I’d like checked are signup/login, onboarding, the web app flow, windows install and first launch, chat experience, file/document uploads, confusing screens or wording, slow parts, broken flows, weird edge cases, and anything that feels unreliable or unclear.

The app is still in beta, so I’m not looking for polished reviews or praise. I need practical bug reports and blunt UX feedback. If this kind of beta-testing request is allowed here, comment or DM me and I’ll send access/details privatly.

I built about 99% of an AI household assistant by myself, and the MVP now works end to end. I’m now looking for people who might want to come in early before I drown in the backlog.

I’m building a product that takes a real chunk of the mental load off whoever is running a household. It can pull expenses from receipts and bank statements, track prices for products people regularly buy, draft household legal documents that users review before anything goes out, help book appointments with local businesses, manage family budgets and calendars, and keep daily routines from quietly falling apart. I’m starting with the US market first.

I’ve already registered the Delaware company. I’m setting up banking and payments now, and Apple and Google developer accounts are in progress. On the development side, I’ve closed roughly 140 tickets and still have around 180 open. The problem is that the backlog keeps growing faster than I can clear it, and that is starting to slow down real progress.

I’m currently working with one QA person and one marketer. We move fast, but I’m overloaded. I need more technical people around the project so we can keep shipping instead of getting buried under unfinished work.

I’m looking for React/TypeScript developers, React Native developers, Rust backend engineers, Electron developers, Docker/infra people, QA automation engineers, and anyone who has actually shipped LLM agent workflows in production rather than just built demos.

I’m using React, React Native, TypeScript and JavaScript on the frontend, Electron for Windows/macOS/Linux desktop builds, Rust on the backend, Docker and Docker Swarm for infrastructure, plus an LLM provider-routing layer with per-user quotas and isolated container sessions per user.

I want to be upfront about the deal. I’m not offering a salary today, and I’m not going to pretend otherwise. I am offering a chance to come in early and help shape a real product before it is locked in.

I’m open to making it formal later as equity, a paid role, a contractor arrangement, or a founding-team setup once funding or revenue is in. I want clear written terms if we work well together. I’d rather under-promise now than run the usual “founding engineer for exposure” routine.

I’m polishing the MVP now and preparing to start investor outreach. I’m interested in talking to people who like early-stage products, can move fast, and want to build something practical for real households.

If this sounds interesting, drop a comment with your stack, what part you’d want to work on, and a GitHub or portfolio link if you have one. DMs are open too.

I built about 99% of an AI household assistant by myself, and the MVP now works end to end. I’m now looking for people who might want to come in early before I drown in the backlog.

I’m building a product that takes a real chunk of the mental load off whoever is running a household. It can pull expenses from receipts and bank statements, track prices for products people regularly buy, draft household legal documents that users review before anything goes out, help book appointments with local businesses, manage family budgets and calendars, and keep daily routines from quietly falling apart. I’m starting with the US market first.

I’ve already registered the Delaware company. I’m setting up banking and payments now, and Apple and Google developer accounts are in progress. On the development side, I’ve closed roughly 140 tickets and still have around 180 open. The problem is that the backlog keeps growing faster than I can clear it, and that is starting to slow down real progress.

I’m currently working with one QA person and one marketer. We move fast, but I’m overloaded. I need more technical people around the project so we can keep shipping instead of getting buried under unfinished work.

I’m looking for React/TypeScript developers, React Native developers, Rust backend engineers, Electron developers, Docker/infra people, QA automation engineers, and anyone who has actually shipped LLM agent workflows in production rather than just built demos.

I’m using React, React Native, TypeScript and JavaScript on the frontend, Electron for Windows/macOS/Linux desktop builds, Rust on the backend, Docker and Docker Swarm for infrastructure, plus an LLM provider-routing layer with per-user quotas and isolated container sessions per user.

I want to be upfront about the deal. I’m not offering a salary today, and I’m not going to pretend otherwise. I am offering a chance to come in early and help shape a real product before it is locked in.

I’m open to making it formal later as equity, a paid role, a contractor arrangement, or a founding-team setup once funding or revenue is in. I want clear written terms if we work well together. I’d rather under-promise now than run the usual “founding engineer for exposure” routine.

I’m polishing the MVP now and preparing to start investor outreach. I’m interested in talking to people who like early-stage products, can move fast, and want to build something practical for real households.

If this sounds interesting, drop a comment with your stack, what part you’d want to work on, and a GitHub or portfolio link if you have one. DMs are open too.

I built about 99% of an AI household assistant by myself, and the MVP now works end to end. I’m now looking for people who might want to come in early before I drown in the backlog.

I’m building a product that takes a real chunk of the mental load off whoever is running a household. It can pull expenses from receipts and bank statements, track prices for products people regularly buy, draft household legal documents that users review before anything goes out, help book appointments with local businesses, manage family budgets and calendars, and keep daily routines from quietly falling apart. I’m starting with the US market first.

I’ve already registered the Delaware company. I’m setting up banking and payments now, and Apple and Google developer accounts are in progress. On the development side, I’ve closed roughly 140 tickets and still have around 180 open. The problem is that the backlog keeps growing faster than I can clear it, and that is starting to slow down real progress.

I’m currently working with one QA person and one marketer. We move fast, but I’m overloaded. I need more technical people around the project so we can keep shipping instead of getting buried under unfinished work.

I’m looking for React/TypeScript developers, React Native developers, Rust backend engineers, Electron developers, Docker/infra people, QA automation engineers, and anyone who has actually shipped LLM agent workflows in production rather than just built demos.

I’m using React, React Native, TypeScript and JavaScript on the frontend, Electron for Windows/macOS/Linux desktop builds, Rust on the backend, Docker and Docker Swarm for infrastructure, plus an LLM provider-routing layer with per-user quotas and isolated container sessions per user.

I want to be upfront about the deal. I’m not offering a salary today, and I’m not going to pretend otherwise. I am offering a chance to come in early and help shape a real product before it is locked in.

I’m open to making it formal later as equity, a paid role, a contractor arrangement, or a founding-team setup once funding or revenue is in. I want clear written terms if we work well together. I’d rather under-promise now than run the usual “founding engineer for exposure” routine.

I’m polishing the MVP now and preparing to start investor outreach. I’m interested in talking to people who like early-stage products, can move fast, and want to build something practical for real households.

If this sounds interesting, drop a comment with your stack, what part you’d want to work on, and a GitHub or portfolio link if you have one. DMs are open too.

PS

At that moment salay: no compensation in next months $2.000

I built about 99% of an AI household assistant by myself, and the MVP now works end to end. I’m now looking for people who might want to come in early before I drown in the backlog.

I’m building a product that takes a real chunk of the mental load off whoever is running a household. It can pull expenses from receipts and bank statements, track prices for products people regularly buy, draft household legal documents that users review before anything goes out, help book appointments with local businesses, manage family budgets and calendars, and keep daily routines from quietly falling apart. I’m starting with the US market first.

I’ve already registered the Delaware company. I’m setting up banking and payments now, and Apple and Google developer accounts are in progress. On the development side, I’ve closed roughly 140 tickets and still have around 180 open. The problem is that the backlog keeps growing faster than I can clear it, and that is starting to slow down real progress.

I’m currently working with one QA person and one marketer. We move fast, but I’m overloaded. I need more technical people around the project so we can keep shipping instead of getting buried under unfinished work.

I’m looking for React/TypeScript developers, React Native developers, Rust backend engineers, Electron developers, Docker/infra people, QA automation engineers, and anyone who has actually shipped LLM agent workflows in production rather than just built demos.

I’m using React, React Native, TypeScript and JavaScript on the frontend, Electron for Windows/macOS/Linux desktop builds, Rust on the backend, Docker and Docker Swarm for infrastructure, plus an LLM provider-routing layer with per-user quotas and isolated container sessions per user.

I want to be upfront about the deal. I’m not offering a salary today, and I’m not going to pretend otherwise. I am offering a chance to come in early and help shape a real product before it is locked in.

I’m open to making it formal later as equity, a paid role, a contractor arrangement, or a founding-team setup once funding or revenue is in. I want clear written terms if we work well together. I’d rather under-promise now than run the usual “founding engineer for exposure” routine.

I’m polishing the MVP now and preparing to start investor outreach. I’m interested in talking to people who like early-stage products, can move fast, and want to build something practical for real households.

If this sounds interesting, drop a comment with your stack, what part you’d want to work on, and a GitHub or portfolio link if you have one. DMs are open too.

I built about 99% of an AI household assistant by myself, and the MVP now works end to end. I’m now looking for people who might want to come in early before I drown in the backlog.

I’m building a product that takes a real chunk of the mental load off whoever is running a household. It can pull expenses from receipts and bank statements, track prices for products people regularly buy, draft household legal documents that users review before anything goes out, help book appointments with local businesses, manage family budgets and calendars, and keep daily routines from quietly falling apart. I’m starting with the US market first.

I’ve already registered the Delaware company. I’m setting up banking and payments now, and Apple and Google developer accounts are in progress. On the development side, I’ve closed roughly 140 tickets and still have around 180 open. The problem is that the backlog keeps growing faster than I can clear it, and that is starting to slow down real progress.

I’m currently working with one QA person and one marketer. We move fast, but I’m overloaded. I need more technical people around the project so we can keep shipping instead of getting buried under unfinished work.

I’m looking for React/TypeScript developers, React Native developers, Rust backend engineers, Electron developers, Docker/infra people, QA automation engineers, and anyone who has actually shipped LLM agent workflows in production rather than just built demos.

I’m using React, React Native, TypeScript and JavaScript on the frontend, Electron for Windows/macOS/Linux desktop builds, Rust on the backend, Docker and Docker Swarm for infrastructure, plus an LLM provider-routing layer with per-user quotas and isolated container sessions per user.

I want to be upfront about the deal. I’m not offering a salary today, and I’m not going to pretend otherwise. I am offering a chance to come in early and help shape a real product before it is locked in.

I’m open to making it formal later as equity, a paid role, a contractor arrangement, or a founding-team setup once funding or revenue is in. I want clear written terms if we work well together. I’d rather under-promise now than run the usual “founding engineer for exposure” routine.

I’m polishing the MVP now and preparing to start investor outreach. I’m interested in talking to people who like early-stage products, can move fast, and want to build something practical for real households.

If this sounds interesting, drop a comment with your stack, what part you’d want to work on, and a GitHub or portfolio link if you have one. DMs are open too.

I built about 99% of an AI household assistant by myself, and the MVP now works end to end. I’m now looking for people who might want to come in early before I drown in the backlog.

I’m building a product that takes a real chunk of the mental load off whoever is running a household. It can pull expenses from receipts and bank statements, track prices for products people regularly buy, draft household legal documents that users review before anything goes out, help book appointments with local businesses, manage family budgets and calendars, and keep daily routines from quietly falling apart. I’m starting with the US market first.

I’ve already registered the Delaware company. I’m setting up banking and payments now, and Apple and Google developer accounts are in progress. On the development side, I’ve closed roughly 140 tickets and still have around 180 open. The problem is that the backlog keeps growing faster than I can clear it, and that is starting to slow down real progress.

I’m currently working with one QA person and one marketer. We move fast, but I’m overloaded. I need more technical people around the project so we can keep shipping instead of getting buried under unfinished work.

I’m looking for React/TypeScript developers, React Native developers, Rust backend engineers, Electron developers, Docker/infra people, QA automation engineers, and anyone who has actually shipped LLM agent workflows in production rather than just built demos.

I’m using React, React Native, TypeScript and JavaScript on the frontend, Electron for Windows/macOS/Linux desktop builds, Rust on the backend, Docker and Docker Swarm for infrastructure, plus an LLM provider-routing layer with per-user quotas and isolated container sessions per user.

I want to be upfront about the deal. I’m not offering a salary today, and I’m not going to pretend otherwise. I am offering a chance to come in early and help shape a real product before it is locked in.

I’m open to making it formal later as equity, a paid role, a contractor arrangement, or a founding-team setup once funding or revenue is in. I want clear written terms if we work well together. I’d rather under-promise now than run the usual “founding engineer for exposure” routine.

I’m polishing the MVP now and preparing to start investor outreach. I’m interested in talking to people who like early-stage products, can move fast, and want to build something practical for real households.

If this sounds interesting, drop a comment with your stack, what part you’d want to work on, and a GitHub or portfolio link if you have one. DMs are open too.

Here’s the situation.

I saw an opportunity to create a product-as-a-service that helps homemakers plan their budget, track expenses, monitor price drops on products, ask for advice on things like how to properly file for divorce and apply for child support, or ask the assistant to book a haircut for them, as well as manage daily and weekly routine tasks.

As a result, I now have a small team: one developer - myself, one QA tester, and one marketer. And we are honestly completely overwhelmed.

Our competitors are OpenClaw, Hermes, Claude Cowork, and Manus - the one Meta reportedly failed to acquire for $2 billion. They are competitors in a broad sense, but I am taking a more niche approach: a mass-market product, but not as broad as competitors who are trying to build everything for everyone at once.

Right now, at the prototype level, we already cover iOS, Android, Web, and also a desktop version for Windows, macOS, and Linux.

As a result, I have more than 140 bug reports across all these platforms. I have already managed to fix more than 100 of them.

I have also initiated the registration of a U.S. Inc. company in Delaware so that we can publish our apps in the App Store and Google Play, and later accept customer payments through subscriptions.

My main problem is that there are simply too many channels and platforms for development and promotion.

I am the only developer, and we have one QA tester and one marketer, but we cannot handle all of this at once. We need to grow the team by at least 3x.

We need to hire at least two more developers, two more QA testers, and also a production specialist who will create content for promotion.

Can anyone help in any way?

We are so exhausted that we are literally working on our last nerve.

We can see that this product has real potential, but it became very hard once we got deeper into it and realized how difficult it is to build this with such a small team.

Please help. Any kind of help is welcome.

Here’s the situation.

I saw an opportunity to create a product-as-a-service that helps homemakers plan their budget, track expenses, monitor price drops on products, ask for advice on things like how to properly file for divorce and apply for child support, or ask the assistant to book a haircut for them, as well as manage daily and weekly routine tasks.

As a result, I now have a small team: one developer - myself, one QA tester, and one marketer. And we are honestly completely overwhelmed.

Our competitors are OpenClaw, Hermes, Claude Cowork, and Manus - the one Meta reportedly failed to acquire for $2 billion. They are competitors in a broad sense, but I am taking a more niche approach: a mass-market product, but not as broad as competitors who are trying to build everything for everyone at once.

Right now, at the prototype level, we already cover iOS, Android, Web, and also a desktop version for Windows, macOS, and Linux.

As a result, I have more than 140 bug reports across all these platforms. I have already managed to fix more than 100 of them.

I have also initiated the registration of a U.S. Inc. company in Delaware so that we can publish our apps in the App Store and Google Play, and later accept customer payments through subscriptions.

My main problem is that there are simply too many channels and platforms for development and promotion.

I am the only developer, and we have one QA tester and one marketer, but we cannot handle all of this at once. We need to grow the team by at least 3x.

We need to hire at least two more developers, two more QA testers, and also a production specialist who will create content for promotion.

Can anyone help in any way?

We are so exhausted that we are literally working on our last nerve.

We can see that this product has real potential, but it became very hard once we got deeper into it and realized how difficult it is to build this with such a small team.

Please help. Any kind of help is welcome.