00:00 Intro
01:15 What is Flow
04:40 The Autotelic Personality
07:00 Developer Productivity for Humans
13:30 Summary
Engineering Enablement - Measuring Flow and Focus Developer Productivity for Humans, Part 6: Measuring Flow, Focus, and Friction for Developers
(00:00) Introduction
(01:12) How are we using AI.
(03:40) AI Products and Testing.
(06:26) AI Testing.
(10:09) Summary
Article: Testing LLM-Based Applications: Strategy and Challenges
Topics I'll cover in 2024. ⁃ AI / LLM / Machine Learning ⁃ Book Summaries ⁃ Domain Driven Design ⁃ Flow ⁃ Metacognition / System Thinking ⁃ Software Engineering, Testing Links: - Website - https://www.alanmbarr.com/ - X - https://twitter.com/alanmbarr
- YouTube - https://youtube.com/@alanmbarr
The Start of The Journey
Recovery, The Journey so far
Figuring Out the Next Level of my Learning
https://www.aarp.org/caregiving/health/info-2019/dementia-warning-signs.html
If you like the podcast, please subscribe and share it with others.
Act 1 - Your Elevator Pitch
Act 2 - Prepare and Edit, liberally and ruthlessly
Act 3 - Three Act Narratives, but mix it up
Resources
Edison Research, April 2019 "The Podcast Consumer"
Edison Research Podcast Consumer - 2018
Otter Voice Meeting Notes - Otter.ai
Be a great communicator Podcast
Today’s Topic is a Book Summary by Vishen Lakhiani from the book The Buddha and the Badass.
Act 1 - Make a big vision and great people will find you
Act 2 - Massive Transformation Purpose and Make a Stand
Act 3 - Craft Your Identity
Chainguard -The Principle of Ephemerality via Carlos Santana
Every week, I'll be posting one episode. I stopped in the past because I didn't have enough content to create a podcast with what I wanted to talk about. The podcast will help me improve my writing and voice. Hopefully, the content will be good as well.
Today's topic is Mindfulness and Awareness.
Mayo Clinic says, "Mindfulness is a type of meditation in which you focus on being intensely aware of what you're sensing and feeling in the moment, without interpretation or judgment."
Act 2 - Desire and Suffering
Act 3 -Be Responsible for our actions and Let It Go
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
The Five Disciplines
- Systems Thinking
- Personal Mastery
- Mental Models
- Building Shared Vision
- Team Learning
Gergely Orosz Hiring juniors
"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:
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?