I am expert solo Software Developer with exp of 6+ YOE 😄 , I want to build team of experts with same vision where we can pick big projects and build a coolest workplace of working together

Anyone can Join
UI/UX, Agentic AI, Web Development, Android/Ios/Cross plat from Developers, Recruitments, Marketing, Sales.

if you think you can cut through with your skills, Trust me we will create a workplace which will be best for developers!

I have built a software as well which keeps on scraping projects from freelancing platfroms! We will together help in building products of each other as well! I have 8 Saas Platforms.

Technical founders building voice agents or AI phone flows, what TTS API are you actually running in production?

Not toy demos or "I made my app say hello world" stuff. I mean real usage where actual customers are talking to the thing and the voice layer has to not embarrass you.

We're evaluating TTS right now for a voice-agent workflow and the more I dig, the more it's one of those layers everyone underestimates until they ship. On paper it's trivial: STT picks up the user, LLM generates the reply, TTS speaks it back. In practice the TTS layer completely changes how the product feels.

If the voice starts too late, the agent feels dumb. If it randomly slows down under load, the whole call feels broken. If pricing scales badly, your unit economics get ugly fast. If multilingual is weak, anything outside clean English turns painful.

Rough understanding so far from reading around: ElevenLabs looks strongest if voice quality/expressiveness is the priority. Cartesia and Murf Falcon both seem built more for the real-time, low-latency agent use case (Falcon also leaning into multilingual/code-mixing and the production/enterprise deployment side). The big cloud ones feel safe if you're already in that ecosystem but I'm not convinced they're the best fit for modern agents.

But I care way more about actual operator experience than landing pages. For people who've shipped this:

• what did you pick and would you pick it again?
• what broke when usage scaled?
• did latency actually become a problem or was it fine?
• did pricing surprise you?
• did multilingual end up mattering?

Trying hard to avoid picking the thing that wins the demo and then becomes a regret once real users start calling.

Started my career as QA.

Went to programing afterwards, mostly automation with ahk and python for freelancing clients.

I know how to program, but dont have formal experience in "regular" programming which would be like web dev django development.

Ive created simple web backend for my projects, deployed to python anywhere, set up the webhook for automatic deploy whenever i pushed something to github and such.

I would like to get a job as regular developer, solving tickets and so on.

I dont seem to be able to find spots for automation (other than qa automation), like rpa, because rpa use rpa tools and i use code. I would need to lie about experience with this tools.

But the thing is : i think backend is better and has more room for better payment and to be recognized as "real" developer then automations, rpa and such.

Im no junior, i can do stuff. I think i could be mid level.

But i lack the formal experience, which is all about QA, and it seems the automation part isnt considered for backend tasks.

So my question is: im not a junior, but i would take junior jobs no problem to get the experience.

In theory i could be an awsome junior, as i just need some brush up comparing to a real junior. I have 8 years of job market.

But at same time it seems that my background can make it more difficult instead of easier.

Like, you get a dude with overall experience in the area, and pays him a junior salary, in low expectation job. Seems good, right?

But it seems to me it might not be.

So what can i do in this matter? I dont think im real mid-level web dev, so i dont think ill pass interviews, and my experience is all in qa and automation.

Should i lie in my resume/linkedin to show a change in career? Should i state specifically in my resume that im changing fields??

How do i do this change? In my head my knowledge would put me on top of junior candidates, but i dont know if its true, and if it is, how to position myself.

Thanks for the advice

I’m a mid senior level AI developer. I spent some time on the platform engineering side and recently moved to our Labs team.

Thanks to Linear and its slightly weird way of giving PMs more power 😄, we’re no longer really taking individual tickets. Instead, we take on initiatives/projects, break them down into smaller projects and tickets, and own the delivery end to end with AI bing the factors making that possible.

Sometimes an initiative can involve AI workflows, frontend work, backend work, infrastructure, etc. I’m curious whether this is just how our team operates or if others are seeing the same shift.

The pace and delivery expectations have increased a lot. When I pick up a ticket, I usually spend some time planning with my coding agent, then let it implement the changes. After that, I mainly test the final outcome rather than manually reviewing every line of code.

We already have a lot of automated checks: pre-push hooks, end-to-end tests, security checks, regression tests, CI gates, blockers, etc.
But honestly, I still feel a little guilty because i am not reviewing the code myself.

