I find that the rushing to automate
Which the entire tech space posts about
Completely assumes it's the right process to calcify
You're automating a process that is not already optimized
"The sun, with all those planets revolving around it and dependent on it, can still ripen a bunch of grapes as if it had nothing else in the universe to do."
Done in #Threejs and #webgl
Inspired by NASA's SDO Wavelength Graphics
@nntaleb@mathoncbro A true NNT fan would blow hot air periodically to enforce antifragility
Otherwise the user will get used to the breeze and take it for granted
every post I see is on how easy it is to automate things
but one needs the process optimized manually to make sure they don't automate something that shouldn't exist in the first place
had this crazy change in psyche 2 months ago looking at my portfolio
at mostly dead startups
and only 2 profitable
and realizing it's just a graveyard of useless shit
and that if i could just make one thing that was still in use
that'd be a win
(and just as lucrative as this)
For the longest time my default to "what I wanted to do" was create a suite of SAASes
But that just led me to deadends and dumb products
If I had a unicorn alone it'd still suck
If I had a unicorn that wasn't useful I'd feel like a leech
Utility over all
Day 20 of FDE curriculum/job hunting
Role secured! Strong product with really cool team (pass "layover test")
Now time to be useful as possible in all I do, online and offline
Day 12 of FDE job search:
Technical went well - same feeling as crushing an exam regardless of grade. Excellent organization, despite poor time management in the actual implementation.
Screen went well - really vibed. Helps vibing with most founders ig - some more than others
Because I was asked by a friend - I don't really sweat these or take it personally.
Startups are hectic, and there's a lot of balls in the air. Again, it's best to treat them as systems, and not confuse the unit for the system
Day 11 EOD of FDE curriculum building
1 screen really vibed, 1 didn't, technical interview - interviewer didn't even show.
Seemed like a mistake. Not my problem. Got another full day tomorrow with 1 screen and 1 technical
I think the most challenging thing here is trusting in a process that has not been enacted yet.
But if you know the first principles of it, and trust in the rate - the process - and not the outcomes - which are units in a system - you can stay sane, happy and calm under stress
Day 11 of FDE job hunt/curriculum building
This process is built on the thought not of drilling tons of possible problems but treating the search as an antifragile processes, learning from each node, repairing, trying again.
What's on deck today:
These guys don't know my potential, only my current state.
Not their fault - it's our job to realize our potential or communicate that.
So any skills I didn't have last week I have now, and that rate of learning to me is more valuable than some snapshot today
Note on Push
I don't find "just do it" helpful. You should question and be thoughtful about what you do, but only enough to start working.
I detach from outcomes. I set a goal I'd be suprised doesn't hit (100 apps for 1 interview), set a deadline (10 days), and perform (10/day)
I build a lot of structure into my day, but the most reliable is a simple push, pull, and a checklist daily.
Push - planning for the next n days
Pull - execution with a checklist daily
Note on Pull
Execution I aim for 3 hour chunks in a row, with named goals each one. Why?
A win in 1 hour doesn't win the day
But a tear on 3 hours peak could actually.
You could win the day by noon, then just pour it on that afternoon into the night