Twitter | Search | |
Oliver Beattie
Head of Engineering , adventurer, full-time nerd. 🤓, ✈️, 🍸, 🏳️‍🌈
13,004
Tweets
568
Following
3,554
Followers
Tweets
Oliver Beattie Jul 20
"You know your designers did something horribly wrong when your customers need to be professionally certified in order to use a wiki."
Reply Retweet Like
Oliver Beattie Jul 20
Replying to @levi @Jonathan_Blow
I tried this game out after seeing your Tweet and now I am SO HOOKED on it. It's so frustrating, and so addictive. 💊
Reply Retweet Like
Oliver Beattie Jul 19
Replying to @filipecvarela
Reply Retweet Like
Oliver Beattie Jul 19
🤔 Inverse Conway's law: when an organisation of humans ends up being structured around the inflexible software it uses.
Reply Retweet Like
Oliver Beattie Jul 19
Replying to @levi
😭
Reply Retweet Like
Oliver Beattie Jul 19
Managing battery levels for all the various devices in one's life is an exasperating, never-ending task. 🔋😩 Science: save us.
Reply Retweet Like
Oliver Beattie Jul 18
Replying to @rebjx
I really enjoyed it 😍
Reply Retweet Like
Oliver Beattie Jul 18
Replying to @obeattie
A completely beside-the-point but mindblowing thing the book also taught me: in the 80s, bullet points were a weird novelty. 🤯
Reply Retweet Like
Oliver Beattie Jul 18
I just read "What Do You Care What Other People Think?" by Richard Feynman. Man, I think I would have really liked him.
Reply Retweet Like
Oliver Beattie Jul 17
App developers: when I click a link, please, PLEASE just open the system web browser. Stop with all the in-app web views that don’t have my cookies. 😑
Reply Retweet Like
Oliver Beattie Jul 13
Replying to @willpillar
1. Monzo Chat 💬 (fun because it’s really “close” to users and requires a bunch of new platform capabilities) 2. Machine learning 🤖 (fun because it’s maths)
Reply Retweet Like
Oliver Beattie Jul 13
There are few better feelings than to get really stuck into a new and complex problem from an unfamiliar domain. 🤓
Reply Retweet Like
Oliver Beattie Jul 11
Replying to @mikekelly85 @jonas
It was a huge investment in the early days and admittedly the costs outweighed the immediate benefits. Now we have >600 services and many independent teams making >100 deploys/day, the benefits are large and obvious.
Reply Retweet Like
Oliver Beattie Jul 11
Replying to @watbe
Ha. I actually recorded a video of this because I am so astonished that someone would willingly put this junk on their site. 🤯
Reply Retweet Like
Oliver Beattie Jul 11
Replying to @mikekelly85 @jonas
In practice not really; most changes simply add fields anyway. Removing a field is a two-step process: update callers, then remove the field from the proto, but given a rollout of even a single service isn't an atomic operation it's something we have to deal with anyway.
Reply Retweet Like
Oliver Beattie Jul 11
Replying to @jonas
On it ✍️
Reply Retweet Like
Oliver Beattie Jul 11
Replying to @mikekelly85 @jonas
Those are compiled Protocol Buffers. Our development practices mean they must be backwards-compatible by at least one service release.
Reply Retweet Like
Oliver Beattie Jul 10
Replying to @chrisdarby89
🕴
Reply Retweet Like
Oliver Beattie Jul 10
It’s just code. Code can be changed quickly and easily.
Reply Retweet Like
Oliver Beattie Jul 9
Replying to @evnsio @SlackHQ
Reply Retweet Like