The practice of building software/technology is going through a phase shift. We’ve worked from abundance the past few years. Now we have to figure out which developments are worth keeping and make a dividend of that exploration. It’s not clear what job roles, kinds of software, practices, and benefits¹ will persevere.

We’re going to have to ask “what would you say it is you do around here?” of software development assumptions from the past few years. It’s unsettling², but some good corrections will come of it.

I’m betting that using writing as a lever will remain under-rated and under-used. Both for asynchronous/remote work and improving all kinds of thinking about building software.

Furthermore, Poker Face is excellent.

1. Sorry, nap pods and ping-pong tables. ↩
2. And, often executed cynically. ↩

Writing improves thoughts and ideas. Doubly so for thoughts and ideas about code.

Writing, about software or otherwise, is a process wherein:

1. thoughts and ideas are clarified
2. ideas are transferred to colleagues
3. culture (of a sort) is created by highlighting what’s essential and omitting what’s transient
   

Documenting code, as a form of writing, is a process wherein:

1. the concepts and mechanics in the code are clarified
2. what’s in our head today is made available to our teams (and ourselves) in the future
3. culture happens by highlighting what’s intended and what’s “off the beaten path” when working with this codebase
   

I suspect that open source is (often) of higher quality than bespoke, proprietary software because it has to go through the crucible of documentation. Essentially, there’s a whole other design activity you have to go through when publishing a library or framework that internal/bespoke software does not.

I can’t objectively verify this. Subjectively, when I have made the time to write words about a bit of code I wrote, it has resulted in improving the design of the code along the way. Or, I better understand how I might design the code in the future.

Writing is a great tool for designing code. Use it more often!

“Turn every page. Never assume anything. Turn every goddamned page.” — Robert Caro, Working

So goes the wisdom super-biographer Robert Caro received from a mentor when he was an investigative reporter in New York. Caro went on to apply this energy and depth to write a sprawling biography on real estate developer Robert Moses and four volumes on the life of LBJ.

I like the energy, determination, and purpose of Caro’s advice. In his writing, Caro takes a maximalist¹ perspective². He looks to understand the system. Caro read every original document in every archive he could find (“turning the pages”) to ensure he fully grasped the context of historical events and didn’t miss any details that might change the interpretation of events. Caro tries to load the whole state of his subject into his head and notes. Only then does he start writing his expansive biographies.

1. Read the code

Building software benefits from the same energy and determination displayed by Caro. As I’m working on a project, I flip between code I’m writing, code I’m using, and adjacent systems. Once I’ve read enough to have the problem and system in my head, I can move through the system and answer questions about it with that everything is at my fingertips feeling³. Fantastic.

Recommended: read third-party libraries, frameworks, standard/core/prelude libraries. Read demo code. Find inspiration, learn something new, and build the muscle for reading code with confidence.

2. Hear the words

When I’m really listening, avoiding the urge to think through what I’ll say next, I’m doing my best work as a coach or mentor. When I really hear and understand what a colleague is trying to accomplish or solve, it’s a bigger win for everyone.

Subsequently, I can switch to brainstorm or solution mode. Not before.

Recommended: literally listen to what they’re saying. Especially for the leaders and managers out there. Get the context needed to understand what they’re thinking. Ask clarifying questions until you’re sure they understand what they’re thinking. Don’t start responding until you’re sure you understand the context and the kind of response⁴ expected of you.

3. Build a model

Reading (words and code) and listening are great ways to build a mental model of how an organization, system, team, or project works. That said, a model is mostly predictions, not rules or hard-won truths.

To verify your model, you have to get hands-on at some point. A model is likely invalid unless it’s been applied hands-on to the system in question. Make a change, propose an updated process. See what happens, what breaks, who pushes back. Building (with code, with words) upon the model will evolve your understanding and predictions in ways that further reading or listening will not.

Recommended: turn reading words, reading code, and listening into a model of how your code-base, team, or organization work together. Apply that model to a problem you’re facing and use the results to improve your predictions on what actions will produce welcome outcomes. Rinse and repeat.

4. Go forth and deeply understand a system

With due credit to Robert Caro, I suggest doing more than “turning the pages”:

“Read the code. Read every damn function or module you’re curious about.” — me, a few months ago

“Listen to what they’re saying. Hear every damn word until they’re done talking.” — me, several weeks ago

