peter royal (@osi) header
peter royal (@osi) profile picture

kiss the sun and walk on air /// making things happen @netflix /// @osi@hachyderm.io

Los Angeles, CA
Joined January 2007
Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)Photo by peter royal (@osi)
‼️ i wrote a book! 🎉 it was my pandemic project. i was approached at the end of 2020 by my would-be editor after presenting on the topic. i put together a proposal, and, well, here we are now with my words in print. fotap.org/~osi/book.html #eventsourcing #cqrs #graphql
9
5
40
6,895
while the cover speaks to some specific technologies, the vast majority of the book is implementation-agnostic. many common practices arise from paradigms that were established to work within past constraints.
1
1
728
our software is no longer bound by the same constraints as the past, and should be looking forward on how to build for the future. i’d love to know what you think. 🙏 fotap.org/~osi/book.html
1
2
596
peter royal retweeted
biggest software flex i've seen in a while: shakti.com/
3
2
3
Ha! I predicted this correctly! In years of discussions about microservices and how it helps solve the org problem, we never stopped to wonder if the (bloated) org *itself* is the problem. But now that CEOs are convinced companies are overstaffed and org charts need culling 😉
Part of today will be turning off the “microservices” bloatware. Less than 20% are actually needed for Twitter to work!
8
14
7
179
i’ve made a mastodon account for the future - @osi@hachyderm.io
2
💯💯 intellij helped me think of my code not as text, but an equation that can be manipulated. refactoring are the key to making these transformations.
This quoted post is unavailable.
6
excellent thread on building software. the approach is sound irrespective of where you work in the stack.
Replying to @mipsytipsy
The whole game is about delegating as much of the solution as possible to reusable blocks, while preserving enough flexibility to build something awesome, yet cognitively cheap to operate. Sounds simple, but it's amazingly difficult. 🙃
1
peter royal retweeted
Junior developers love magic. Senior developers hate magic. ...because they know it will eventually bite them in the ass. Learn to Keep It Simple and Stupid (KISS). #developer
1
6
2
17
peter royal retweeted
Hot take: if you need multiple large monitors to program with, you should consider writing smaller/simpler functions.
198
77
69
1,400
💯💯 in order to appreciate practices that help with quality and maintenance, you need to have maintained a quality system over time.
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
3
🔁🔁 💯💯 the feedback loops are key, all the way to production. i’ve also found that people need to experience them to truly understand.
This Post is from an account that no longer exists. Learn more
3
🤗 Hi friends! I’m speaking in the Just Culture track at @QConSF this year. I’d like to hear from engineering and operations folks about your experiences after incidents and outages. Please RT for reach 🙏 forms.gle/KhUrRPDjUcUX4eCG6
12
9
excellent rant. largely agreed about desktop vs web applications today. other concerns aside, it _is_ possible to use graphql subscriptions + react to create a real-time UI. one _does_ have to consider the entire stack, as he says.
1
1
the entire thread is excellent. application architectures matter in being able to deliver collaboration features.
Replying to @amaldorai
Multiplayer collaboration is the future of all applications, and Figma is by far the richest multiplayer collaborative app. This will go down as one of the smartest software acquisitions of all time, and if there are regrets they will be only Microsoft's, for not offering more.
One of the few things that I can be absolutely definitive about is the definition of a "Deployment Pipeline", because I defined it. So here is a short thread that answers the question “What is a Deployment Pipeline". 1/9
5
52
3
169
peter royal retweeted
I keep repeating this. Here is a quick list of suggestions on how to write good documentation: 1. Empathize with the person reading and trying to understand your code/api. This should be obvious but apparently isn't.
"Good code documents itself" is one of the most damaging takes in software engineering. Code itself won't tell you about the decisions and rationale behind it, nor about about higher-level structures and abstractions. All this needs elaboration in documentation.
2
3
1
6