Is #LearnInPublic suitable for everyone?
What if I look dumb?
My answers below, but I'd love to hear yours too!
(DM shared w/ permission)
1/ Learning in Public is *not* “broadcasting everything”. Nobody wants that.
It is about realizing you have a choice to go from 0% to not-0% public. The stuff you do share, you will learn faster, while building a network. It’s up to you to set the boundaries of what you share.
2/ Understanding how to turn your ignorance into power is a key career skill. If you want to grow at all you must make ignorance an old friend, and make friends out of ignorance.
Lean into the discomfort. Become a professional (but responsible) ignoramus
We are besieged by todo lists: Open browser tabs, YouTube Watch Later, Podcast queue, Twitter bookmarks, unread emails, notifs, messages.
Todo lists aren't good enough.
They just solve the easy problem: storage.
Actual Hard Problems: Prioritization and Scheduling
Calendars are todo lists with prioritization and scheduling **built in**. You *have* to answer questions like: "what should I do first?" and "what's my time budget for this?"
Most people's cals only track meetings with others. But why shouldn't we make appointments w/ ourselves?
A reader asked about mental models that I learned from my finance days, that are still relevant for developers.
Here's a quick thread in no particular order, let me know what resonates or mystifies:
1. The Role of Confidence (Being a Con Man)
- People are attracted to confidence for interviews and promotions
- We aren't as objective as we think
- Jobs which traffic in confidence are prone to bullshit
- Assess each choice relative to your other options.
- For employers: be great at finding and evaluating options in ways they care about
- For your self: Accumulating options = Building wealth
- "Making past mistakes look good" is not an option
I was asked about why declarative programming is at the heart of "newer" trends in tech all the way up and down the stack, from React to Terraform.
I replied in an email but here it is as a quick thread:
DOM APIs are imperative, which encourages manual setup/teardown of event listeners, and intermingling of business and presentation logic.
At best this is just quite verbose and disorganized, at worst this creates runtime bugs and memory leaks. Lack of structure is painful.
We use React/Vue/Svelte to organize code into declarative components, help us organize the above and automate the boring parts. It also lets us *share code* much easier because the markup, state, and styles are scoped to the component, so they don't leak to the rest of the app.