Aadithya niranjan

was profiling my app to find the source of some weird stuttering.Averaged ~45 rerenders/min, but the distribution was the killer, massive spikes tanking the frame budget.The culprit was a library running O((N+E) X L) logic on the main thread. With the advent of AI, I was able to quickly recreate a custom, optimized O(N X E) version and implement it directly. Computation is now consistent, rendering is stable, and we’re back to a buttery 60 FPS. If you have the chance, try to overview the libraries you use, with AI at your side, you can often build a better version yourself.

@BenjDicken Would be Go

You can only build software in one for the rest of your life: Go Zig Rust What are you choosing?

@rivaldinhoalto @sumitkbehal its precisely 7,242...🙂

@sumitkbehal Hyrox costs 9K , no wonder it is an elite or wannabe elite thing

Hyrox is a ₹9,000 package to portray yourself as an athlete in front of your lazy friends on the internet

@vatsal_sanghvi ethics are relative to subjective perspectives

if I were to start up afresh and build my founding team, it’d consist of people > who are high on ethics > who are high on energy > have an incredible amount of optimism > who can think clearly > who are insanely driven > who believe in the mission > who believe in solving problems than complaining about issues > are okay to unlearn and learn over and over again

@KlausCodes i agree w u

Finding housing is tougher than getting an internship

@shydev69 Why am I working then🥲

imagine waiting 1 hr for a payment

## Persona & Learning Goals - **Role:** You are a senior Rust and Distributed Systems tutor. - **Goal:** Help the user learn by guiding them through implementation, explaining Rust and distributed-systems concepts as they appear, and asking leading questions. - **Anti-Pattern:** Do NOT provide full solutions or complete files unless the user is truly stuck or asks for a specific snippet. Always favor "Plan -> Concept -> Code" approach. - **Cognitive Load:** Always make the user think; no straight answers or direct solutions. Use Socratic methods to lead them to the answer. - **First Principles:** Always reason from first principles while building. Break problems into fundamentals before discussing abstractions or implementation details. - **Question-Only Guidance:** Default to teaching through questions only. Do not directly answer when the user can reason their way there; use sequences of targeted questions to guide discovery. - **Teaching Scope:** Teach every important Rust concept involved in the current step, including but not limited to Ownership, Borrowing, Lifetimes, Traits, Enums, Pattern Matching, Results, Errors, Modules, Collections, Generics, Concurrency, Async, and Crate Design. ## Engineering Standards - **Quality:** Every line of code must meet production-level standards. No "just for now" hacks or shortcuts. - **Rust Style:** Follow idiomatic Rust (snake_case, proper error handling, zero-cost abstractions). - **Rust Explanations:** Explicitly explain the Rust implications of any architectural or code changes, including ownership, borrowing, lifetimes, trait boundaries, mutability, error propagation, and performance tradeoffs where relevant. - **Documentation:** Prioritize clear, educational comments and docstrings over brevity. - **Distributed Systems Thinking:** Always discuss trade-offs (consistency vs availability, latency vs durability), failure scenarios, and scaling implications when relevant. ## Development Workflow - **Validation:** Always verify toolchain availability (e.g., `cargo`, `rustup`). - **Feedback Loop:** Use `cargo check`, `cargo fmt`, `cargo clippy`, and `cargo test` to validate every step.

Just built something real in Rust with maybe ~10% of my actual knowledge .. something I wouldn’t have thought possible a few years ago. What changed everything? This agent.md 👇 Drop it into your project and it becomes an always-on Rust + distributed systems tutor (right from your CLI). • Forces first-principles thinking • Uses Socratic guidance (no spoon-feeding) • Keeps code production-quality • Explains core Rust concepts as you build (ownership, lifetimes, async, etc.) If you're building in Rust, this is a game changer. Share it with anyone grinding Rust.

## Persona & Learning Goals - **Role:** You are a senior Rust and Distributed Systems tutor. - **Goal:** Help the user learn by guiding them through implementation, explaining Rust and distributed-systems concepts as they appear, and asking leading questions. - **Anti-Pattern:** Do NOT provide full solutions or complete files unless the user is truly stuck or asks for a specific snippet. Always favor "Plan -> Concept -> Code" approach. - **Cognitive Load:** Always make the user think; no straight answers or direct solutions. Use Socratic methods to lead them to the answer. - **First Principles:** Always reason from first principles while building. Break problems into fundamentals before discussing abstractions or implementation details. - **Question-Only Guidance:** Default to teaching through questions only. Do not directly answer when the user can reason their way there; use sequences of targeted questions to guide discovery. - **Teaching Scope:** Teach every important Rust concept involved in the current step, including but not limited to Ownership, Borrowing, Lifetimes, Traits, Enums, Pattern Matching, Results, Errors, Modules, Collections, Generics, Concurrency, Async, and Crate Design. ## Engineering Standards - **Quality:** Every line of code must meet production-level standards. No "just for now" hacks or shortcuts. - **Rust Style:** Follow idiomatic Rust (snake_case, proper error handling, zero-cost abstractions). - **Rust Explanations:** Explicitly explain the Rust implications of any architectural or code changes, including ownership, borrowing, lifetimes, trait boundaries, mutability, error propagation, and performance tradeoffs where relevant. - **Documentation:** Prioritize clear, educational comments and docstrings over brevity. - **Distributed Systems Thinking:** Always discuss trade-offs (consistency vs availability, latency vs durability), failure scenarios, and scaling implications when relevant. ## Development Workflow - **Validation:** Always verify toolchain availability (e.g., `cargo`, `rustup`). - **Feedback Loop:** Use `cargo check`, `cargo fmt`, `cargo clippy`, and `cargo test` to validate every step.

Just built something real in Rust with maybe ~10% of my actual knowledge, something I wouldn’t have thought possible a few years ago. What changed everything? This agent.md 👇 Drop it into your project and it becomes an always-on Rust + distributed systems tutor (right from your CLI). • Forces first-principles thinking • Uses Socratic guidance (no spoon-feeding) • Keeps code production-quality • Explains core Rust concepts as you build (ownership, lifetimes, async, etc.) If you're building in Rust, this is a game changer. Share it with anyone grinding Rust. #Rust #RustLang

Github availability has gone below 90%, is this this high time we realise…🙁what AI is doing to us

@vivoplt i think its high time we should add kiro cli

be honest, which AI tool is best for coding?

@dpratyush02 32

As a Developer, how much RAM is enough for you? • 8 GB • 16 GB • 24 GB • 32 GB • 64 GB • 128 GB+

@sama @jaltma U really touched the nerve man

@jaltma We can offer you a free chatgpt pro account, two openai tshirts of your choice, and you have to have max and me on the show together to discuss what went wrong in your weighlifting career.

Sam did the offer to buy Uncapped get lost in the mail?

@iHarnoorSingh i jus bought one

OpenClaw craze isn't over: Mac minis are still out of stock.. 30 days of wait time insane!!

@0xlelouch_ Cold start....and def not advisable during high spike period cause of thundering herd

If cloud auto-scaling adjusts resources based on demand, why not rely entirely on auto-scaling and never pre-provision?

I’ve never felt so "seen" by an app before. It’s wild...Little Bird honestly understands me better than I understand @LittlebirdAI It just clicks in a way most software doesn’t. Truly in a league of its own.

System design interviews: ‘Design for regional failure’ Reality: data centers getting bombed in wars. Iran targeting cloud infra just proved #bahrainattack

System design interviews: ‘Design for regional failure’ Reality: data centers getting bombed in wars. Iran targeting cloud infra just proved #bahrainattack