@MichelTricot and @JeanLafleur are building the fastest growing ELT startup ever. 0 to 10,000+ companies syncing data in 1 years, planning to grow >500% this year. Ask @avaidyanatha how our OSS is a perfect match: temporal.io/airbyte
@andyasprou has been bootstrapping the first ever all-in-one Instagram hashtags platform and analytics suite, and loves @temporalio for the massively parallel scraping and scheduling work!
Shreyas is doing a live workshop for super-followers now, he gave us permission to tweet notes and it's been a hot minute since I livetweeted an event, so here goes:
Extended annotations on @shreyas' Time Management ππΌ
The origin story starts with this looongstanding open issue on TSDX from @n_moore. As an early helper on TSDX I shied away from it bc I thought that it should be solved by dedicated tooling like @yarnpkg.
Big monorepo shops like Facebook and Google have loads of tooling to make monorepos work, but this class of tooling never made it out into open source.
@TurboRepo does 3 things:
- Make monorepos zero config
- Make monorepos incrementally adoptable
- Make monorepos scale
Trying out @factoriogame for the first time this weekend
If you don't hear from me... you'll know its going well
@factoriogame streaming it actually DM to jump on stream and chat if we know each other
Before I attempt the last tutorial I'm checking out a few tips and tricks videos to see what I'm doing suboptimally and there's a LOT! man, tutorial was good but I was doing so much manually that they could've just told me outright...
This year I've done a total 180 on open source strategy.
Remember Elastic making a fuss with "Amazon: NOT OK"? I was quite persuaded. If MongoDB, Redis, Cockroach, Confluent relicensed and do fine, maybe SSPL just becomes acceptable "open source".
Now I think MIT is just fine.
Probably my biggest test of confidence was in March when @martin_casado and @davidu pushed back on the open source religion - if your monetization is SaaS, then open source is just marketing (there's nuance here, pls read his replies before reacting)
Open sourcing has a cost - at @temporalio it impacts decisionmaking in engineering, product, docs, devrel. Tradeoffs we wouldn't have if we just had a free tier.
But look at how extensively @NetflixEng has been able to adapt our SDKs and devtools:
in fact iβm -so- not a perfshamer I shall now say the thing Iβm not supposed to say:
before today you didnt know or care that Notion had a 9.1MB JS marketing site; if it impacted them enough they wouldβve fixed it sooner; you may have a fast site but they have 10 million users.
- Delivery lead time
- Deployment frequency
- Mean time to restore service
- Change fail rate
What would the 4 key metrics of Dev Experience be?
my picks:
π Time to World Tour
Anyone can do "Hello World" with `git clone` and not teach a thing. More impt to give the developer a useful mental model of what they should know in short time.
You can't visit all 192 countries, but you can show that there are 7 continents.
πββοΈ Time to Implement Change
Anyone can build brittle systems. But great DX optimizes for 1-2 standard deviation changes in requirements:
- find helpful docs fast (better: no docs needed)
- low edit distance
- smooth migration paths