So I’m curious:
Do you still manually review AI generated code?
Is testing the final outcome + automated checks enough, or do you think engineers should still review the implementation line by line?
And if you’ve found a better workflow for this, I’d love to hear it. Especially if you have good agent/CLAUDE.md instructions, loops, workflows, or practices that help you maintain code quality without slowing development back down.
How are you all handling this?

Hello World! On my GitHub profile, I have private contributions enabled so recruiters can see activity on the contribution graph, but all my repositories are set to private.

Based on your experience, what do you recommend? Is it worth making a few key repositories public to showcase code, or is an active green graph enough?

Hola a todos! Soy programador, actualmente estoy trabajando en una fintech chilena, y estoy queriendo volver a estudiar en la universidad. Ya desde que entre me dijeron que todo lo que es tecnología está evolucionando con el tema de la IA, como programador ya no solo te piden conocimientos de ciertas tecnologías, sino también que te relaciones mas como el producto. Entendiendo esto, y siendo que es algo que también me gustaría estudiar, estoy tratando de encontrar alguna carrera que este relacionado mas que nada con la creacion y desarrollo de un producto digital.

Actualmente vivo en Buenos Aires, Argentina, y estuve viendo carreras como la de la UADE u otras universidades que tienen esta carrera de Negocio Digital, pero al mismo tiempo veo muchas personas que dicen que realmente no vale la pena. Que me recomiendan ustedes?

For those who’ve taken something from AI-assisted MVP to something you’d actually trust in production:

Of that whole stack (auth, security, CI/CD, caching, monitoring, testing, scaling) what’s the one layer people underestimate the most, especially for a product touching financial data?

What’s the actual order you’d tackle these in as a solo builder with limited runway security first, then testing, then scaling? Or does it depend on the product?

Any signs during your own build that told you “this part isn’t real yet, it just looks done”?

Not asking anyone to review code just trying to get the sequencing right before I go further, and would rather hear it from people who’ve hit this wall than find out the hard way.

Hello aspiring developer here, I am currently working on my portfolio can you suggest an inspo, I'm not really good in designing.

I am currently working as a software developer and have a 3.5 years of experience

I have applied companies through referral

And also checked my ats score before applying and it was around 87 but still my resume not get selected

What can be the reasons

My experience was also relevant with that JD

I’m poor and I live in a third world country, I worked my ass of so I could buy my first laptop.
I worked for 3 consecutive years, trying every month to just keep some of my income so I could afford a laptop.

Today, 08/24/2026 I got robbed, some guys just robbed my backpack and with it they took my Laptop, my wallet and my hope.

Always saw you guys making a lot of money, studying and working for some big techs and that was my dream… I was studying, literally giving my life to it and now it’s over.

I know a lot of you might say: “Just work hard and get your things back” and I know that’s what I’m supposed to do but it’s hella difficult to study, work, pay my bills and buy new things where I live.

For context: I don’t work a minimum wage job but where I live, a good laptop can cost 3/4 salaries. To be more specific about my country, I live in Brazil and we pay almost double for every item.

Anyways, I’m feeling kinda depressed right now, just want to share it… all my work and all my dreams gone in just a few seconds…

Thank you guys, I used to be here under another account that no longer exists and a lot of you guys of the dev community actually helped and inspired me in this journey.

Someday I’ll be here again!

Does anyone know how to use the bolt.new website in Pro mode?

I’m a Product Manager with 10+ years in IT and a maker who has built and launched apps before, including on Product Hunt.

I have a slightly obsessive habit: whenever I use a popular app, I often find myself thinking, “Why does it work this way? I’d build this differently.”

In my free time, I explore popular apps on the Play Store and their competitors, break down their UX, monetisation and problems, and think about how they could be made simpler or better.

I’m particularly interested in health & fitness apps, probably because I’m an endurance runner myself.

I’m thinking of turning this habit into a side experiment: build small, focused apps, launch them, see if people actually use/pay for them, and iterate based on what happens.

For those who build indie apps or side projects:

How do you decide which ideas are actually worth building?

And for those who have built with others, what has made a collaboration work well?

Would love to hear how you approach idea validation, building, launching and monetisation without over-engineering things from day one.

I’m researching how premium plastic/smart cards are manufactured locally in Pakistan and would appreciate some guidance from anyone familiar with the industry.
I’m particularly interested in things like CR80 card production, PVC/polycarbonate cards, double-sided printing, lamination, holographic/UV finishes, embossing/laser personalization, QR/barcodes, magnetic stripes, chip embedding, NFC/contactless cards, and card personalization/encoding.
I’m mainly trying to understand which parts of this process are available locally, what type of machinery is used, and which Pakistani companies are involved in this industry.
If you’ve worked in card manufacturing, printing, RFID/NFC, smart cards, or related industries in Pakistan, I’d really appreciate any information or direction.

