Zmbnski's Categories
Zmbnski's Authors
Latest Saves
The Beatles wrote “Yesterday” in less than a minute.
Led Zeppelin wrote “Rock And Roll” in 30 minutes.
The White Stripes, “Seven Nation Army”, 10 min during a soundcheck.
The Rolling Stones, “I Can’t Get No Satisfaction”, 40min.
Making a startup in 24 hours is perfectly fine.
I worked on my first startup for 2.5years. It was an events app. Sunk in cost and expectations were so high, that I had to close it, despite getting consistent revenue.
In comparison, I wrote @CryptoJobsList in 2 days. And it's way more meaningful than what I've been doing in my events startup for 2.5 years.
When I let go of my engineering ego and let go of expectations that I need to raise capital and hustle for 4+ years — I started lauching fast and interating fast without any expectations — then I started coming up with something truly meaningful and useful ✨
12 startups in 12 months by @levelsio
24 hour startup by @thepatwalls
— are great challenges that make you focus on the end product value, iterate fast and see what sticks and ruthlessly kill what does not work.
Led Zeppelin wrote “Rock And Roll” in 30 minutes.
The White Stripes, “Seven Nation Army”, 10 min during a soundcheck.
The Rolling Stones, “I Can’t Get No Satisfaction”, 40min.
Making a startup in 24 hours is perfectly fine.
I really think this idea of starting a starup in 24 hours is bad idea. Gives people thinking that you can do something meaningful in short period of time. https://t.co/l3x2ov33Qn
— Myk Pono \U0001f60e (@myxys) November 10, 2018
I worked on my first startup for 2.5years. It was an events app. Sunk in cost and expectations were so high, that I had to close it, despite getting consistent revenue.
In comparison, I wrote @CryptoJobsList in 2 days. And it's way more meaningful than what I've been doing in my events startup for 2.5 years.
When I let go of my engineering ego and let go of expectations that I need to raise capital and hustle for 4+ years — I started lauching fast and interating fast without any expectations — then I started coming up with something truly meaningful and useful ✨
12 startups in 12 months by @levelsio
24 hour startup by @thepatwalls
— are great challenges that make you focus on the end product value, iterate fast and see what sticks and ruthlessly kill what does not work.
1/ 👋 Excited to share what we’ve been building at https://t.co/GOQJ7LjQ2t + we are going to tweetstorm our progress every week!
Week 1 highlights: getting shortlisted for YC W2019🤞, acquiring a premium domain💰, meeting Substack's @hamishmckenzie and Stripe CEO @patrickc 🤩
2/ So what is Brew?
brew / bru : / to make (beer, coffee etc.) / verb: begin to develop 🌱
A place for you to enjoy premium content while supporting your favorite creators. Sort of like a ‘Consumer-facing Patreon’ cc @jackconte
(we’re still working on the pitch)
3/ So, why be so transparent? Two words: launch strategy.
jk 😅 a) I loooove doing something consistently for a long period of time b) limited downside and infinite upside (feedback, accountability, reach).
cc @altimor, @pmarca
4/ https://t.co/GOQJ7LjQ2t domain 🍻
It started with a cold email. Guess what? He was using BuyMeACoffee on his blog, and was excited to hear about what we're building next. Within 2w, we signed the deal at @Escrowcom's SF office. You’re a pleasure to work with @MichaelCyger!
5/ @ycombinator's invite for the in-person interview arrived that evening. Quite a day!
Thanks @patio11 for the thoughtful feedback on our YC application, and @gabhubert for your directions on positioning the product — set the tone for our pitch!
Week 1 highlights: getting shortlisted for YC W2019🤞, acquiring a premium domain💰, meeting Substack's @hamishmckenzie and Stripe CEO @patrickc 🤩
2/ So what is Brew?
brew / bru : / to make (beer, coffee etc.) / verb: begin to develop 🌱
A place for you to enjoy premium content while supporting your favorite creators. Sort of like a ‘Consumer-facing Patreon’ cc @jackconte
(we’re still working on the pitch)
3/ So, why be so transparent? Two words: launch strategy.
jk 😅 a) I loooove doing something consistently for a long period of time b) limited downside and infinite upside (feedback, accountability, reach).
cc @altimor, @pmarca

4/ https://t.co/GOQJ7LjQ2t domain 🍻
It started with a cold email. Guess what? He was using BuyMeACoffee on his blog, and was excited to hear about what we're building next. Within 2w, we signed the deal at @Escrowcom's SF office. You’re a pleasure to work with @MichaelCyger!
5/ @ycombinator's invite for the in-person interview arrived that evening. Quite a day!
Thanks @patio11 for the thoughtful feedback on our YC application, and @gabhubert for your directions on positioning the product — set the tone for our pitch!

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.