Next time you think “I need more context here” or “that seems like magical code/thinking”, go deeper. Take 15 minutes to read the code, or listen 15 seconds longer to your conversation-mate.

Turn the pages. Read the code. Hear the words.

1. Aside from his biography quote above, all of his books are doorstoppers. ↩
2. Extensively aided, it should be noted, by further research and organization by his wife. ↩
3. Aka Fingerspitzengefühl ↩
4. e.g. commiserating, brainstorming, un-blocking, taking action, etc. ↩

Checking my emails frequently. Responding to a few group/direct-message chats at a time. Managing to write code, do math, or put together a slideshow/essay at the same time. Always in front of a computer.

That’s what productivity in my college years¹ looked like. There was lots of multitasking and goofing around online. A smidge of collaboration via nascent networks².

There is little coincidence that’s close to how I work today. Slack is a better IRC³, messaging apps work a lot like AIM⁴ and ICQ⁵ did back in the day. I try to focus more and multitask less, to the extent that circumstances and discipline allow.

What strikes me is, when my career started⁶, that’s not how we worked.

In the early 2000s, if I needed to talk to more-experienced developers or managers, I wrote an email or walked over to their office/cubicle⁷ to try and catch them for a quick chat. If I needed to talk to a more junior developer who was just out of college (like me), I sent them an instant message. I probably had Slashdot, IRC, or several blogs open in a minimized window somewhere.

Now, I’m the experienced developer/manager-type person, and the style of work matches a lot of my college habits. A lot of that is leadership determinism (i.e., I have the agency to set and model the structure of our work). Maybe some is down to measurable productivity improvements that, e.g., Slack bring. Most of it feels like it is down to the opportunity seized of remote work – you can’t work remotely without all the tools folks in my cohort started using as we were pivoting from students to professionals.

Today, “Extremely online” is a whole other thing that is unrelated to how I work professionally. But as a new generation becomes the largest in the workforce, probably that will change and things will look a little weird to me. So it goes!

1. 1998-2003. Most of those spent on a dual-everything Linux PC. I bought my first laptop/Mac in December 2002. ↩
2. Mostly, folks were Very Offline. Especially outside my generation, but even in my peer group. Now, we’re all Pretty Dang Online. ↩
3. For all but the neck-beard-est measurable axes. ↩
4. AOL Instant Messenger, the definitive software of my youth. ↩
5. Which required knowing your user ID to get people to add you as a friend. Thusly, I can still tell you my ID to this day: 11772935. ↩
6. Roughly 2000 is when I did my first productive programming for money. ↩
7. Thinking back, cubicles were not great or cool, but they did beat desks in an open layout on most axes. Larger pair cubicles with someone you like to collaborate with were pretty good, all things considered. ↩

We live in the most amazing time for ideas. They’re all over the place. It’s never been easier to share them, and indeed they are shared at a phenomenal pace¹.

It’s so easy to find ideas that it’s a little difficult to squeeze our ideas into the noise. Plenty of folks will tell you how to “build an audience”, but I want to make it personal.

Build an audience with yourself!

Make room for your thoughts to exist in your head despite all the noise that exists in our modern world.

1. Clear mornings

I’m a morning person. I do my best work early in the day. Look at my calendar, you’ll see this. One giant, defensive block to focus in the morning and get stuff done. Please — do not schedule me in the morning²!

However, I’ve come to think there’s more to a good morning than a clear schedule. Having a clear mind, with stillness and lack of lingering stressors, helps a lot! If I wake up with something bouncing around in my head, seize it or solve it. Write it down to think it through or solve tension³ my brain has dwelled on overnight.

Going deeper into a clear mind reveals the absence of others. A truly spectacular morning of creativity correlates to (almost) exclusively thinking my thoughts. My ideas in my head⁴ — great! Someone else’s idea, via social media, television, books; promising, but likely not as good.

2. Attention machines

Among books, television, podcast, radio, etc., ideas via social media are particularly hard to avoid. I have to put a lot of discipline/energy into “don’t open socials, chats, emails, news, etc.” before 11:30am lest another idea trample over my idea.

Modern social media has evolved, in form and function, to bypass the smart part of our brains and go straight for the emotional and often irrational part. It’s the upsetting and frustrating ideas that stick with me when I use social media. Rarely do I open my laptop, read social media for a few minutes until a good idea comes up, and then close the laptop to go think about it.

