What if someone asked you to design a new API description format like OpenAPI? What would you include? What would you take away? What would you do differently? What would your focus be? As I’ve been thinking about complexity in API design, I had the thought that it might be an interesting exercise to come up with an API description format that aggressively limits complexity in API designs. How would I do this?
I’m coming down this week after a book release last Thursday. I didn’t realize how much different a book would be than a blog post. I know they’re different—obviously—but finalizing a PDF that people would download had a new level of finality to it. Lots of times with blog posts I fix things after I publish them. That’s not possible with a PDF. Once you put it out there, it’s out there.
All the way back in 2002, Martin Fowler talked about what he called Design Decay. He says: If you have a notion of planned design, that the design is something that’s right at the beginning, then it’s kind of inevitable that the design will decay. I like this concept of design decay. While I don’t think a design ever perfectly captures the essence of its subject, I think the design does lose its relevancy and accuracy over time.
It’s already October? This last part of the year always flies by for me. It’s so busy with holidays and birthday. I do love Fall weather, though, which we’re getting a glimpse of now. I didn’t write a weeknote for last week. I was too busy! First, I released my book API by Design. I’ve been researching the topic for several months and writing the content for a couple of them.
This week I opened up preordering for my book API by Design. This has dominated my time outside my normal working hours. I’ve had a lot of fun writing it. It’s been enjoyable taking ideas I’d been working on for a long time and trying to package them up to share with others. This takes a lot of time and work. And help from others. I’ve enjoyed this ebook format for writing.
I’ve been writing a lot these past few weeks. I’m excited to say I finished the first draft of a book I’ve been working on. It’s a shorter one, but I wanted it to be short. I hope to have a pre-order up soon for it along with more information on what it’s about. It’s about dealing with complexity in API design. On writing and editing I’ve been using my Remarkable 2 for writing.
I’m experimenting with an idea. I bought a Mac Mini M1 early this year, but I’ve wanted to have something I could use away from my desk. I considered getting a new Mac laptop to replace my 2014 one that’s in need of a new battery. I also considered getting an iPad with a keyboard. But I decided to try out a Chromebook. There are lots of things I’m not thrilled about with a Chromebook.
This is my sixth weeknote in a row that I’ve published without publishing a regular post. I’m OK with it. I’m writing a lot, personally and for work, so I’m keeping the habits, just not on here. I’m fortunate to be working with companies right now that put a high value on writing and ask me to spend a big part of my time doing it for them. Consuming too much I read a tweet recently that got me thinking about the amount of content I consume in a week.
This was a quieter week compared to the last few. I did a lot of personal writing and writing for work. The driving range where I hit golf balls has been closed, so that’s been a bummer. On communication I struggle in my work life finding ways to express myself. I’ve experienced that a lot these past few weeks. My issue is that I use weak language to share my ideas and opinions.