Jaffrey

Software Engineer - II @deepsourcehq
@iiit_hyderabad '24

Interested in Databases, Compilers and mostly anything involving systems.

Stay Curious!

[Joe Ingeno @JoeIngeno]

How to Write an Effective Software Design Document https://t.co/I1PxiKf4j5

[Vivek Galatage @vivekgalatage]

The Path of a Packet Through the Linux Kernel

https://t.co/SZKFetlj8M

[Kautuk | Conscious Engines @Kautukkundan]

Wanted to do this since a very long time

Introducing - Bangalore Paper Club
A series of offline research gatherings, under The Research Room India.

We're hosting the first edition this Thursday at Araku Indiranagar. Come over! and bring people with you.
---

Obviously inspired by the YC Paper club, the idea is to meet researchers in real life, present papers, discuss interesting problem statements and work together on some of them. We'll be doing presentations, recording them and putting them on YouTube.

I started "The Research Room India" community a while ago and it hit 500+ members recently. It's nice to see people interacting with each other over deep tech, taking feedback and also providing commentary to others. I met some really smart people through that, some of them joined my team at Conscious Engines as well.

It was natural that we had to take the next step which is to bring such people together offline.

Research as a topic is usually perceived as boring, too technical or nerdy. It may not be fully true.
The idea is to add a little bit of glamour to research so atleast more people pick it up and find it interesting, hosting it Araku, one of the hottest venues in Bangalore is a step towards that direction haha.

Link to the Luma event in the comment

[Vivek Galatage @vivekgalatage]

Knowledge Graphs over Two Decades by Xia Luna Dong

https://t.co/VeRO5UDOPi

[BangPypers @__bangpypers__]

We started a new segment called "Papers n Pip" over @discord & here's E1
Join us onto the next one onwards and come present your work or any interesting paper you might've come across lets discuss with community
https://t.co/F24Lw4yHc3

[Vivek Galatage @vivekgalatage]

It's all in the name!

https://t.co/NbrZpHwwWn

[Jaffrey @jaffreyjoy]

@trashh_dev ragebaiter lvl 100 😭🤣

[Jaffrey @jaffreyjoy]

@trashh_dev @binfohazard lol ur the best 🤣

[Alex Kuleshov @0xAX]

Nice reading about performance optimization - How 4 bytes of padding make array clearing 49% faster - https://t.co/yglULDRTCM

[Vivek Galatage @vivekgalatage]

Awesome breakdown @brotzky

https://t.co/hA3Uf7yM7a

[Bilgin Ibryam @bibryam]

Why is DuckDB Fast? 🦆💨 🚗
https://t.co/wGMeQg3r6U

[Jaynit @jaynitx]

Marc Andreessen went on Chris Williamson's podcast and broke down exactly how Elon Musk runs multiple companies at once

No other CEO on Earth does this:

1. Every week, Musk shows up at each of his companies, identifies the single biggest problem that company is having that week, and fixes it. Then he does that for 52 weeks in a row. At the end of the year, each company has solved its 52 biggest problems. Meanwhile, most large companies are still having the planning meeting for the pre-planning meeting for the board presentation with the compliance review and the legal review attached.

2. This is not a new operating method. It is actually how the great industrialists of the late 1800s and early 1900s ran their companies. Henry Ford, Andrew Carnegie, Thomas Watson, who built IBM. Total devotion from the leader to fully and deeply understand what the company does, be in the trenches, talk directly to the people doing the work, and be the lead problem solver in the organization. Andreessen says he is not aware of another current CEO who operates this way.

3. The framework Musk uses is the bottleneck. In any manufacturing chain, there is always one thing holding everything up. Sometimes it is raw materials at the start. Sometimes it is warehousing at the end. Sometimes it is in the middle. The job is to find it and remove it. Musk has universalized this concept across every company he runs. In any given week, there is one main bottleneck. He micromanages the solution to that one thing and delegates almost everything else.

4. Musk delegates almost everything. Andreessen is clear about this. He is not involved in most of what his companies are doing. He is involved in the one thing that is the biggest problem right now. Once that is fixed, he moves to the next biggest problem. Everything else by definition, is running better than the bottleneck, so it does not need him.

5. When Musk identifies the bottleneck, he goes directly to the engineer who actually understands it. not the VP of engineering, not the director, not the manager. The individual contributor who has the actual technical knowledge. He sits in the room with that person and fixes the problem alongside them. He does not ask for a report to be reviewed in three weeks. he shows up at the keyboard or on the manufacturing line and works through it overnight if necessary.

6. This is why technical people who work for Musk say it was the best experience of their lives. Andreessen's framing: if you are stuck on a problem you cannot solve, Elon Musk is going to show up in his Gulfstream, sit with you in front of the keyboard, and help you figure it out. For an engineer who genuinely cares about the work, that is an almost incomprehensible level of support from the CEO of the company.

7. Business school teaches the opposite of this: management as a generic skill applicable to any industry. Soup company or a rocket company, the management principles are the same. process, balance sheet, meeting schedules, compliance, executive motivation, interpersonal conflict resolution. Andreessen says those skills are useful in many contexts. They just give you nothing; you need to do what Musk does. And Musk pushes as far as he can away from all of that so he can spend all of his time doing the things only he can do.

[P99CONF @P99CONF]

Curious how #Netflix performs large-scale system migrations with replay traffic testing, canary analysis, dual writes/reads, and with NO downtime? Get the inside perspective from Abhishek Pandey, Senior Software Engineer. https://t.co/m6t7dRAtLy

#ScyllaDB

[Vivek Galatage @vivekgalatage]

Learning the Linux Kernel with Tracing by Steven Rostedt (2018)

Steven introduces tracing using ftrace to explore the kernel. The session covers fundamental computer architecture, virtual memory, page tables & how programs interact with the kernel.

https://t.co/iyFMIAwb6Q

[Vivek Galatage @vivekgalatage]

The previous paper and talk focused on using SIMD (Single Instruction Multiple Data) to efficiently parse massive JSON files.

SIMD is a form of vectorization utilizing built-in capabilities of hardware for faster execution.

https://t.co/2kn3k1WZpA

Since both the posts resonated quite well, here is a solid high-level overview and a roadmap to understand the vectorization.

[Alex Kuleshov @0xAX]

Small update on the tiny VM with a built-in kernel debugger I posted about earlier.

Last time it could reach Linux setup code and fail beautifully. It still fails beautifully 😀

But already have some visualization

[Interlatent @interlatent]

Hardware is the bridge between AI and the physical world

Atoms and bits must work together to create future systems embedded with physical intelligence

We wrote a guide for those curious about the atoms.

[Vivek Galatage @vivekgalatage]

How to Write Shared Libraries - Ulrich Drepper

https://t.co/W8GtDzcvrN

[Mihalis Tsoukalos @mactsouk]

Excited to announce my new book: "Systems Programming with Zig"!!! Find more at https://t.co/cROopoqLiN - I will let you know when it becomes officially available.

[Vivek Galatage @vivekgalatage]

Amazing perspective, enjoyed the talk... Highly recommend it, folks!

https://t.co/5hpNmICGIw