I put my blog posts into a knowledge graph so you can ask how different topics are connected... the best part is that it runs a language model IN YOUR BROWSER.
Check out the demo below.
[Knowledge Graph Search]
You can learn anything you want in 30 days.
Over the past month, I've taught myself Lisp, Rust, and JavaScript. The entirety of my formal programming education was one entry level CS class.
Here's how to learn anything with a 3 step feedback loop:
My co founder
@caddycapital
and I are on a mission to make our start up, BirdDog, hit $100K ARR by the end of the year.
Currently, BirdDog has no product and $0 in ARR.
Here's the roadmap:
After a couple weeks of hacking, I'm proud to say that BirdDog has an MVP to show the world.
I've been vague about what BirdDog is (we're still figuring out ourselves), but a great way to describe it is command F over your prospect list.
When you debug your code, you're really debugging yourself.
As you start to observe patterns in your errors, and you start fixing the sources of those patterns, you're making yourself a better programmer.
I made a not at all spontaneous decision to start a weekly newsletter about what I'm up to. Shoot it a subscribe if you find the first one interesting:
It seems that success and failure both come from small, repeated actions over time.
Watching "one more" four minute youtube video is surprisingly close to sending "one more" cold email or improvement on the code base.
Starting is harder than continuing.
You're not a hacker bc of what you can achieve with your computer, you're a hacker bc of all of the steps you don't have to take to achieve those things.
Given enough time, anyone can do anything.
A hacker can do it with speed & accuracy.
If I didn't schedule meetings with users & promise them I'd have things to show them I would probably just keep coding in circles indefinitely.
Work is necessary but not sufficient; you need feedback, too.
You don’t win by fighting, you win by training.
If I beat someone whose been grappling for 3 months, I didn’t beat them when we went at it.
I beat them 2.5 years ago when I started.
Thrilled to be building on
@praxisnation
. If you are, too, dm me for priority access to Ultima Mercury, the last sales enablement tool anyone will ever need.
Ultima just secured it’s first contract since we pivoted into sales in late November.
Pay on performance, nothing huge, but an awesome step in the right direction.
Time to perform.
The greek guy who gave me a haircut yesterday paused before I got out of the chair, looked me in the eye, and said, “Be safe tonight.”
That’s the kind of energy you should have towards your customer after selling a saas product.
I love how often I find myself thinking “this is the best code I’ve ever written.”
It’s a constant reminder that there is still so so so much further to go. Each iteration will be so much better than the last.
You're not paranoid, you're just insecure.
Just assume they've already said all the things you're afraid they might say.
If the things are true, figure out why they bother you.
If the things are lies, disprove them with your future actions... or, get over it.
You're not afraid of the blatant lies they're saying about you.
You're afraid of the lies they're saying that contain the truth.
Meaning, really, you're afraid of the truth.
Over the past 1.5 months, I've been staying at the Harvard Hacker Houses, ran by
@edchucation
The experience involved Category Theory, hacking, piano, jiu jitsu, and adopting birds. Check out my love letter to C House:
1) Consume Information
Take in as much information about the thing you're learning as you can. The important part here is that you integrate it with your worldview.
The less I code like I know what the "perfect" solution is, the better my code ends up being.
My assumptions about "perfection" are usually wrong; I think the key is making something that works and then aggressively improving it as the world tells you where it's bad.
I went on the craziest bike ride of all time with
@bobby_housel
yesterday.
Dozens of energy gels, six flat tires, four angry dogs, a funeral procession, an unsafe town at sundown, and a police station.
Check it out:
The design of your product is subservient to the problem it solves, not the product's technical implementation.
If you get to design your leg muscles, you should change your gait because you want to move faster, not because your muscles are designed in a limiting way.
Hoping that the value of a product is directly related to how quickly you can improve your assumptions.
Either that or I'm just coping for the dozen or so bad assumptions I've already found and removed.
Dozens more to come, I'm sure.
As an example, I compared the way you can use lisp to increase levels of abstraction to how you should make applying pressure in jiu jitsu second nature. That way, pressure is on auto pilot when you go for a higher level thing, like a submission.
3) Keep Learning
You'll make mistakes; they're there to teach you.
If it's a simple mistake, leverage a system to avoid it. You don't have to remember that declaring a function in your lisp dialect uses "defn" if you can just scroll up in your code to refer back to it.
Some friends and I from
@Ultima_Insights
have put together an
#AI
pipeline to summarize news flow on your portfolio via email every morning, and we need as much feedback as possible!
Front end is still a bit glitchy, but here's the link:
Following this method, this year alone, I've taught myself 3 programming languages, closed my first B2B sales, and started surfing.
If you want to join me on my journey of learning how to learn, click the link in the bio to subscribe to my weekly newsletter.
2) Execute
If you're trying to learn how to code, code.
But, make sure that all the while, you keep referencing back to the information you've consumed.
If the quirks in lisp are there to help you abstract away your code, you better be abstracting it away.
Took me a week to get my first sunburn in costa rica, and it’s really not that bad; yet, I have been spending ~40% of my waking hours outside and haven’t worn sunscreen once.
I still don’t plan on it.
You can get pretty far if you’re just careful. Next time I go on a midday
The habit tracker is not the goal.
The habit tracker is how you maintain a minimum acceptable state or a minimum level of progress in secondary fields while you push towards the primary objective.
Full post here:
Surprising similarity between Bee Keeping 🐝 and Brazilian Jiu-Jitsu 🥋: Forced calm.
There's a negative feedback loop around shallow breathing and panicking... if you're not breathing deeply and keeping a clear head, the bees sting you or your opponent taps you.
"Why waste time say lot word when few word do trick?"
Kevin from the office was on to something--minimizing the length of information and maximizing the value of the signal is value add for society.
My reflections on signal density:
You give us a prospect list & some keywords you care about, and we go to town finding relevant quotes.
You can use those quotes to understand the prospect, write a killer cold email, and, if you're good enough at what you do, maybe close the deal :)
My favorite director is Werner Herzog. 70 movies, 12+ books. The man ships.
He embodies the belief that the best way to produce a high quality of product is to produce a high quantity of product.
Full take:
"But I don't think of you." -Howard Roarke
Overcoming your "enemies" means letting go.
If someone hurt you, and you keep feeling hurt by it, they're still hurting you.
The best victory is moving on.
Overheard at a founder house:
"Oh, I just realized it's the super bowl tomorrow."
"Whose uh... whose like... playing?"
"Uh the chiefs and 49'ers, I think."
"Oh. I don't know those guys."
I've found my people.