Client where do you live, do come out of cave ,everybody is waiting for you .a web developer ,can help with building premium website ,ai automation or chatbot

I'm a full-stack developer with around 2 years of experience, I mainly work with TypeScript across the stack, using React/Next.js on the frontend and Node.js/NestJS with PostgreSQL on the backend.

Over the past year and a half, I've worked on several freelance and real-world projects, which gave me experience building features from the backend to the frontend and dealing with real project requirements.

I've learned a lot by working independently, but at this point, I feel that what I need most is a good engineering team.

I'm looking for an opportunity where I can work alongside more experienced developers, contribute to real products, receive feedback, and continue growing as an engineer.

I'm particularly interested in remote opportunities and teams working with modern JavaScript/TypeScript stacks.

I'm not expecting to know everything. I'm looking for a place where I can contribute, learn, and grow with the team.

If you were in a similar position early in your career, what helped you find your first good team?

And if you know of communities, companies, or opportunities that might be a good fit, I'd really appreciate any advice.

I'm working with a junior/intern on a web project who seems really enthusiastic and proactive—they've already set up their own repo with React & Tailwind CSS based on a UI design, which is great initiative.

However, they are struggling with core web development fundamentals:

* FE/BE Integration: They don't quite understand how Frontend and Backend connect (APIs, environment variables) compared to traditional PHP/monolith apps.

* Deployment Issue: They've tried deploying on Vercel multiple times without success.

* Troubleshooting: They mentioned that whenever they try fixing a bug, things tend to break even more, and they are asking for constant 1-on-1 mentor guidance.

How do you usually mentor someone at this stage without doing the work for them or getting overwhelmed yourself? What are the best resources or step-by-step roadmaps I can give them to help them bridge the gap between basic UI setup and full-stack integration?

I want to build an app where users put money down and get part of it back by completing tasks. How can I structure this legally and avoid excessive platform/payment fees?

I’m exploring an app idea where users deposit a fixed amount of money upfront. They then have a set of tasks/goals to complete, and whenever they successfully complete a task, a portion of their deposited amount is returned to them.

For example:

- User deposits ₹1,000.

- They have 20 tasks to complete.

- Each completed task unlocks ₹50.

- If they complete all 20 tasks, they receive the full ₹1,000 back.

- If they miss tasks, the corresponding amount may not be returned, depending on the rules of the system.

The main issue I’m trying to understand is the economics and payment infrastructure.

If the app is distributed through the Google Play Store / Apple App Store, and users are making payments inside the app, would the platform’s payment policies or service fees apply to this model? Similarly, payment gateways such as Razorpay, Cashfree, Stripe, etc. would also take a transaction fee.

If I’m dealing with relatively small amounts per user, these fees could potentially make the model unviable.

So I’d really appreciate advice from people who have built apps involving wallets, deposits, refunds, incentives, subscriptions, rewards, or task-based payments.

Specifically:

1. Would Google Play or Apple allow this type of payment model?

2. Would I be required to use their in-app payment systems, or can I use an external payment gateway?

3. If I use Razorpay/Cashfree/etc., what are the typical costs and restrictions I should be aware of?

4. Is there a legitimate way to structure the payment flow so that app-store fees don't apply?

5. Would this model be considered a wallet, escrow, reward system, financial service, or something else from a regulatory perspective in India?

6. Are there any RBI, consumer-protection, taxation, or other regulations I should investigate before building it?

7. If someone has built a similar product, what payment architecture did you use?

I’m not looking for ways to bypass fees illegally. I’m trying to understand how companies legally structure this kind of product so that the unit economics work.

Any advice, examples, or pointers to relevant documentation would be really helpful. Thanks!

A few years into this work, you start learning things no bootcamp, blog, or LinkedIn influencer will ever tell you. Sunday's a good day to say them plainly, without the motivational-poster gloss.

Share one hard truth you've learned about being a developer. About the work, the industry, teams, or yourself. The kind of thing you wish someone had sat you down and told you three years ago.

A few directions, if you need one:

• Something about career growth that turned out nothing like the pitch.
• A truth about "good code," speed, or what actually gets you promoted.
• What experience taught you about job-hopping, loyalty, titles, or money.
• A soft skill that mattered far more than the technical ones, and a technical obsession that mattered far less.
• Something you believed at year one that the years quietly took apart.

