tiwariaditya15's profile picture. LLMs, Agents, GenAI @ Network18 | TS, Go, React, Python, Cloud | ex - @wellness_24X7 @invactHQ | 🏊‍♂️|🎾

Aditya Tiwari

@tiwariaditya15

LLMs, Agents, GenAI @ Network18 | TS, Go, React, Python, Cloud | ex - @wellness_24X7 @invactHQ | 🏊‍♂️|🎾

Wish I could write C++

Breakfast of a Senior SWE who writes C++

ChShersh's tweet image. Breakfast of a Senior SWE who writes C++
ChShersh's tweet image. Breakfast of a Senior SWE who writes C++


Aditya Tiwari 님이 재게시함

Most JavaScript developers switching to Go often ask "where's async/await?" and it reveals a fundamental misunderstanding of execution models. In JavaScript, async/await exists because V8 runs on a single OS thread with an event loop. Every syscall would block the entire process,…


Aditya Tiwari 님이 재게시함

I’ve been trying out few generative AI things, and I gotta this stuff is pretty rad. I feel like I was living under stone for all this time.


Aditya Tiwari 님이 재게시함

I really enjoy watching @RyanCarniato's streams. His ability to articulate very complex topics around reactivity and framework internals and distill them into examples that make a lot of sense is incredible. Kudos :)


Aditya Tiwari 님이 재게시함

If I had any wisdom to teach younger devs it would be this: 1. Program against, consider, and handle the error path first and foremost. Include useful logging, telemetry, and error messages. 2. Utilize your type system, whatever that may be, to make as many invalid states…


It's been 2 months since I joined @moneycontrolcom. Fortunately, I got to work on one of the critical events (budget 2024) for them. I experienced firsthand how different pieces are orchestrated at scale. Looking forward to shipping good UXs for our users.


Aditya Tiwari 님이 재게시함

If you care about security for your NextJS app, stop using top level "use server" - it's way too easy to leak data Top level "use server" creates endpoints for all exported functions, even if they are never used on the client One accidental export can cause a ton of damage

RhysSullivan's tweet image. If you care about security for your NextJS app, stop using top level "use server"  - it's way too easy to leak data

Top level "use server" creates endpoints for all exported functions, even if they are never used on the client

One accidental export can cause a ton of damage

A/B Testing at Scale: How We Engineered a Solution for Millions of Users with AWS by @fireblaze_15. rahulsuresh.net/blog/ab-testin…


Aditya Tiwari 님이 재게시함

we read about how blob stores (S3) can be a universal infrastructure backend, and discussed how this approach helps reduce cost upfront for startups, how S3's durability / reliability enable us all, and also some of the caveats of this approach. (linked below)

shrirambalaji's tweet image. we read about how blob stores (S3) can be a universal infrastructure backend, and discussed  how this approach helps reduce cost upfront for startups, how S3's durability / reliability enable us all, and also some of the caveats of this approach.

(linked below)

This week we read about SysCalls. I learned what syscalls are, how a userland code calls funcs in kernel, and what roles registers like RAX, MSR_LSTAR play in syscalls,etc. The article was dense(for me) but Shriram broke down code/drew diagrams which helped me understand better.

in this week's orbital weekly, we learnt about the "Anatomy of a system call" in linux by @dmd_lurklurk. Despite not being very proficient at C (as much as I want to be) we got a cursory understanding of sys calls - specifically `sys_read()` in x86_64 systems. Uploaded it to…

shrirambalaji's tweet image. in this week's orbital weekly, we learnt about the "Anatomy of a system call" in linux by @dmd_lurklurk. 

Despite not being very proficient at C (as much as I want to be) we got a cursory understanding of sys calls - specifically `sys_read()` in x86_64 systems.

Uploaded it to…


Loading...

Something went wrong.


Something went wrong.