Thing I learned at Stripe: make an extra special effort to make sure your internal tooling is compulsively composable, like unix commands.
-
-
Replying to @patio11
This lets users of the system invent new use cases for it much, much faster than you can just write new features into the system.
1 reply 4 retweets 15 likes -
Replying to @patio11
Let's see, how would I analogize this to something almost every software company has on hand... OK, consider your admin dashboard.
1 reply 2 retweets 6 likes -
Replying to @patio11
You might do the first N features for your admin dashboard by just implementing them in Ruby or whatever in that codebase.
1 reply 2 retweets 9 likes -
Replying to @patio11
Now consider any other tool you have like, I don't know, some sort of pub/sub system like NSQ or Kafka whatever you like.
1 reply 2 retweets 6 likes -
Replying to @patio11
Your admin gets a *lot* more useful the nanosecond it can interact with the pub/sub system, in ways you won't appreciate for a while.
2 replies 2 retweets 7 likes -
Replying to @patio11
And you probably have some way to make a message go to an arbitrary email address. Make sure that also interacts with the pub/sub system.
1 reply 2 retweets 8 likes -
Replying to @patio11
And now suddenly, without explicit coordination at either end, your admin speaks email. (Which is a somewhat contrived, toy example.)
2 replies 2 retweets 8 likes
I am occasionally awed by what non-engineer colleagues manage to coax out of a set of web interfaces that don't "know about" each other.
-
-
Replying to @patio11
In my previous life, I relied on "I'll just build a page in admin for that", and got huge mileage out of it, but O(N^2) a beautiful thing.
0 replies 2 retweets 12 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.