Tirthraj Mahajan

221 posts

Tirthraj Mahajan banner
Tirthraj Mahajan

Tirthraj Mahajan

@TirthrajM007

I rant about things and code sometimes

Pune, India Katılım Kasım 2022
142 Takip Edilen46 Takipçiler
Kedar Vartak
Kedar Vartak@kdrvrtk·
Rendering md files for docs has been a hassle for so long. Shitty web based editors, Very bad export to pdf experience and no shareable links at all Don’t get me started on No AI capabilities in these online md editors Is someone else facing this same issue?
English
2
0
5
309
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
At MTW 26. Majority of all presentations are about voice agents (multi-language)
English
2
0
2
129
Kedar Vartak
Kedar Vartak@kdrvrtk·
Mere company me sirf Ui Ux karne ka reh gaya hu baki sab domains me to haat mar hi liya hai
Indonesia
1
0
2
148
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
I wrote a blog on DynamoDB internals - @tirthraj2004/dynamodb-internals-9e841b257704" target="_blank" rel="nofollow noopener">medium.com/@tirthraj2004/… Go check it out if you are interested!
English
0
0
3
54
Tirthraj Mahajan retweetledi
AJ
AJ@ClearwaterCoder·
The Minecraft to Computer Science pipeline needs to be studied
English
50
246
3.4K
103.5K
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
AI made developers faster. It did not magically make them senior. I wrote about: - why output is becoming commoditized, - why judgment matters more than ever, - and what actually creates engineering depth in the AI era. Go check it out - @tirthraj2004/ai-made-you-faster-it-didnt-make-you-senior-ca0c2ce66f3b" target="_blank" rel="nofollow noopener">medium.com/@tirthraj2004/…
English
1
0
3
54
Tirthraj Mahajan retweetledi
mitsuri
mitsuri@0xmitsurii·
Why C++ still wins in finance.
English
21
202
1.9K
94.7K
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
One of the best videos I've seen recently. Definitely worth a watch!
Tirthraj Mahajan tweet media
English
0
0
0
51
Tirthraj Mahajan retweetledi
JNS
JNS@_devJNS·
ZXX
28
192
3.8K
108.9K
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
Abstractions are important, they save time. But often, treating something as a complete blackbox doesn't help you grow more.
English
0
0
0
29
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
I didn't know how Python works underneath the hood and how GIL works. I implemented a basic version of it from scratch.
English
1
0
0
37
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
The best way to demystify things if to implement the goddamn thing itself. While it is not the "recommended" approach, I have always done this and it's always almost worked in my favor You don't have to implement it entirely, but it should fundamentally do the same thing
English
1
0
1
59
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
When the data model encodes the domain (like normalized SQL), bottom-up understanding works well. When the data model is optimized for access patterns (like DynamoDB), top-down understanding via APIs is more effective
English
1
0
0
60
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
As per my observation - Start with APIs (what does the system expose?) Peek into DB (how is it stored?) Map flows (how data moves) Then loop: API <-> DB <-> business logic
English
1
0
0
56
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
This is not really a hard and fast rule, though. The deeper principle is - Start from wherever the system’s 'design truth' lives. Some SQL systems (modern microservices) are API-first, and some NoSQL systems have implicit structure buried in data
English
1
0
0
49
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
However, having now worked with DynamoDB-based systems, their structure is optimized for access patterns, not relationships. If you start with the database schema, you'll misunderstand why the data is shaped the way it is. This is where top-down is more effective.
English
1
0
1
51
Tirthraj Mahajan
Tirthraj Mahajan@TirthrajM007·
I have always worked with systems that use SQL as their underlying DB. Naturally, I go bottom up, looking at the database schema first, and then APIs, and then business logic. This is because traditional systems were designed database-first
English
1
0
1
48