tushar

@TrisH0x2A Fr fr

i just love rust a lot but these compile times are testing my patience fr

@TrisH0x2A this sounds so fun!!! Will do on my own sometime this week!

malloc(size) takes a byte count and returns a pointer to a block of that size. that's it. one function. but to implement it you need to understand how the OS hands out memory, how to track free blocks, and how to inject your code into any binary without recompiling it. let's build it from scratch

@EFDevcon @Nitashaberry Would love to be a volunteer!

Devcon is built by the people who show up! Volunteering is one of the best ways to experience it from the inside. Thanks to @Nitashaberry for sharing her experience✨ Comment below for the waitlist link ✍️👇

finished the cache-friendly version of this!!! was very fun implementing it, took a couple of iterations to get it to work. onto benchmarking!

@zavxai buy a nice external keyboard lmao

Honestly, how can I prevent MacBook keyboard from becoming like this?

@0xlelouch_ The way i’ve tackled this is by breaking down tasks into small, “easy” steps and then just doing it one at a time.

It is hard to improve as a software engineer when your main coping strategy is distraction. I have seen a lot of engineers (including me) who say they want to get better at systems, debugging, cloud, observability, performance. But the moment things get a bit uncomfortable, they escape. Open YouTube. Jump to another course. Switch from Go to Rust to Python to Kubernetes. Read 20 threads. Watch 3 conference talks. Do everything except sit with the actual confusion. That is the trap. Real improvement needs sustained contact with what you do not understand yet. Take observability for example. Most people would say they “know” logging, metrics and tracing. But ask them to debug a real production slowdown and things start falling apart. API latency spikes. CPU looks normal. Error rate is low. Customers are still complaining. Now what? This is where distraction usually begins. You start reading random blogs on OpenTelemetry, Grafana, Jaeger, Prometheus, distributed tracing. Looks productive. Feels productive. But you are still avoiding the real work. The better way is more uncomfortable. Pick one small service. Add structured logs properly. Add request IDs. Add latency metrics. Add error counters. Add one trace through the critical path. Now send traffic. Break one dependency. Add retry. Watch what changes in logs, metrics and traces. Now you are learning observability for real. It's not only about consuming content. It's is essentially about being in contact with the part that is still weak. You will notice things like: - logs tell you what happened - metrics tell you where the pattern is - traces tell you where time went That one hands-on exercise will teach more than 50 “complete observability roadmap” posts. Most people are stuck because they have trained themselves to escape discomfort too fast. As a software engineer, your growth starts the day you stop using distraction as fake progress and start sitting with the messy part long enough to understand it. Thanks for reading!

@skivthecreator i gotta lock in on x too 😭😭

@tushj994 from other perspective, hell yeah

im so addicted to 𝕏 i close 𝕏 and the next thing i do is open 𝕏 again like wtfff 😭

@dansku_hk @Remitarded whats the mechanism for this? how does the absorption actually happen?

@Remitarded Aave token holders must absorb any loss of the protocol. READ the use of Aave token.

$Aave below $100 feels cheap Price is around previous bearmarket low but with ~4x TVL Confident it will bounce back stronger

@duttasomrattwt This is super cool!!

This time freeze effect is going viral, and it's super easy to make using Seedance 2.0 Check the reply for the prompt.

@juliusilg @ItsWillHenry A lot of people do believe in the Fat Model Thesis. What's your opinion on it?

@ItsWillHenry reverse roles if founder is building on the app layer, where the value accrues 💀

How VCs treat me after I tell them my company does “AI infrastructure”.

@ChShersh poetry

This is all me, and nobody does it like me

@AroraBhavyam what's he building damn.

Met someone yesterday who has 3 separate Claude accounts, all with max subscription, and he still hits the weekly limit within 3-4 days. 💀 Here's what his browser might look like…

@uttam_singhk defi brings more transparency and more independence to users. But this means that users have to be much more aware of the risks in everything they do. If we don't push this, then it's better for most users to just give their money to professional money managers.

I’m starting to understand why vitalik hates DeFi

@Steezehuman I have no strategy

People who get no engagement on 𝕏, what's your secret?

@_trish_xD making a simple system is much harder than making a complex system. That's where true engineering lies.

wise words from the best systems engineer I've worked with: "two things that make code actually maintainable: 1. reduce the layers a reader has to trace 2. reduce the state a reader has to hold in their head" applies to every codebase. always.

@uttam_singhk time to buy maybe? tough call.

IDK where we go from here. confidence in DeFi is at an all-time low right now scary af

@0xratnakar @hankypanty @innercircle_so @aiweekendsxyz damnnnnnnn

When I said WHYC is going to be fun, I meant it FR super excited to have @hankypanty joining us for the show. and i can promise you’re still not ready for this.

@AroraBhavyam yeah alot of my friends attended, none of them said that they liked it XD.

Honest opinion about the event: - All the talks felt like recordings, and we were not allowed to ask questions. - Most crowd were IIT & BITS students who just wanted free credits, not building anything and wanted a job. - Networking was worthwhile if you hit the right person. - Content team was crazy though @blockwee! - Pretty bad air ventilation, almost felt like a boiler room! Left within 3 hours of entering. 🫡