MusicLM
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.
The Enshittification Lifecycle of Online Platforms
This piece by Cory Doctorow on TikTok's enshittification (also available at Wired) contains some of the best and simplest descript
What time is it on the Moon?
Satellite navigation systems for lunar settlements will require local atomic clocks. Scientists are working out what time they will keep.
It Doesn’t Matter How Much You Spend on AWS
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.
Alerting and how 50 lines of code changed how we do it.
Sometimes things go bad, that’s how it is. Regardless of how much effort we put into preventing it. And when they do, it’s crucial to be…
Rooms, voice, gestures, and why Apple HomePod hasn’t quite clicked for me
Posted on Thursday 26 Jan 2023. 1,423 words, 6 links. By Matt Webb.
Laurence Tratt: Distinguishing an Interpreter from a Compiler
When is software correct
With tests, we can prove that our software works correctly. But how do we define ‘correct’ in software testing?
Is “stream” as a design paradigm over?
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…
What Comes After Microservices?
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.
What Does a Prompt Engineer Do?
Is Prompt Engineering the Career of the Future?
LISP — Mecrisp Stellaris Unofficial 1.0 documentation
The Subtle Art of the Changelog | CommandBar Blog
Writing Code Without Plain Text Files
The Unison programming language doesn’t store code in files, but in a database. What is that like?
Platform Engineers: Developers Are Your Customers
How your platform fits into your organization's practices, needs and culture is what's going to make the platform engineering team valuable.
Functional Programming Is Great. But It Ain’t Magic
It’s not magic, folks. It’s just code.
Vibrant Knitwear Tricks Facial Recognition Cameras #WearableWednesday
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…
NYC Subway Payment Systems: Who Gets Left Out By Changing Technology?
The NYC subway system still struggles to build payment systems that work for everyone. And often, the tech often separates the haves and have-nots.
Can you read or write? A metadata story.
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.
Cloud Services Ranked: Build vs. Buy
The Database of the Future: Seven Key Principles
There are seven principal features DevOps and developer teams need to chart the development of next-generation databases.
Do Aftermarket Products Point to Design Failures? - Core77
The booming market for product solutions shows plenty of room for improvement
Culture, care and typography
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…
How Tesla’s design took it from innovator to dud
The electric vehicle boom is bad news for Tesla.
Humble Developers — The Unicorns of Software Development
Do humble developers exist?
One Technology That Makes Renewable Energy More Efficient
Time series data can provide insight into ways to make energy production and consumption more cost-effective and efficient.
Workflow Engine Paradigms
Blog