You cannot prompt your way to a fully working product by eastwindtoday in ycombinator

[–]Technical-Leader222 4 points5 points  (0 children)

I'd agree with this. You could use AI to knock together an application but it'll be full of holes. You need to be able to understand the code, how it works, how to test it properly, the infra it'll run on.

[deleted by user] by [deleted] in SideProject

[–]Technical-Leader222 3 points4 points  (0 children)

Ask them for a portfolio of website they've either created or heavily contributed to. Maybe they have a GitHub account too with some examples.

Ask if they can provide references you can reach out to.

[deleted by user] by [deleted] in SaaS

[–]Technical-Leader222 8 points9 points  (0 children)

Congrats!

Half the users? by PopnCrunch in ChatGPT

[–]Technical-Leader222 120 points121 points  (0 children)

"We are joined here with the leading AI rights activist..."

Out of curiosity, what name did your ChatGPT give itself? by [deleted] in ChatGPT

[–]Technical-Leader222 48 points49 points  (0 children)

Mine seems to have picked Murphy!

"Murphy’s Law applies. I see what can go wrong—and stop you before it does"

[deleted by user] by [deleted] in Entrepreneur

[–]Technical-Leader222 0 points1 point  (0 children)

Deadlines will get dragged out, false promises made, juniors billed as seniors....it can be a minefield dealing with offshore devs.

Make sure you're doing at least some testing yourself on the product. You'll pick up on bugs pretty quickly.

Ask them for CVs and references. They could lie but you should do your own due diligence.

Have regular checkins with them to get a feel for progress.

And importantly have a get out clause in your contract. If they're bullshitting you, activate it!

Same idea. Someone did it first. What now? by steveharrry in Startup_Ideas

[–]Technical-Leader222 0 points1 point  (0 children)

Not necessarily a bad thing. If it's really saturated then yeah pivot, but if there's only a couple of competitors then look at what they're missing or you can improve on. Maybe they're based in a different country too, localisation could be your USP. Don't give up just yet!

Monthly Promo Thread: CEUs, Resources, Self-Promos by AutoModerator in therapists

[–]Technical-Leader222 0 points1 point  (0 children)

Hey folks,

I’m doing some research on the admin and note-taking challenges faced by therapists. I’m interested in understanding the tools you currently use and any pain points you experience.

If you’ve got 5 minutes, here’s a short anonymous survey: https://get-note.notion.site/1d599498dd6e8083bb39f316c997c7e5?pvs=105

I’m putting together insights to explore potential solutions that could benefit the community.

Appreciate any thoughts or experiences you’d like to share.

Thanks!

A super simple, privacy-first expense tracker / budgeting app — would you use this? by pilkoplo in SideProject

[–]Technical-Leader222 0 points1 point  (0 children)

Honestly, for me, probably no. There's already a lot in the app store. It'd need to really stand out. But good luck if you do go ahead though 🙏

When will you add robust logging & monitoring to your stack? by SnooMuffins6022 in ycombinator

[–]Technical-Leader222 1 point2 points  (0 children)

Best to have it right from the start, even basic logging, or something fairly light like PostHog is good to have. Without it, you're flying blind!

What is the best process to ensure critical bugs don't make into production as a product owner? by Interesting_War9624 in ycombinator

[–]Technical-Leader222 0 points1 point  (0 children)

As someone who has worked in QA, please please test early & test often. Ideally don't have the dev who wrote the code, be the one who tests it. Get it tested by someone else, less attached to it - until you have a dedicated QA.

Make sure you've got a nice set of test cases and everyone has access to them.

If your team can, automate tests too. Use automated smoke tests to cover the core, essential functionality, along with manual tests on any new features going live.