Writing is an important skill:
- first, to clarify our own thinking, and then...
- to simplify it for others to take action.
I am excited to announce that I have launched a course on @MavenHQ to help s/w engineering & product leaders get better at writing:
https://t.co/fXqNk5fIpH
(Use the promo code EARLYBIRD for 30% off until Feb 23 or until all spots are filled, whichever is the earliest)
Enrollments are in progress! I have enrolled a few students over the last week, and I have ~5 spots left.
If you are interested (or want to know more), please feel free to check out the course details above and/or reach out to me.
Being consistent with habits is a hard problem.
But I keep trying.
Here's my new framework - I am calling it "Anchor & Connect":
https://t.co/GNILN2efXF
I once worked with someone — let’s call him Joe (not his real name). He could talk on and on about low-level details. But he couldn't help in deriving any higher-level conclusions.
I also worked with another person - let's call him Steve (not his real name). He was a highly regarded expert and he spoke in highly abstract terms with impressive sounding words. But he rarely provided any concrete examples or next steps.
Both sets of conversations left me drained.
Here's one thing they could have done better: this is based on my learnings from the Ladder of Abstraction and how we can navigate it to become better thinkers, writers, and speakers:
https://t.co/wbLV5Lijq4
#writing #communication #thinking
But, why a *cohort-based* course and not a book or self-paced course?
After having attended 3 cohort-based courses over the last few years, I have seen first-hand the benefits it brings:
- rich interactions with the coach AND the peers,
- hands-on exercises and projects,
- more accountability,
- connections with the community,
- helps retain learnings since you are applying them immediately.
Writing is an important skill:
- first, to clarify our own thinking, and then...
- to simplify it for others to take action.
I am excited to announce that I have launched a course on @MavenHQ to help s/w engineering & product leaders get better at writing:
https://t.co/fXqNk5fIpH
(Use the promo code EARLYBIRD for 30% off until Feb 23 or until all spots are filled, whichever is the earliest)
Enrollments are in progress! I have enrolled a few students over the last week, and I have ~5 spots left.
If you are interested (or want to know more), please feel free to check out the course details above and/or reach out to me.
Some context on why a course on *writing*:
Many engineering and product leaders responded to my survey. They want to get better at:
- clarifying their own thinking,
- simplifying the message,
- structuring it concisely and effectively to inspire change.
But they don't want to stop there. They also want to mentor and coach their team to get better at these skills. So, after speaking to a few of them and learning about their challenges and aspirations, I took the logical next step & launched this course.
In hindsight, it looked like a silly mistake.
But I suspect that, in our busy lives, many of us might be making this mistake.
In this story, I share the story of a mistake I did in how I was reading books, and how I am now fixing it:
https://t.co/UwLqqa7jLQ
As more libraries instrument using OpenTelemetry, Tracing can improve Observability even within the context of a single app/service.
This is the beauty of OpenTelemetry's mission "to enable effective observability by making high-quality, portable telemetry ubiquitous." (7/7)
Many people think of "Distributed Tracing" as being valuable only when many/all apps/services in a scenario participate in it.
But even if you enable it for just a SINGLE service in your system, it can save you hours of back & forth.
Here is WHY (based on a real issue): (1/7)
A trace can be reconstructed based on the above span data.
We viewed a representative trace and were able to easily pinpoint the exact sub-operation in the SDK that was taking longer under certain conditions... (6/7)