I am out so this week. Please enjoy the techniques of Negotiation such as Never Split the Different

Act 1 - What is persuasion and why should we be persuasive?

Act 2 - Low Stakes Persuasive Techniques

Act 3 - Higher Stakes Persuasion

2021 dev.lab internal developer. I'll be back.

Alan Barr Podcast Interview with Tyler Lemke 

Don't make me think

Empathy Mapping

Mentors in tech

MIX08 Microsoft Office 2007: The Story of the Ribbon

Get Your First Dev Job 

Danny Thompson

Tyler's Youtube

Tyler's Website

Junior To Senior Dev Podcast

The Five Disciplines

- Systems Thinking

- Personal Mastery

- Mental Models

- Building Shared Vision

- Team Learning

Leverage Points in Systems

Gergely Orosz Hiring juniors

Dark matter developers

"The average tenure of software engineers in small companies is only 1.5 years, where it’s 2.3 years for large companies." - Why Programmers Shouldn't Stay in One Company for a long time.

Michael Nygard Coupling Definition

Dave Farley Junior Developer Mistakes

What are the skills you think juniors should be learning?

Act 1 - Your First Ultralearning Project

Act 2 - Nine Principles of Ultralearning

Act 3 - Alan’s Version of an Ultralearning Project/Habit

Summary

You will be more successful if you start by researching your learning plan. You can ask experts or review guides. Shape your environment to focus. Participate in activities that allow you to use the learning in a real or near-real environment. You can learn what you are learning is composed of and learn to drill the parts that provide leverage. As you are applying the learning you are forced to retrieve that information or you are testing your knowledge via other tools. You either seek others to give you specific feedback for improvement, give yourself feedback via tracking, then use that feedback to tweak your learning. To retain what you learn you space learning out over time. You use the Feynman technique to teach others what you know which forces you to confront if there is a gap in your understanding. Finally, you play with variables with what/how you learned something so that it is more interesting and you learn new things about what you are learning.

If you walk away with nothing else:

Raw Book Notes

Andrew Huberman’s neuroplasticity super protocols

In this episode, I review a few books on API Design. The Design of Web APIs by Arnaud Lauret the API Handyman, Irresistible APIs by Kirsten Hunter, and API Design Patterns by JJ Geewax. I also brainfart may refer to Kirsten Hunter as Kirsten Stewart so just ignore that.

Act 1 - What is the goal of the API?

API Goal Canvas - Who - What - How - Inputs - Outputs - Goals

Alan's Digital Garden if the Manning link doesn't work in the future.

Act 2 - What makes a “good” API?

Act 3 - RESTful HTTP Guidance and Support

Summary

What do you do when the majority of software in the world is vulnerable to a remote code execution exploit via the logger? The one type of system the majority of programs run. How can we get better as an industry to benefit from sharing our code but also keeping our code up to date? Can we show restraint in adding features? Can we improve our quality and review processes to find these types of mistakes sooner?

Act 1 - Self-Awareness

Act 2 - Emotional Regulation

Act 3 - Patience and Acceptance

If mastering the fundamentals sets us apart, what are those fundamentals?