The doom-scroll demands more scroll.

The upside is, we may also live in a moment where the abundance of ideas surfaced by attention machines comes into balance as alternatives to hyper-scaled social networks come into play. I’m hopeful that to a smaller extent, Robin Sloan’s words on de-leveraging from Twitter will start to ring true as Twitter, in particular, fades from prominence:

The speed with which Twitter recedes in your mind will shock you. Like a demon from a folktale, the kind that only gains power when you invite it into your home, the platform melts like mist when that invitation is rescinded.

3. No retreat

The previous is not to imply that attention machines aren’t useful! I don’t want to Waldenpond or go full digital luddite. When I squint at it with optimism, some forms of social media look like a networked/distributed system attempting to reach a consensus⁵.

There are less intense attention machines that aren’t built around hyper-tuned engagement loops. Basically anything where I have a list of things to watch/read/enjoy is an attention machine: a Netflix watch list, YouTube subscriptions, Substack subscriptions, and the humble/old RSS reader. These don’t demand that I stay in a loop, thinking other people’s thoughts and consuming the surrounding ads. Which is useful because I want to get other people’s thoughts, but only on my terms.

I find that my thoughts are more interesting if I prime them with idea from specific authors via various primary sources, social networks and otherwise. It’s thrilling to discover new scenes, folks self-organizing into web-rings and networks and chats to think about or share the commonality and challenge of their work or hobby. Having that kind of energy bouncing around in my head tends to improve my ideas rather than dilute them like hyper-scaled social networks might.

Bottom line: keep using the web to find fascinating people and scenes, participate in a few of them.

4. Seize your thoughts

I return to A Precious Hour from Rands in Repose, a lot:

Each day I blocked off a precious hour to build something.

Every day. One hour. No matter what.

Every day? Yup. Including weekends.

An hour? Yup, 60 full minutes. More if I can afford it.

Doing what? The definition of “building a thing” is loose. All I know is that I get rid of my to-do list, I tuck the iPhone safely away, and if there is a door, I close it. Whether it’s an hour of Choose yourownadventure Wikipedia research, an intense writing session, or endlessly tinkering with the typography on the site, it’s an hour well spent.

Make the most of the mornings (afternoons, evenings, whenever it is for you). Work the thoughts I find compelling, not merely upsetting or prevalent. Share it with interesting people. That’s how an exciting life of thinking my own ideas happens⁶.

1. For better or worse! 😬🤷 ↩
2. This is as much a message to myself as anyone else. Too many times I’ve scheduled an appointment in the morning thinking “surely it will be fine this time” and surely enough current-me regrets the decisions of past-me. ↩
3. Usually: think it through by writing it down. ↩
4. What a concept! ↩
5. See also: Graph Minds. ↩
6. I think! ↩

Only Solve One New Problem At A Time, Ben Nadel:

The example he gives in the episode is “learning Golang”. Understanding how to use Golang was a new problem for the company. As such, in order to start integrating Golang into their work, they applied it in the context of an already-solved problem: sending emails. This way, Golang was the “one thing” they were solving—the email-sending logic already existed in Ruby; and, they just had to port it over to a new application server.

Good advice for any developer at any experience level¹!

The ability to focus on one concern at a time is possibly the mark of a senior developer. It takes experience to ignore other factors as noise. It takes time to learn how to avoid tripping on distractions/side-quests. Distinguishing useful, new information from distraction and noise is the mark of a focused senior developer.

The trick for juniors, is they’re always learning more than one thing at a time, often on accident. They want to build a feature, but it requires a new library, and it requires learning the library. They went to start up my development server, but then something weird happens with Unix. It’s the essential challenge of being a junior – they’re just getting started, so they’re always learning a couple of things at a time².

---

If I could be so bold as to add a corollary to the rule of “one new problem at a time”, I’d suggest that if it can’t be done incrementally, don’t do it. Over the last 6-years, feature flags have revolutionized the way that I work. And, a majority-stake in that change is the fact that everything I do is now built and integrated incrementally. Until you’ve worked this way, it’s hard to even articulate why this is so powerful. But, I literally can’t imagine building anything of any significance without an incremental path forward.

Working incrementally: absolutely, more people should do this. Even seniors. Especially myself!

