pragprog.com/titles/rmrfsd/
pragprog.com/titles/snokrs/
pragprog.com/titles/jkthp2
pragprog.com/titles/mmteams2
Rob Moffat
@staffannoteberg.bsky.social
Sandy Mamoli
David Mole
Joe Kutner
It's alive! Komplexitetspodden (The Complexity Podcast) is now available at Apple podcasts.apple.com/us/podcast/k...
...and at Spotify: open.spotify.com/show/40Cpa7M...
First episode: Enkla regler (Simple Rules). A new episode, featuring a unique theme, will be published every Thursday.
Each episode is a conversation with a hard limit: exactly 25 minutes, timed with a mechanical kitchen timer 🍅. When the bell rings, we stop—even mid-sentence. It's our way of acknowledging that conversations about complexity have no natural end.
Stay tuned for more information in upcoming weeks.
(2) Outcomes of Complexity: Emergent phenomena such as tipping points, fractals, and self-organization.
(3) Tools for Navigation: Methods and frameworks like nudging, jamming, and quenching to help analyze and act within complexity.
We have identified roughly fifty topics—one for each episode—breaking them down into three categories:
(1) Sources of Complexity: Factors like diversity, numerosity, and feedback.
In Komplexitetspodden, we aren't presenting ourselves as experts. Rather, we are curious guides exploring complex ideas alongside our listeners. We'll use everyday anecdotes and stories to help spark their own thoughts and reflections.
This is what we, Ola Ellnestam and I, will be exploring in our new project: the Swedish-language podcast named "Komplexitetspodden." We have our first recording sessions booked, and we plan to release a new episode every Thursday during the fall.
Hindsight makes every failure seem obvious. A phantom traffic jam appears from nowhere, only to vanish moments later. Unwritten rules at the office dictate collaboration far more than any employee handbook. Phenomena of complexity that can't be understood by simply looking at their individual parts.
Sweet dreams are made of this. Who am i to disagree?
Everybody’s looking for something...
Book review: Guiding Star OKRs
Setting, tracking, and reporting OKRs is terrible. But what if it wasn't? In Guiding Star OKRs: A New Approach to Setting and Achieving Goals, Staffan Nöteberg lays out a framework that focuses on heading in the right direction instead of trying to meet exact…
Spring Best Sellers Sale, Week 2
40% Off – This Week Only!
Code: 2025testing at checkout
pragprog.com/titles/...
@staffannoteberg.bsky.social
I've got 52 years of experience so far.
Started FORTRAN programming at age 8 in 1973.
8080 machine language programming in 1977.
6502 and BASIC programming in 1978.
8086 and C programming in 1986.
VAX/Sun/BSD/SysV in 1988.
Became professional (VAX/VMS dev) in 1990.
Modern C++ in 2017 :)
Book cover a white telescope with brass trim
Celebrating Guiding Star OKRs by Staffan Nöteberg, now in print!
🔗 Read more: medium.com/pragmatic...
📘 ebook: https://pragprog.com/titles/snokrs/guiding-star-okrs/
#teams #leadership #goals #okr #pragprog #books
Guiding Star OKRs
by bestselling author Staffan Nöteberg
@staffannoteberg.bsky.social
With knowledge distilled from diverse industries, this new approach teaches you to create a compelling “Guiding Star” vision that combines purpose, unified direction, and the freedom to adapt when needed.
Sometimes, we find outstanding self-published titles we 'd truly feel proud to distribute. It's wonderful when our audience agrees.
Right now, 3 of those distribution titles are on our bestsellers list!
pragprog.com/best_se...
@miguelgrinberg.com
Minh Quang Tran
@staffannoteberg.bsky.social
Bestsellers for the past week: http://pragprog.com/best_sellers/
Top 3:
#1 Regular Expressions Machinery
#2 Ash Framework
#3 Real World Event Sourcing
@staffannoteberg.bsky.social
@zachdaniel.dev
@sevensea.cat
Minh Quang Tran
“One standout feature of the book is the focus on applying TDD to regex. Writing correct and maintainable regexes can be challenging, especially in production code. By combining regex with TDD, you can write patterns that work flawlessly and stand the test of time.”
medium.com/pragmatic-pr...
Just as twins can inherit different combinations of genes, perhaps these two books, despite their differences, inherit common traits from the author's voice and the way information is structured.
That said, they share some important DNA:
– Fresh Perspectives: Both books offer unique insights into their respective subjects.
– Practical Tools: Both equip readers with knowledge and tools to achieve specific goals.
– Accessibility: Both are written to be accessible to their intended audiences.
I'm about to release two new books, almost like giving birth to twins. And while they're arriving at nearly the same time, they're more like fraternal twins than identical ones. They have different target audiences and were researched in different ways.
Thanks Kadu.
I tdd regexes in isolated functions. It improves my confidence. And extract-method-refactor legacy regexes to exploratory code test them.
As the subtitle suggests, the book uses plenty of illustrations to cater to different learning styles.
Stay tuned for details on how to get your hands on a copy!
[n/n]
PART III: SYNTACTIC SUGAR, ABSTRACTIONS, AND EXTENSIONS. We'll cover the familiar syntax, from basic quantifiers to advanced lookarounds, and I'll highlight common traps to avoid. Numerous examples illustrate these concepts.
[4/n]
PART II: TWO OPERATIONS AND ONE FUNCTION. Believe it or not, all regular expressions can be built from just two operations (spoiler alert: concatenation and alternation) and one function (second spoiler alert: the kleene star). This section demystifies the core logic.
[3/n]
Rather than presenting a dry list of syntax, I've structured the book to build a deep understanding:
PART I: THE AUTOMATON. We start with the foundation – finite automata. It may sound intimidating, but it's key to really grasp how regex works. It might surprise you how intuitive it can be.
[2/n]
This book just got a fresh look and a new title—in preparation for a wider distribution. It's a labor of love, and differs from the usual regex resource. Why?
Unfortunately, many software developers find regexes to be hard to write and decipher.
[1/n]
A direction can be a goal beyond the immediate iteration, such as value for the customers’ customers or prioritizing between two positive outcomes.
Learn more about the Guiding Star framework in the book “Guiding Star OKRs”: pragprog.com/titles/snokr...
[4/4]
❓ This leads to a crucial question: Are OKRs about 🧭 direction or ✅ projects?
🌟 GUIDING STAR OKRs define a direction. Otherwise, OKRs simply duplicate what’s already in Roadmunk, Jira, or MS Project.
[3/4]
Tense: “next” implies the future, while “now” emphasizes the present.
Protagonist: “What happens" considers the broader context, whereas “What will I do” focuses on the task assignee.
Result: “happens” suggests an outcome, strategy, or direction, while “do” implies a specific task or project.
[2/4]
“What happens next?” differs from “What will I do now?” This fine print distinction from Seth Godin's new book “This is Strategy” highlights key differences like tense, protagonist, and result.
[1/4]
