@karenb698@Shpigford@JustworksHR It worked ok for a while. It puts more burden on the team members and the max payment won't always cover their monthly costs. Good as a stopgap when you're small, but as our team grew I eventually bit the bullet and got us a UnitedHealthcare plan.
It's a little ironic that for a decade we've been talking about how "AI will wipe out blue collar jobs but artists and intellectuals are safe" -- then AI (quasi) shows up and immediately starts doing art, writing papers + programming apps.
My TypeScript journey so far:
🥳 `strict: true` - Let's type all the things!
😑 80% of my dev time is now just googling...
😩 This is so slow and painful... `strict: false`
🤔 Ok, makes sense to add a couples types here
Next phase TBD
@simpixelated Yea, may be result of JS being the only language that browsers support. It limits the way new frameworks can differentiate... They really have to reinvent the approach. You can argue that's happening now, but "winners" of the previous approach (ex: jQuery + React) stick around.
You can make a case that React is past its prime, but the ecosystem is just sooo massive.
At worst, I think React's fate will be like that of PHP's... it'll become seemingly clunky and uncool, but will remain widespread for decades.
Every piece of SaaS marketing advice I could think of after 6 years as a marketer:
1. Your "market" is not the people who *could* use your product. It's the people who are willing to *pay* for it.
@BairdHall It’s a nightmare. Interstate payroll too. The thresholds for triggering sales tax differ by state and small SaaS product can often stay below them… Regardless, I’d consider using @PaddleHQ instead of @stripe next time to avoid it all.
People are great but managing takes you away from your craft and adds stress. It's just untenable for many technical craftspeople over the long term -- myself included.
The percentage of technical founders I talk to who are interested in building another company but "don't want to manage people this time" is nearly 100% lol