Making sense of Uber's Engineering
Uber's tech is mammoth. Studying and understanding it can prove quite helpful if you are venturing into building your own business or a product or even a new feature. Not because you should align with it from day one, but so that you never fall into the trap of building fancy, complex tech in the early stages.
Here’s how I have planned this part of the series:
We will start by understanding Uber's tech ecosystem
Next, delve into what you should (and should not be) building for your first product or feature
Finally, try to build an early version of an Uber-like app ourselves
In the first post, I would be covering point 1. Bear with me even if any of this seems a bit overwhelming, you will surely appreciate it once the journey is over.
To make things simpler, I have italicised terms throughout the post which should only be taken as examples and skimmed through (have also hyperlinked them as well though in case you are interested to read further on them).
At all points, I would like you to only focus on the larger picture and not get bogged down because of the details.
So, go right ahead, grab a snack or drink and get to reading the first post
Do drop me a line at hrishikesh@flexiple.com in case you would like to engage in a discussion over any of the points or would like me to elaborate on something.
You could also tweet to me @HrishikeshPard2 in case you would like everyone to benefit from the discussion. I am planning on sharing shorter snippets of content on Twitter, so, do keep in touch there as well