Notes on “How to Write Online Workshop” by David Perell

In this ~1 hour video David Perell explains his method for writing. The Capture Habit You need a note-taking system for generating better ideas. What ideas should you save? PILE: personal inspiring easily lost (losable) effective (useful) Sources: ebooks, online articles – use a service like readwise. Capture your ideas while you read. Capture things while they are fresh. Writing Modern writing isn’t created. It’s assembled.
Read more →

Notes on ”How to Build a Career in Tech”

Notes on ”How to Build a Career in Tech”
Kurt Kemple is a self-taught programmer who learned to code when incarcerated. In his talk with Jason Lengstorf he shares his experiences. Here are my notes from the ~1 hour video: Technical skills are a small part of your day to day job. Kurt learned how to prioritize, commmunicate with others and how to organize the work from his previous experience in construction work and as a line cook. Break a big task into small pieces.
Read more →

Notes on “Hack Your Career”

Notes on “Hack Your Career”
Troy Hunt talks about his journey from a corporate software job to independence in Hack Your Career (58 min video). Troy is probably best known for the platform have i been pwned?. One of the best ways to make yourself more marketable as a software developer is have an active online profile What opportunities are you going to make for yourself? Start a blog. If you are willing to put yourself out there (writing online), you get valuable feedback from others.
Read more →

Notes on ”Advice for Your First Dev Role”

Notes on ”Advice for Your First Dev Role”
Virtual Coffee is a remote community for developers that aim to support each other. They offer “brown bags” which are talks and discussions about a specific topic. Here are my notes from Advice for your first dev role by Bryan Healey: Remember that there will be a ramp-up period. You should take the time to talk to other engineers in your team. Learn about the tooling stack as soon as possible.
Read more →

Notes on “How to Become a Better Developer With Nacho Iacovino“

Notes on “How to Become a Better Developer With Nacho Iacovino“
Notes from the Twitch stream with Francesco Ciulla and Nacho Iacovino (1 hour 17 mins): Nacho Iacovino is a self-taught developer from Spain who grew his Twitter account in a short time. Here are some tips that he shared. Coding interviews: He learned from each interview. Even if you can’t answer a question, you can go home, research, and then you can answer the question on the next interview. It’s a process.
Read more →

Notes on “Enterprise Architecture Patterns“

Notes on “Enterprise Architecture Patterns“
The goal of the workshop is to learn the mental models and patterns to reduce complexity in software development. The principles from the course are framework-agnostic, but the teacher uses examples from Angular. (I found the concepts front-end centric. That’s unsurprising as the course platform targets front-end developers). What are “enterprise patterns”? The core problem across all enterprise software is complexity. We strive to solve complexity by diligently applying first principles.
Read more →

Notes on “Ramping Up at Your First Developer Job”

Notes on “Ramping Up at Your First Developer Job”
Read more →

Summary of “Hyperfocus“ by Chris Bailey

Summary of “Hyperfocus“ by Chris Bailey
These are my notes and summary from the book Hyperfocus by Chris Bailey. 🚀 The Book in 2 Sentences The book teaches you about two kinds of focus: “hyperfocus” and “scatterfocus”. It offers tactics on how to build an environment that’s conductive for better focus and why that’s useful for you. 🎨 Impressions How I Discovered It Last week I bemoaned my lack of focus. I decided to learn more about how focus works to improve my strategies on becoming a better software developer.
Read more →

Summary of ”What Programming Is Never About”

Summary of ”What Programming Is Never About”
Read more →

Notes on the Pluralsight course “Angular Best Practices” by Jim Cooper

Notes on the Pluralsight course “Angular Best Practices” by Jim Cooper
Notes File and Folder Structure LIFT: Locate code quickly, Identify code at a glance, Flattest structure possible, Try to be DRY organize code into feature areas one item (service/component/directive) per file General Coding Practices Single Responsibility Principle (example: re-factor data access service to separate services for user and catalog) prefer immutability use small functions Angular Module Organization App Module Core Module: shared singleton services, app-level components (e.
Read more →

Sign up for the newletter!

powered by Buttondown