Understanding what you should (and should not) be building
I know it's been long since I wrote the first post onย Uber's engineeringย and I heard back from quite a few people asking me when the next part would be published. There's always the 'busy with work' excuse but nothing explains such a long delayย ๐.
So, here are a few commitments from my end on this -
Theย second post is now liveย (of course, otherwise you would kill me for spamming you without any content ๐ค). Also, the third post in this short series on Uber would be live next Friday ๐
I would be publishing new posts every two weeks and you should see one mail from me every fortnight.
Now that is in order, let's quickly talk about the second post. This is a crucial connector in making the point around what (product) should you be building and when. Just because we understand how complex tech systems comprise of or how they are built, shouldn't push us to build such systems when not needed.
Have a read and drop me a line on what you think about this. I have made a conscious effort across the posts to share my learnings, experiences & opinions and not be preachy in any way. Do let me know if I have done a good job with this ๐
Until next Friday!
Cheers,
Hrishikesh