I maintain this checklist for #SaaS CTOshttps://github.com/stockandawe/saas-startup-cto-checklist …
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Not a course/book, but
@andrewculver's http://bullettrain.co is an excellent set of SaaS best practices with actual code that works out of the box. Not a bad way to tackle the same problems. - Još 4 druga odgovora
Novi razgovor -
-
-
I know
@benediktdeicke started to working on this with https://benediktdeicke.com/saas-guidebook/ . But I guess it is in sleep mode due to the success of Userlist. -
Unfortunately, I have to admit that this statement is very true.
- Još 1 odgovor
Novi razgovor -
-
-
I really enjoyed this free book which shows the three main different approaches to multi tenancy. It's written specifically for Django, but the concepts should apply across frameworks: https://books.agiliq.com/projects/django-multi-tenant/en/latest/introduction.html …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Not a book, but here's a long tweet thread :)
@brettstarkhttps://twitter.com/flybayer/status/1220406529901223936 … -
Thx a lot. Will digest.
- Još 3 druga odgovora
Novi razgovor -
-
-
Nothing specific to SaaS. I’ve always found generic design patterns to be very abstract and hard to apply. For me i’ve sought out ruby/rails specific pattern examples. For Ruby anything by Sandi Metz is great.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
No book but the glaring omission so far is you have to learn how to deploy and operationalize.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
Technical Design Patterns for SaaS
(A thread)
Goals:
• Fantastic end-user experience
• Build as little as possible
• Speedy development
• System resiliency
• Easy for a solo dev
First part is a specific stack, but the rest is stack-agnostic.