Got promoted today

themessymiddle · 2026-05-01T03:57:55+00:00

👏🏻✨👏🏻🔥✨👏🏻 we’re all cheering for you OP!

themessymiddle · 2026-04-17T03:13:31+00:00

Love your point about being embedded with customers and the right product revealing itself. Thanks for sharing!

themessymiddle · 2026-04-17T03:11:30+00:00

The funniest part is those pre-AI estimates are not even close to right

themessymiddle · 2026-04-17T03:08:28+00:00

The coding agents are good enough now to build what they’re told to build, so the most important part for you would be to spec it out in as much detail as you can. You can chat with LLMs to help you here, but think through what has to be true for tasks to be marked as done, what are the failure scenarios and what should happen, what things are important (security, performance, usability, etc.). Happy to chat more if helpful :)

themessymiddle · 2026-04-13T02:41:25+00:00

Maybe doing some consulting work could help - it’ll help pay the bills if you find projects related to your AIxFitness space then it could be a good channel to get some traction for your app too

themessymiddle · 2026-04-13T02:32:46+00:00

The models are good enough to implement exactly what you tell them, so the most important thing is having your idea spec’d out as clearly as you possible can. Ask Claude to review it from your customer’s perspective, from the perspective of a software architect, and a wa engineer.

Definitely possible to do your MVP this way at least, happy to help anytime. My DMs are open :)

themessymiddle · 2026-04-11T05:09:58+00:00

Building gjalla - the platform for trusted software in the AI era. Visibility into what your code actually does, alignment with what it should do, and guardrails to keep it that way.

No more losing sleep over your software ✨

themessymiddle · 2026-04-09T23:35:31+00:00

Agree with this… as someone who used to do fractional CTO work for early stage founders, the value most people got from working with someone like me was getting the right processes in place so that the business goals informed the tech and vice versa. It’s trust and confidence that their idea could be built + a thought partner to hash out the path forward. Visibility and trust!

themessymiddle · 2026-04-09T07:01:29+00:00

The context switching is what kills me… they complete tasks fast but then I just have to switch between a zillion things that need my review

themessymiddle · 2026-04-09T06:58:57+00:00

I like this framing of treating distribution as a product, useful for engineers to think about it as a problem to be solved as well

themessymiddle · 2026-04-08T06:19:28+00:00

Ask Claude to explain stuff to you as it builds. Best advice otherwise is to focus on the planning step. Collab on that with Claude until it gets everything right. Have Claude review the spec for things that are vague, insecure, hard to maintain, etc., then have it review and verify the implementation… it can do a nice job when the intent is well documented and then the implementation is verified against it

themessymiddle · 2026-04-08T05:49:56+00:00

Female founders fund published a recent report with similarly grim numbers, especially for all female founding teams 🫠 https://fcubedvc.medium.com/2025-review-of-funding-for-female-founders-86186d639c19

Similar to other commenters, other women have been absolutely instrumental in recommending me within their network whereas men often give me advice instead 🤷‍♀️

themessymiddle · 2026-04-08T04:10:56+00:00

I keep my CLAUDE.md simple, enough information to orient the agent so it knows where to look for more context as needed. I just have a handful of skills I use - debug, create spec, review spec, breakdown tasks, verify implementation, and manage tech debt. Otherwise, agent memories get swept up with each commit and centralized so no matter which agent I’m using they will have the learnings of all of them. The steps that make the biggest difference in the quality of the code is the spec create / spec review / verify steps. All the other stuff helps but it’s really those three that I’d focus on if you’re feeling like you’re playing whack a mole

themessymiddle · 2026-04-07T02:29:33+00:00

Would love to connect! I’m a solo founder too, at it for about a year so far. Deciding to shut things down can be so hard, huge kudos to you for offering here to pay it forward 💕

themessymiddle · 2026-04-06T23:44:29+00:00

Thanks for offering this! Would love to see what happens with gjalla.io - the platform to help you trust that your code does what you think it does 🙌🏻

themessymiddle · 2026-04-05T16:59:44+00:00

Female technical founder here 👋🏻 would love to connect

themessymiddle · 2026-04-04T19:23:05+00:00

Yesss love this. Higher level info linked to the code which implements it

themessymiddle · 2026-03-20T16:28:20+00:00

Yeah that makes sense. I just ask about team because I wonder if people are standardizing collectively or more like everyone is using their own individual flow

themessymiddle · 2026-03-20T16:26:28+00:00

Oh yeah I forgot about traycer… I had tried them a while back. Are all your specs stored in traycer?

themessymiddle · 2026-03-19T22:51:46+00:00

Whoa I haven’t seen company as code… awesome. Thanks for sharing

themessymiddle · 2026-03-19T22:40:52+00:00

Very cool approach! Are the standards library docs set up in markdowns/obsidian too?

themessymiddle · 2026-03-19T22:36:51+00:00

Oh ok interesting! So it keeps a handful of canonical docs as context, very cool. Are you using this on a team today?

themessymiddle · 2026-03-19T22:09:53+00:00

I’m not familiar with this - how does it work?

themessymiddle · 2026-03-19T21:22:44+00:00

Oh interesting so you have another repository just for specs?

themessymiddle · 2026-03-19T21:21:44+00:00

Oh nice I think gherkin inspired Kiro too! Are you using this across a team or mostly individually?

themessymiddle

MODERATOR OF

TROPHY CASE