Society has no mechanism for recycling the experience of founders of failed startups.
Sad to see friends who have worked for up to 3 yrs at their now failed startup, getting into a regular job where they never to get share or apply experience gained from failure.
I got promoted to Staff Engineer last year (my 3rd promotion at Google in 4 yrs) and I'm thinking of doing a Twitter Space/AMA to share some of the things I learned re navigating a career in tech. Trying to gauge if this is something folk might be interested in. Pls rt for reach.
Thanks to everyone who joined the AMA. As promised here's a
@lifeatgoogle
recording I did months back on interviewing and working as a Senior Software Engineer at Google:
I hit the 5 yr mark at Google today, it's been an absolutely amazing ride and I strongly believe there's still a lot of potential to unlock (think googol == 1.0 × 10^100).
Ok, there's interest. I've asked my friend and colleague
@_alternatewolf
(an excellent moderator) to help with moderating a Twitter Space for an AMA sometime next week. We'll share details tomorrow. Thanks everyone!
Ended the talk a few minutes ago. Feedback was generally positive except it was quite intense: syscalls, public key encryption, port forwarding, agent forwarding etc. all within 2 hrs 🥲
Thanks to the organisers and everyone who attended 💪🏽
Hi everyone, we're excited to announce our next conversation: SSH Internals with Moses Koledoye (
@MoVonLagos
) on Sun, April 16th, 2023, at 6pm GMT.
Moses is a Senior SRE at Google that has worked extensively on distributed systems, particularly with SSH.
One of the things I enjoy most about working at Google is the unique class of problems one encounters, problems software will never run into if it isn’t serving billions of users.
My kid brother asked me how to become good at writing. My reply was to read a lot of good writing and to write a lot. Like most things, it takes practice.
For a start, I've asked him to go read all of Paul Graham's essays:
Now taking questions ahead of this Saturday's AMA to better prepare with thoughtful and relatable answers, and to get quality conversations from the overall session.
Ahead of the upcoming AMA with
@MoVonLagos
, we'd like to compile some questions from attendees.
Please add your questions here: . You can also upvote existing questions -- questions with more votes will have a higher priority.
Art is the climax of human ingenuity and code at its finest form tramsutes into art.
Here's Linus Torvalds' linked list argument for good taste. Artsy!
Relatable. Too many years working on a specialized/niche area that you become the (number one) expert but become comically out of tune with everything else. "How to re-integrate with society after a PhD" could be a best-seller.
SRE is a via negativa approach to software engineering. We prefer derisking to over-engineering to achieve reliability. Instead of spending countless hours trying to make a service 99.9995% reliable, we spend time removing risks that can burn the miniscule 0.0005% error budget.
What are the best books you've read as an engineering manager or software engineer this year?
Books that taught you something new related to your job, provided inspiration, ideas.
We had a revolutionary idea to Make suits for the boys and dresses for the girls(Inspired by The queen’s gambit) to tell a new narrative of children in the slums that is not just one of poverty, but an image of what is possible if they’re given equal opportunities to excel.
Imagine yourself as a 10yr old kid from a remote place in Florida watch SpaceX launch rockets and recollect them for reuse on a steady. Imagine what that does to the boundaries of your realm of possibility.
One of the peak moments in which I had felt truly proud to be Nigerian was the launch of the NigeriaSat-1 satellite. Atypical Saturday morning in 2003, live launch on NTA, heart heaving with expectation, I had begun to nourish a deep belief we were on a course for great things.
I’ll be hosting an AMA with my friend
@MoVonLagos
next Saturday by 6 pm WAT (via
@sysdsgn
).
Moses is a Staff Engineer at Google who has been promoted 3 times in 4 years — an incredible feat, given the commonly accepted rate.
That job posting was just objectively wrong on many grounds. The more reason why stronger labor laws are required in Nigeria to protect against such predatory and discriminatory job postings and/or workplaces.
There's a further math kerfuffle doing the rounds and I feel compelled to say folk should not be made to think math is yet another subject. Like language, there are things in the universe that are currently best understood through math.
One of the biggest costs economic immigrants pay is living away from parents in their last and probably most crucial years. Technology helps with maintaining contact, but it's only an approximation of shared presence.
For landing impact in an org where process and ambiguity are rife (read Big Tech), I find “speculative execution” invaluable. As long as the cost of throwing away work stays marginal, I’d pick this over idling while planning-to-make-a-plan on how to execute.
Google, OpenAI, Meta, Mistral all dropping banger AI updates this week.
Me: still trying to get through the arxiv papers for the updates from last December.
All valid points. A bit latent are how being on a high-impact, high-visibility project + an excellent manager are career tailwinds that make the cost of reaching staff less prohibitive. Speaking from personal experience.
Pick your project(s) and your manager(s), if you can.
Why most engineers don't make it to Staff:
They have the wrong behaviors and mindsets.
I went from Junior to Staff in 3 years largely because of the way I worked.
3 behaviors that helped me (feel free to copy):
If you're coding only for the paycheck, you're in it for the wrong reasons. Passion is what drives innovation.
Code because you love it, because it challenges you, because it excites you. Then, success will follow.
Growing up in sub-urban Nigeria, I remember going to cyber cafes in the early 2000s to google stuff for my science projects. Google to me was more than just a search engine, it was a portal to endless knowledge.
Happy 25 to my real G.
I went from academic research in distributed robotic systems to SRE work in distributed systems.
There, Steve Jobs, I'm gradually connecting all the dots.
After months of interviewing, the final stage, onsite in SF, had 6 interviews on one day. Lunch/1:1 with the CEO was the climax and was quite memorable.
Eventual offer was conditioned on getting a US work visa which never came through. Deep deep sadness at the time.
People often measure themselves by what they see from others around them and never truly know what limits they're capable of beyond a made-up yardstick.
I don’t know which is more prestigious:
Winning a perf optimisation award for rewriting a (C++) batch pipeline.
Or
Being nominated as one of the top meme creators (internal) at Google for yr 2020.
Black Tax goes in the budget like every other expense. And given the nature of one-off requests and never ending emergencies, it requires discipline and honesty to keep within said budget and to say no before it becomes overbearing. That or financial self-immolation.
🛠 Building the Responsible AI Toolkit.
Today at
#GoogleIO
, we announced a new dataset exploration tool, Know Your Data! Learn how to integrate Responsible AI practices into your ML workflow in this session with
@LudovicPeran
and
@catherina_xu
.
Watch →
There's a Dublin in California and folk in SF just undermine my 12hr travel because they think I'm from around when I say I'm visiting from Dublin, lol.
It's 2049, a new Are-Ona-Kankanfo emerges in Yoruba land and the title's leading word "Are" is inaugurally expanded to AI Reliability Engineer, thereby embracing the zeitgeist of the times.
The fact that Stripe processed 1 TRILLION dollars in payments and posted a profit of $100M is one of the most disturbing business facts I've heard in a while.
Twitter/X can help with metacognition but too much of it, and it does start to feel like intellectual scavenging. And naturally, a lot of the hardwork actually happens offline.
@OlacodedM
Good thread. My general advice is to be decidedly clear about what and whatnot is negotiable. I took an entry level role at Google after my PhD partly because the recruiter did not realize I had a PhD and I felt too exhausted to take more interviews to be leveled up at the time.
Curse of knowledge/expertise.
I usually try to find real world scenarios that map to the concept I’m trying to explain. It gets harder if I can’t find one.
The engineering strategy doc is the principal engineer's manifesto.
That strategy doc is how they get their hundreds to thousands of engineers marching in the same direction.
Having another engineer who listens (regarding project woes, small wins, team/org dynamics etc.) is generally good for your sanity as a software engineer.
I like to call it core-dump buddy.
Disruptive companies are hard to build because having super smart folk by itself is not sufficient, the same folk also need to believe (to a much higher degree) in the mission of the co. enough to take full ownership of whatever is in their sphere of influence and then some.
If academic paper reviews can be like code reviews where some reviews are just a rubber stamp; no-op for author(s). As against reviewers almost always needing to suggest something for "improving" a paper.
To be honest, I miss the thrill of writing and publishing academic papers: the whoosh of passing deadlines, LaTeX, reviewers pontificating over something you’d considered irrelevant etc.
I miss it all.
Activation energy is a property that applies reasonably well to cities. Some cities leave you feeling lethargic or underwhelmed too often i.e. high activation energy, requiring mental footwork to get basic stuff done (because bureaucracy, weather or just local culture).
Towards elections, Nigerian politicians always apply the peak-end rule — hand out meager incentives to undermine the gruesome experience voters have endured in the last 4 years.
2009 - Started toying with programmable computers during my third year of elect/elect engineering, FUTA, Nigeria.
2019 - Finished a CS PhD. Started work
@Google
~2 weeks after final submission. Living in fourth country.
The year is 2009. 10 years ago.
What were you up to?
Looking back, did you know you will be where you are right now?
A lot can happen in 10 years, heck, even in 3 years!
Those years harboured ambition. The talk of the day was not merely putting food on tables, Nigeria entertained and pursued grander plans. Quite disheartening to see how it's all gone downhill.