Praneeth Patakota

16.5K posts

Praneeth Patakota banner
Praneeth Patakota

Praneeth Patakota

@praneethr86

Engineering Leader

India Katılım Aralık 2007
878 Takip Edilen747 Takipçiler
Praneeth Patakota
Praneeth Patakota@praneethr86·
Nico Hulkenberg made it to his first podium today after 239 race starts. The Hulk always had it in him. Amazed how long some drivers wait patiently for this moment. Endurance is key ! #f1
English
0
0
1
54
Praneeth Patakota
Praneeth Patakota@praneethr86·
Reading sci-fi keep me sane. Gonna start some Indian author sci-fi this week - The City Inside - by Samit Basu.
English
0
0
2
78
Praneeth Patakota
Praneeth Patakota@praneethr86·
Deep work has been a mountain for me to conquer in my career. I finally figured out that it requires a lot of mental clarity on priorities, a bit of meditation, and self interest to be consistent at deep work habits.
English
0
0
0
66
Praneeth Patakota
Praneeth Patakota@praneethr86·
The habit of questioning everything and learning every concept in-depth is absent in most careers. People tread on the periphery only to see if that’s enough to do their jobs. But those who dwell deep into technical details are the ones who are truly worth having in your team.
English
0
0
0
80
Praneeth Patakota
Praneeth Patakota@praneethr86·
@hnasr I am going through this course right now and the way you explain internals and other concepts is just truly epic ! @hnasr thanks for creating this content.
English
0
0
0
38
Hussein Nasser
Hussein Nasser@hnasr·
For a long time I built database applications without fully understanding how they worked. that left me helpless when encountering performance issues, racing conditions, bugs and even corruption. That was early in my career ~15 years ago. I finally resolved to truly understand the workings of database systems, ensuring I knew every query my app sends and how exactly it is executed by the DB, what truly happens at every step and the IO cost and overhead of the DB itself. I've condensed the core principles of database engineering I learned into a course for my own younger self, grounded in my personal experiences rather than theories. Check it out and use the limited discount coupon. People seem to like it, I hope you enjoy and find it useful. Get my fundamentals of database engineering course databases.win My other courses (with coupons) Fundamentals of Network Engineering network.husseinnasser.com Fundamentals of Backend Engineering backend.win Discovering Backend Bottlenecks performance.husseinnasser.com Introduction to NGINX nginx.husseinnasser.com Python on the Backend python.husseinnasser.com
Hussein Nasser tweet media
English
11
44
499
51.3K
Praneeth Patakota
Praneeth Patakota@praneethr86·
@dmwlff @Meta @reactjs Great read. Keeping things simple at the core of our investigation is important, and ensuring we do not overlook the importance of observability is paramount. Every time we fix an issue, the logging and monitoring should improve.
English
0
0
0
37
Adam Wolff
Adam Wolff@dmwlff·
I ended my time at @Meta as a director. But I started as an engineer on FB Chat. Everything about it was broken — we had to rewrite it. And while the effort to fix it is one the projects that led to @reactjs, the most important fix was far simpler... Here’s the full story: — I worked on Facebook Chat for several years, both on the front end and the infrastructure. Before the major effort to redo the UI, FB Chat was super broken and we had no idea why. We got tons of bug reports about Chat being broken every day, but we noticed an odd pattern in the data: the volume of reports didn’t match the volume of usage. It was time-shifted from the peaks we’d see in the US. We didn’t know what was wrong, but we knew the code was a mess. We set about rewriting both the front-end and the back-end in an effort to fix it. The front-end rewrite pulled in a whole team of amazing engineers and became one of the big threads that led to @reactjs In the public eye, we portrayed this project as the one that ultimately fixed Chat. And the way I’ve usually told it, fixing Facebook Chat and the birth of React are the same story. But no framework was going to fix the worst problem with Chat. — During the time we were working on the Chat rewrite, we were also replacing the original Erlang backend with one written in C++. This was probably a good move, but the problem wasn’t with Erlang either. Our initial spec for the new backend didn’t say much about observability, but it was an important feature, and the rewrite forced us to rebuild it. Little did we know this would lead us to the root cause of our problems… When we finally gained insight into our deliverability data, we were able to cut it by region. We noticed Chat was really popular in India. This was before WhatsApp, at a time when SMS wasn’t reliable. Eventually we pinpointed a region in India where one specific DNS provider was giving out the wrong IP addresses for our Chat servers. So when people went to use Chat, they would sometimes get a notification that they had a message, and then it would disappear. Or they’d send a message and it would get lost. All because they were connecting to the wrong IP address. That was it! None of the sexy new tech we were working on was going to solve that problem. Ever. — Instead, the solution was to build observability that allowed us to track end-to-end message delivery. In the end, we could start with a broad cut of our data by country or web browser, and then zoom all the way in to look at what happened to a specific message for a specific user. Once we pinpointed that the problem was with a DNS server, the matter was resolved with a quick phone call. I don’t know what they did, but I imagine it was something like turning it off and turning it on again. We sometimes talk about observability as if it’s enough to buy a product like Datadog and just look at the pretty graphs. Sure, that’s a start. But true observability is a feature that needs to be built— painstakingly, iteratively, by-definition starting with a shot in the dark. — These days, it has become fashionable to poo-poo the idea of being data-driven. People point out that measurement can distort the phenomenon that is being observed. They want to make processes “data-informed.” But this seems like silly backlash against the only rigorous standard in all of software engineering: That we hold ourselves to an objective standard. We measure how long things take, how many errors we encounter, how often a process successfully runs to completion. So here’s what this experience taught me about observability: When an issue happens in production, time-box the investigation. Sure, take a few hours to try and figure it out by looking in the logs and inspecting the code. But if you’re coming to the end of the day and you still don’t have a fix, then push a PR that adds logging. The first one may be just a guess, but it will begin a process that leads to the truth. And that is what we should all ultimately be striving for. — For more engineering tips and stories, follow me @dmwlff
Adam Wolff tweet media
English
113
588
4.1K
597.7K
Praneeth Patakota
Praneeth Patakota@praneethr86·
The Garnacho goal reminds everyone of Rooney's overhead kick, one for the posters for sure. But the best takeaway from the #EVEMUN match was the really impressive debut of @KobbeMainoo, here's hoping he will bring a change of luck.
English
1
0
3
130
Praneeth Patakota
Praneeth Patakota@praneethr86·
@pyconindia These folks were amazing and so courteous in picking us up and dropping us off at all the speaker venues. Thanks to them all and kudos to @pyconindia for this collaboration.
English
0
0
1
59
Avi
Avi@AviSchiffmann·
Thinking in Systems is the best book I’ve read all year. Feels like I gained 10 IQ points just by opening it. Having clarity over how the world works is essential for anyone trying to do anything worthwhile.
Avi tweet media
San Francisco, CA 🇺🇸 English
231
869
12.1K
3.1M
Praneeth Patakota
Praneeth Patakota@praneethr86·
Neymar heads to Saudi pro league too. Gotta start watching the league seriously now. Meanwhile Inter Miami CF have started a dream run under Messi’s leadership. Should I watch MLS too now ? What a weird football season this is going to be !
English
0
0
1
127
Praneeth Patakota
Praneeth Patakota@praneethr86·
Premier league is back in action !
English
0
0
0
57
Praneeth Patakota retweetledi
Josh
Josh@joshmanders·
NASA doesn't fuck around. Look at those function names.
Josh tweet media
English
86
806
8.7K
837.3K
Praneeth Patakota retweetledi
Uncle Bob Martin
Uncle Bob Martin@unclebobmartin·
You cannot fail a sprint. Sprints cannot fail. The purpose of a sprint is to produce management data. A sprint that delivers zero stories has produced very important and useful data for managers.
English
35
119
783
119.5K
Praneeth Patakota
Praneeth Patakota@praneethr86·
I love reading stories published in SciFi magazines. They carry so much imagination stuffed into a tiny story. Amazing ! Try reading one of the latest I loved : Cheaper to Replace by Marie Vibbert clarkesworldmagazine.com/vibbert_07_23/
English
0
0
0
31