When 'architecting' a system - aka planning how to build it, what components to put in place, what technologies to use - what are considerations you should take?
Here's an important one: capture the current business needs, and anticipate future ones:
Now that I no longer work there, I will say that something I really disliked about Google (and this may just be a Big Tech thing and not unique to them) is how much of the job was self promoting and the theatrics of demonstrating impact.
The weird thing about startups is one clear-headed systems thinker can produce more output than 100 unorganized people working very hard.
And not just in code.
One of the mentally healthiest things I've done is to assume positive intent — that people are good, they're trying their best, and they mean well.
I am rarely proven wrong.
Happy to announce that @AgaraLabs is being acquired by @coinbase . Looking forward to continue working with @segmenta and the Agara team. And to work again with old mentor @pankaj !
We’re excited to announce the acquisition of @AgaraLabs, an AI-powered support platform with operations in India and the US, to enhance our customer support with powerful machine learning technology.👇 https://t.co/cyKmZprJwZ
"Don’t do things that you know are morally wrong. Not because someone is watching, but because you are. Self-esteem is just the reputation that you have with yourself. You’ll always know." -
@naval