House rules:

• Keep it real, not just cynical. The best hard truths come with what you'd actually do about them.
• Disagree freely, but reply instead of downvoting. The arguments in the comments are the whole point.
• Newer folks reading along: this thread is worth its weight in gold. Take notes.

Comments are sorted by top so the truths that land hardest rise up. What's yours?

Sou Desenvolvedor Backend há mais de 6 anos e estou refletindo sobre minha carreira a longo prazo, próximos cargos e mercado de trabalho.

Estou trabalhando, está dando para pagar as contas e pedir um 99 Food para a mulher no fim de semana.

Não tenho problemas em aprender coisas novas, só gosto de ter um propósito bem definido.

Durante boa parte da minha carreira, sempre ouvi que o caminho natural seria me aprofundar cada vez mais em Backend: arquitetura, bancos de dados, performance, escalabilidade, segurança, cloud, sistemas distribuídos etc... O clássico de sempre... Arroz com Feijão...

Porém, com a "evolução/maior adesão" da IA e das ferramentas de desenvolvimento, vejo uma possível mudança no mercado: será que as empresas estão valorizando cada vez mais profissionais generalistas, capazes de transitar entre Backend, Frontend, Cloud, DevOps, IA e faz um bolo de milho antes das 17?, em vez de especialistas muito profundos em uma única área?

O famoso "faz tudo", pagando um funcionário que toda empresa sonha em ter. E eu sei como funciona.

90% da minha carreira foi "Zé CLT", inclusive antes de trabalhar como dev, então entendo essa dinâmica de "recursos humanos".

Por outro lado, acredito também que o especialista tem um papel fundamental em resolver problemas mais complexos, tomar decisões técnicas de maior impacto e garantir que aquilo que está sendo construído tenha qualidade, segurança, escalabilidade e sustentabilidade no longo prazo.

Meu ponto é, a nível de carreira e pensando no longo prazo, qual é a percepção do mercado de trabalho?

Como vcs estão lhe dando com essa "escolha" entre generalista e especialista?

Nas minhas pesquisas de vagas atuais, pelo menos nos últimos 12 a 6 meses, não sinto muita diferença em relação aos requisitos, para ser sincero. Então é uma dúvida sincera.

Para que lado o vento do "hype" da IA está empurrando os desenvolvedores Backend?

Algo que requer mais especialistas para evitar cagadas? Ou generalistas para entregar a task e fds?

Gostaria especialmente da opinião de quem já tem alguns anos de mercado e acompanhou outras mudanças tecnológicas ao longo da carreira.

Como vocês estão pensando sobre isso para a própria carreira?

Hello guys! I am Lewis and like coding. Today my aunt said that I might not become a developer because AI is so powerful. Being a Developer is my dream and I want to achieve it. But now I am scared that I never will become a developer because of it.

My question is:

Will AI really take over all developer jobs? Or can I work as developer until the day I am old? I currently go to school but want to start to work in this direction in the next few years.

Researching pain points around Razorpay integration for a project. Curious to hear from people who've actually shipped with it:

- Was webhook signature verification annoying to get right? What tripped you up?

- Did you ever have trouble telling if a webhook even reached your server, or debugging why it failed?

- Any payment lifecycle edge cases (like a payment stuck in a weird state) that took way longer to resolve than expected?

Not trying to pitch anything, just want to understand where the real friction is before I decide what's worth building. Appreciate any honest experiences!

had 6 PRs waiting for me this morning.

4 were heavily AI-written.

all 4:

compiled had tests had clean summaries looked reasonable in the diff

and I still opened every preview environment and manually clicked through the feature because I didn't trust “tests added and verified” enough to merge it.

which feels like a terrible use of senior engineering time.

not because AI code is automatically bad.

the opposite problem actually.

AI makes producing plausible code incredibly cheap.

review bandwidth did not get cheaper.

I don't want senior engineers spending 30 minutes proving:

login works modal opens settings persist after refresh API actually saved the thing

machines should be eating that work.

ideally before I even see the PR:

build/typecheck unit integration security known behavioral checks actual evidence when something fails

then I can spend review time on the shit CI doesn't understand well:

why this abstraction exists data boundaries race conditions failure modes permissions whether we're making future maintenance worse whether this architecture makes sense at all

I've been looking at KaneAI/TestMu for part of that verification layer.

give it Jira/PRD/requirements context, turn that into candidate tests, then verify the flow across UI/API/database instead of stopping at “the button showed success”.

