Why? Because building a startup teaches you things most jobs can’t and how to work with uncertainty, figure things out from scratch, sell, make decisions and take ownership when there’s no one else to blame :)
looking for people who’ve been through it and want a second arena to build in.
If that’s you, DM me.
[MOD Approved post]
We’re YE Stack, a venture studio based in Kochi that has been operating with founders and building startups for 9 years now. One of the things we’ve realized in the process is that great individuals develop best when they’re around other great individuals. And this is why we created Ascent, an in-person fellowship of curious and high agency builders.
If you’re an engineer, designer, founder, operator, researcher, student or someone else, we’d like to invite you to join us. It’s not a program, an accelerator or a networking opportunity.
People are the curriculum.
If this sounds like your community, you can find out more and apply at:
As AI tools make it easier than ever to build software, a new problem is emerging: understanding what was actually built.
ProductLens helps founders, operators, and non-technical stakeholders make sense of software projects by analyzing a codebase and turning it into business-friendly insights.
Some things we're exploring:
The goal is simple: make software easier to understand for the people making business decisions around it.
We're still early and looking for feedback from founders, agencies, investors, and anyone working with software they didn't personally write.
Would love to hear:
Happy to answer questions and share more details.
Website : https://productlens.report/
We're a small product and development team that builds apps and web products for early-stage founders. Alongside client work, we're also building our own product.
Looking for a Product Designer who can take rough ideas and founder conversations and turn them into clear user flows, wireframes, and interfaces before development starts. Strong Figma skills are important, but we're more interested in how you think through problems than how polished your screens look.
You might be a good fit if you've worked at a startup, agency, or studio, enjoy working directly with founders, and can move from ambiguity to a testable product concept quickly.
If interested, pls dm
We're a small product and development team that builds apps and web products for early-stage founders. Alongside client work, we're also building our own product.
Looking for a Product Designer who can take rough ideas and founder conversations and turn them into clear user flows, wireframes, and interfaces before development starts. Strong Figma skills are important, but we're more interested in how you think through problems than how polished your screens look.
Company name : TGH Technologies PVT Ltd
Company website : www.tghtech.com
Role : product designer
You might be a good fit if you've worked at a startup, agency, or studio, enjoy working directly with founders, and can move from ambiguity to a testable product concept quickly.
Remote is fine.
If interested, pls fill in the form.
We're a small product and development team that builds apps and web products for early-stage founders. Alongside client work, we're also building our own product.
Looking for a Product Designer who can take rough ideas and founder conversations and turn them into clear user flows, wireframes, and interfaces before development starts. Strong Figma skills are important, but we're more interested in how you think through problems than how polished your screens look.
You might be a good fit if you've worked at a startup, agency, or studio, enjoy working directly with founders, and can move from ambiguity to a testable product concept quickly.
Remote is fine.
If interested, pls dm
If you built your product with AI and don't have a technical background, you've probably tested it, it worked, and you moved on.
But "it works when I use it" and "I know what's inside it" are two different things.
I ran my scanner on repos from people in exactly this situation. The same things kept coming up:
Actions or pages that weren't supposed to exist anymore, still sitting there active. Nobody knew.
Connections to other tools that looked set up but never actually worked. Silently doing nothing.
Passwords and keys written directly into the code instead of stored safely. Only visible if you open the files.
None of it made the app crash. None of it showed up during normal testing. It was just there, invisible.
Most people who build without a technical background have no way to see any of this. Not because they're not smart enough, but because nobody built a readable version of it for them.
That's what this does. It reads your codebase and gives you a plain English map of what's actually in there. No technical knowledge needed to understand the output.
Built specifically for non-technical founders.
If anyone wants to run it on their repo, drop a comment or DM me.
Used ai to structure my post
If you built your product with AI and don't have a technical background, you've probably tested it, it worked, and you moved on.
But "it works when I use it" and "I know what's inside it" are two different things.
I ran my scanner on repos from people in exactly this situation. The same things kept coming up:
Actions or pages that weren't supposed to exist anymore, still sitting there active. Nobody knew.
Connections to other tools that looked set up but never actually worked. Silently doing nothing.
Passwords and keys written directly into the code instead of stored safely. Only visible if you open the files.
None of it made the app crash. None of it showed up during normal testing. It was just there, invisible.
Most people who build without a technical background have no way to see any of this. Not because they're not smart enough, but because nobody built a readable version of it for them.
That's what this does. It reads your codebase and gives you a plain English map of what's actually in there. No technical knowledge needed to understand the output.
Built specifically for non-technical founders.
If anyone wants to run it on their repo, drop a comment or DM me.
Used ai to structure my post.
If you built your product with AI and don't have a technical background, you've probably tested it, it worked, and you moved on.
But "it works when I use it" and "I know what's inside it" are two different things.
I ran my scanner on repos from people in exactly this situation. The same things kept coming up:
Actions or pages that weren't supposed to exist anymore, still sitting there active. Nobody knew.
Connections to other tools that looked set up but never actually worked. Silently doing nothing.
Passwords and keys written directly into the code instead of stored safely. Only visible if you open the files.
None of it made the app crash. None of it showed up during normal testing. It was just there, invisible.
Most people who build without a technical background have no way to see any of this. Not because they're not smart enough, but because nobody built a readable version of it for them.
That's what this does. It reads your codebase and gives you a plain English map of what's actually in there. No technical knowledge needed to understand the output.
Built specifically for non-technical founders.
Need a young, creative video editor to help with a product launch video.
If interested, drop your portfolio/showreel and rates in the comments or DM me. Thanks!
For a while I kept hitting the same wall. Every time I took over or evaluated a codebase, I had no fast way to tell whether what the README and the team said it did actually matched what the code was really doing. Reviews ate days, and I still never fully trusted that nothing important was slipping through.
So I worked with my tech team and built ProductLens (https://productlens.report/) to deal with it. Short version: it reads just the source code (never your running systems or data) and produces a single report that maps the code to what the product actually does, flags the risky areas, and does a "claimed vs real" pass, what the docs and team say vs what the code actually shows, with every finding pointed to the exact file and line so it's not the AI just making confident noise.
Mostly I want to hear from you all though: when you inherit or evaluate a codebase, how are you getting confidence quickly today? Is there a process or tool you swear by? And honestly, are there better alternatives to what I've built that I should just be using instead? Not trying to sell anything, I genuinely want to know if this is useful or if I've reinvented something that already exists.
note - used AI to help structure this post so it reads clearly, but the problem and the question are genuinely mine
For a while I kept hitting the same wall. Every time I took over or evaluated a codebase, I had no fast way to tell whether what the README and the team said it did actually matched what the code was really doing. Reviews ate days, and I still never fully trusted that nothing important was slipping through.
So I worked with my tech team and built ProductLens (https://productlens.report/) to deal with it. Short version: it reads just the source code (never your running systems or data) and produces a single report that maps the code to what the product actually does, flags the risky areas, and does a "claimed vs real" pass, what the docs and team say vs what the code actually shows, with every finding pointed to the exact file and line so it's not the AI just making confident noise.
Mostly I want to hear from you all though: when you inherit or evaluate a codebase, how are you getting confidence quickly today? Is there a process or tool you swear by? And honestly, are there better alternatives to what I've built that I should just be using instead? Not trying to sell anything, I genuinely want to know if this is useful or if I've reinvented something that already exists.
Used AI to help draft this post.
A few months ago, I realized I had no real visibility into my cloud infrastructure costs.
I could see the total bill at the end of the month, but I couldn't quickly answer simple questions like:
That lack of visibility led to a few financial decisions I probably wouldn't have made if I had better cost insights.
So I ended up building a small internal dashboard for myself that tracks infrastructure spend and breaks it down in a way that's easy to understand. (Attached a screenshot.)
Now I'm curious:
Is this a problem others face as well, or am I just unusually bad at keeping track of cloud costs?
How are you currently monitoring and managing infrastructure spend?
Used AI to help draft this post.
A few months ago, I realized I had no real visibility into my cloud infrastructure costs.
I could see the total bill at the end of the month, but I couldn't quickly answer simple questions like:
That lack of visibility led to a few financial decisions I probably wouldn't have made if I had better cost insights.
So I ended up building a small internal dashboard for myself that tracks infrastructure spend and breaks it down in a way that's easy to understand. (Attached a screenshot.)
Now I'm curious:
Is this a problem others face as well, or am I just unusually bad at keeping track of cloud costs?
How are you currently monitoring and managing infrastructure spend?
Used AI to help draft this post.
A few months ago, I realized I had no real visibility into my cloud infrastructure costs.
I could see the total bill at the end of the month, but I couldn't quickly answer simple questions like:
That lack of visibility led to a few financial decisions I probably wouldn't have made if I had better cost insights.
So I ended up building a small internal dashboard for myself that tracks infrastructure spend and breaks it down in a way that's easy to understand. (Attached a screenshot.)
Now I'm curious:
Is this a problem others face as well, or am I just unusually bad at keeping track of cloud costs?
How are you currently monitoring and managing infrastructure spend?
I'm part of a small org and recently Asked my team for a competitor breakdwn. They came back with a clean, thorough one, which actually covered evertthing in detail and was a Solid work. But it wasn't what I needed. I wanted the one insight I could actually make a call on, not the full picture. We'd been picturing two different things the whole time and neither of us caught it until it was already built.
Still think about the time that cost andd the fact that it was probably my fault for how I framed it. Does this happen to you too, and how do you feel when it does? Curious if it's just me.
keeps happening to me and im never sure if its just us.
ill think ive been clear on what were building and why. team nods, everyone
seems on the same page. then the work comes back and its a different version of the goal than the one i meant. not wrong exactly, just not what i was
going for, and nobody realised until it was already built.
not really looking for "do better kickoffs" advice, more just want to know:
- does this happen to you too
- whats the worst / most expensive version of it youve had
- when you finally caught it, what was the moment that gave it away
starting to think this is the actual hard part of building and nobody talks
about it.
Im working on a deeptech project and had new person joining my team 2 months ago and he attended all the meetings and did tasks too but it is only very recently i understood he had very different perceptions of the product than wht i had in mind.
This made me curious. Have you guys ever had a new hire who seemed productive but later realized they weren't actually aligned on what mattered most?
Is there any signals that i can notice in future to avoid this?
The misses that stick with me aren't the people who drop the ball. It's the ones who do precisely what I said, on time, solid work, and it's still not what was needed, because we'd each been picturing a different version of the priority the whole time.
For those of you managing teams or running at the leadership level, when's the last time that happened to you? I'm after the specifics: what you'd asked for, what you actually got, and the moment you realized your understanding of the goal and theirs had quietly diverged. Did you ever figure out a way to catch that before the work came back?
I've noticed information isn't the same as understanding. I can read 50 articles in a day and get less out of it than if I'd read one and actually thought about it.
I think understanding needs a pause. A bit of time for my brain to fit the idea into what I already know. But I don't pause anymore. A war, a meme, and a market crash all hit me in the same scroll in 30 seconds.
AI feels like it's speeding this up for me. More summaries, more shortcuts, less actual thinking. Does anyone else feel this or am I overthinking it?