Now, the tables can turn. I’ve observed juniors who are more adept at working incrementally than seniors. Because they’re tripping over other tasks all the time, the junior has to work in smaller increments to make progress.

Perversely, a senior who can see the whole feature/change in their head is sometimes tempted to push the whole thing through in one (large) change. Developers who have learned³ to avoid pitfalls and gotchas sometimes have to relearn how to work incrementally.

I speak from experience! Working incrementally is something I consciously have to work towards. Conjuring a masterpiece into existence in a fury of git pushes and one pristine pull request feels good. On net, a big bang of development is a detriment to my team. An early pull request, small tactical commits, and a write-up to describe why and how I got there are more useful to align the team and spread ideas.

Previously: one priority is like wind in the sails.

1. I’m looking a this sentence again, double checking it, and yes this is a global pronouncement about programming and developers and yes I think it carries its weight↩
2. Or even worse, accidentally learning things that aren’t relevant to what they’re trying to tackle. Sometime, ask me how excited I was about Tcl/Tk in 1998, arguably several years past the apex of that language/toolkit. ↩
3. Often through the luck/privilege of having lots of time to practice/tinker at programming outside the job! ↩

The Bird hit another inflection point on Friday. Now, many people, myself included, are looking at alternatives or actively decamping¹. It was quite a thing to experience.

Several days before, I read a post about the value one can potentially get out of Twitter. On one hand, it may not age well². Network-effects will cause Twitter to lose “value” faster than it loses daily/weekly/monthly active users. On the other hand, thinking about how I might get tremendous value out of the next network is a useful thought experiment.

Herein, allow me to riff on how to get a surprising amount of professional value out of publishing to and participating in Twitter-like³ social networks.

The value proposition is two-fold:

• the ability to publish into other folks’ attention streams (i.e., reputation building)
• a high-quality stream of information to adjust my own world view/model

---

On the publishing/write side: note that folks like Patrick, Simon, and Laura are Very Good at Twitter. They’ve been writing there for years, building a reputation. In particular, they form thoughts such that they travel and evolve well on Twitter in particular.

With a lot of practice, I could reach this level of operation. Building the reputation, of course, is about showing up consistently for months and years. A few months of rebuilding my Twitter routine and ‘practice’ and I’m out networking with the best.

In other words, use Twitter as a big professional networking tool⁴. Instead, the networking happens at the idea level. Contribute and participate in developing ideas and the network comes to you.

---

On the read side: I’m guessing anyone who enjoyed Twitter in 2022 and gets useful signal out of it is equipped with:

1. a well-curated list of mute-words⁵
2. bespoke user lists which focus the valuable discussion and reduce the din of a global social/information network
   

Throughout its history, Twitter was often adversarial. There’s a “main character” of the day. Many folks come solely to build them up or tear them down. Disagreeing parties come to dunk on each other. Occasionally, they directly engage, but social bubbles/fortifications are the norm.

Anyone who gets professional value out of Twitter ignores that aspect. 🤷🏻‍♂️ In particular, they are using Twitter itself (or well-considered 3rd party applications) to automate filtering out the noise⁶.

I’ve dabbled in setting up mute-words and curated, high-signal lists. It worked pretty well at various points in Twitter’s history, particularly in combination. Perversely, now that we’re possibly in the waning days of Twitter’s influence, I’ve got a pretty good setup for finding interesting, new-to-me ideas. Sometimes those ideas put my work, or even the world, in a better perspective. That’s valuable!

---

Bottom line: you get out of Twitter-like networks what you put into it. The better I write, work the network, choose your sources, and manage the flood of information, the more likely interesting/valuable things will come my way.

1. I feel like this happened at least twice before, probably circa 2015 and 2018? ↩
2. This started off as a thread that ended with this caveat: “Assuming that Twitter doesn’t drastically regress under New Management.” Reader, it did indeed regress. ↩
3. Tumblr, Mastodon, Micro.blog, Cohost, Fediverse, etc. ↩
4. Not in the way LinkedIn aims to do that around the resume. ↩
5. I started with this list, which is unfortunately paywalled now ↩
6. Mastodon in particular has community conventions around content warnings and requiring consent to see upsetting images or even posts about ongoing dramas. By social convention rather than software or regulation, this makes it a much better place for human brains to hang out. ↩