Back in 2018, when I first wrote about sizing engineering teams, I was surprised how much my advice rankled a colleague. He wanted to spin up a new engineering team of two people, which I thought was a bad idea. It would be a fragile team that would fall apart quickly if it didn’t grow. It would be missing the components we’d seen make other teams successful, like an engaged manager or ability to handle on-call if someone took a vacation.
CIA Chief: We'll Spy on You Through Your Dishwasher
It's great that you've got so much new household hardware connected to the internet. Especially for the CIA, whose director wants to spy on you through it.
Simply cutting your cloud costs may not be a good long-term strategy. It can lead to a decline in quality, limit your ability to scale, and stifle innovation. The real question you should be asking is how cost-efficient your infrastructure is.
Photo by Kenny Eliason on Unsplash Earlier today, I read something that led to the question” do we even need to organize the blogs in the reverse chronological stream? Ben Werdmuller, frustra…
Good API trends can linger on for some time, but as with the decline of monolith, many love to anticipate the death of microservices through strangulation by its own distributed weight. While event-driven, circuit-breakers, GraphQL, and other leading patterns will continue to help us orchestrate successfully across this chaos, there are some other elements of our API operations that will be shaping what the API landscape looks like in the coming years.
Remembering How I Built API Evangelist As I Rebuild My Social Presence
As I work to rebuild my social presence via Mastodon, I am reminded of how I built API Evangelist using Twitter and my blogs between 2010 and 2020. I am very invested in API platforms these days, and API blah blah blah that will attract the attention of enterprise organizations. So I tend to tell stories about things like API collaboration, automation, and governance, and things that API producers care about. As I do the work each week to slowly build my Mastodon community for my API Evangelist presence, I am reminded that most people do not care about the producer side of things, and what really matters to business and technical readers is always about consuming APIs. Telling stories about using APIs is how I built API Evangelist in the early days, and it is how I’ll rebuild my social presence in the Fediverse.
The future of fashion may be in AI disguises. While these flashy peices envoke a flair of the 90’s the inspiration is actually anonymity. Would you rather be perceived as a giraffe or a zebra…
This is a short story about metadata (I have to assume at this point you can read). About why a data file or dataset on its own is inadequate for analysis or research, and therefore insufficient to draw conclusive evidence or make informed decisions. Why you should never publish data or make it available through an API without its documentation. And, being mindful that computer applications are the immediate data consumers, emphasize the importance of machine actionable metadata. Here is an example, amongst many, I like to use to illustrate these issues.
I’ve been fascinated by the way we set type since I did my first packaging forty years ago. It’s a combination of tech, art, systems, culture and most of all, deciding to put in the eff…