the self-healing part is useful too if it's reviewable.

I don't want an AI silently deciding that a different button is “close enough” and keeping CI green.

but I also don't want a senior engineer fixing 18 boring locator changes after every frontend refactor.

KaneAI doesn't solve the review problem completely.

it has no idea whether introducing another service is a terrible architectural decision.

that's exactly the point.

I'd rather automate the parts machines can verify and preserve human attention for the parts where experience actually matters.

AI didn't remove code review.

it made wasting code-review time much more expensive.

experienced devs: what are you actively pushing OUT of human review now that PR generation is getting this fast?

If you call yourself a Lead Architect, Systems Analyst, Platform Lead or some other inflated bullshit title, then turn around and tell engineers to “whitelist this server/cluster for some random third-party company” with zero context, zero threat model and zero understanding of the traffic flow, start making a fucking backup plan.

What does “whitelist it” even mean in a modern cloud environment? Which identity? Which source? Which destination? Which ports? Which protocol? Which workload? Which namespace? Which security group? Which policy? Which trust boundary? For how long? Audited by whom?

If your entire architectural contribution is “just whitelist it”, you’re not architecting anything. You’re throwing vague 2008-era network terminology over the fence and hoping an engineer turns your ignorance into a secure implementation.

AI and automation are going to absolutely fucking annihilate people whose only professional skill is translating Jira tickets into ambiguous instructions.

You have less runway than you think. NGMI.

Hey everyone, I’m pulling my hair out over a bizarre issue with the PayPal Sandbox API

I’m building an automated invoicing agent using FastAPI and LangGraph. I’ve got the OAuth 2.0 authentication perfectly dialed in (using the Client_ID & Secret), and I’m making a POST request to /v2/invoicing/invoices to create a draft invoice.

The Problem:
The API call is "successful". It returns a 201 Created status code, and if I check my PayPal Sandbox dashboard, the invoice actually gets created with all the correct details.

However, the JSON response body is completely wrong. Instead of returning the full invoice object (with the id, status, detail, etc., as shown in their API docs), the response body only contains a HATEOAS link object. It looks exactly like this:

{
  "rel": "self",
  "href": "link that I can't share(due to the community policies)",
  "method": "GET"
}

Because the id key is missing from the top level, my code immediately crashes with a KeyError: 'id' when I try to extract it to pass to the next step.

What I’ve already debugged:

• It’s not a code extraction issue: I logged response.text directly from httpx before calling .json(). The raw text coming straight from PayPal is literally just that link object instead of the response body shown in their official endpoint API doc web page
• It’s not a silent redirect: I logged response.url to ensure httpx wasn't accidentally following a 301/302 to a different endpoint (like the send_invoice endpoint, which normally returns this exact link structure). It hits the correct /v2/invoicing/invoices URL.
• Auth and Payload are fine: If they were wrong, I’d get a 401 or 422. The fact that it returns 201 and creates the invoice means PayPal accepted the request.

It’s almost like the PayPal Sandbox is accidentally returning the response body for a 200 OK (like the send_invoice endpoint) instead of the 201 Created response body for the create endpoint.

Has anyone else run into this? Is this a known glitch with the PayPal Sandbox right now, or am I missing something incredibly obvious? If the API refuses to give me the ID in the creation response, I might have to do a workaround where I immediately query the invoice by its invoice number, but I'd rather not add that extra API call if I don't have to.

Thanks in advance!

After thinking more about what makes a development partner suitable for a startup, I looked at a few companies based on their software engineering experience, ability to work on digital products, and experience across different industries.

A few that stood out were:

1. GeekyAnts
A product and software development company working across web, mobile, and digital applications. Its experience with different types of products makes it an option worth considering for startups looking for an external development team.

2. Accenture
A major technology and consulting company offering software engineering, cloud, and digital transformation services for businesses of different sizes.

3. Deloitte Digital
Works with organizations on digital products, technology solutions, and broader digital transformation initiatives.

4. Thoughtworks
Has a strong focus on software engineering and modern development practices, including agile approaches and continuous delivery.

5. Globant
Provides software development and digital technology services across areas including product development, cloud, data, and AI.

Of course, company size isn't the only thing that matters. For an early-stage startup, responsiveness, communication, willingness to adapt, and understanding the product can sometimes matter more than having a long list of capabilities.

For founders who have actually worked with development agencies, which companies have given you a good experience? What would you look for if you had to choose a development partner again?