Backend Engineer • Low level System Programming

Joined March 2018
Pero Dios...
1
1
My frequent recommendation: Performance Engineering of Software Systems from MIT ocw.mit.edu/courses/6-172-pe…
CppCon 2014: Chandler Carruth "Efficiency with Algorithms, Performance with Data Structures" youtu.be/fHNmRkzxHWs
2
43
3
366
36,134
kaneda retweeted
Wrote a blog on serverless 101 . Link in the replies
11
45
1
878
21,265
If you are beginning with compilers and are interested in clang, "An Overview of Clang" is a good talk. youtu.be/5kkMpJpIGYU
3
29
283
6,008
kaneda retweeted
ban and delete most if not all code comments! agents love copying what already exists. a seemingly harmless comment explaining some temporary workaround is one of the worst viruses you can have in your codebase. like a weed it'll spread quickly as a tool for agents to quickly get their job done. before you know it, your codebase is overrun with hacks and stale comments. just one more workaround bro you can use pstack's /no-comments skill as a weedkiller. it'll seek out useless comments while keeping the ones that actually should exist (like explaining a browser quirk), and figure out how to solve them on a first principles basis here's a prompt you can try asking @bot: create a project agent that uses /poteto-mode to spawn a /swarm to use /no-comments and identify useless code comments we can prune in my repo. come back with a high level plan of which of these workarounds would be best solved by refactoring and which we can straight up delete x.ai/bot/plugin/9717366
313
210
143
5,094
490,640
kaneda retweeted
if you’re interested in backend engineering, read this blog on timeouts, retries, exponential backoff and jitter
4
11
1
224
5,157
Checking in on Speedometer 2.1 again. We're getting close to the @ladybirdbrowser alpha and I'm currently pushing hard on performance! 🤓📈
Checking in on Speedometer 2.1 in @ladybirdbrowser one year later (same machine ofc). We haven't been doing focused work on it, but general performance work is pushing it up anyway. You love to see it! 🤓
17
8
3
398
9,093
Los empresarios dominicanos son AI Engineers. Los haitianos son sus agentes: baratos, silenciosos y nunca piden vacaciones ni aumentos. La República Dominicana es el servidor que se quema mientras ellos hacen dinero.
La mano de obra haitiana no es vital para la República Dominicana. Es vital para el dueño del negocio que necesita un costo operativo casi-cero para poder embolsillarse la mayor cantidad de dinero posible.
26
Linux Networking 101 🛠️ Understand a Linux host's network configuration: find interface names, IP and MAC addresses, the default gateway, and determine which route it would use to reach a certain destination. Free practice at labs.iximiuz.com/challenges/…
2
72
1
610
15,850
kaneda retweeted
Found out that LinkedIn has a gold mine of distributed systems related blogs probably gonna read most of them while I travel for next few days :D
2
43
1
725
26,353
kaneda retweeted
and just like that stripe too has good amount of blogs on infrastructure and sandbox related blogs
Found out that LinkedIn has a gold mine of distributed systems related blogs probably gonna read most of them while I travel for next few days :D
5
18
354
6,568
Princeton's "Distributed Systems" (COS 418) by Michael Freedman, Kyle Jamieson & Wyatt Lloyd Covers RPCs, logical clocks, consensus/RAFT, Spanner & more. Course website: cs.princeton.edu/courses/arc…
74
3
568
18,270
Here are the basics for the compilers as lecture notes cs.cornell.edu/courses/cs412…
CS 6120: Advanced Compilers: The Self-Guided Online Course cs.cornell.edu/courses/cs612…
3
61
1
453
11,572
kaneda retweeted
after partially completing my rabbit hole of netflix's ai infrastructure its time to go for stripe's rabbit hole started with how do they build their proxy and the optimization tricks to play while building one stripe.dev/blog/building-a-d…
5
25
357
8,956
Ese mismo policía lo he visto en otros dos videos más en donde también abusa de su poder ¿solución? Cambiarlo de zona. Así es como funcionan las cosas en RD. Gracias a @PoliciaRD @pesqueiradiego @FarideRaful
1
30
kaneda retweeted
Gave Claude another 12 hours to one up this.. Woke up to.. The Clodyssey
Gave Opus 5.5 donald's prompt, Midjourney, and a moodboard 12 hours later, woke up to this:
486
1,030
365
9,634
12,484,808
kaneda retweeted
tl;dr of the upcoming blog/article its been ages since I have dropped a well "time spent" blog/article . I will be starting this series again :p happy learning chat
3
7
165
3,115
🚨🚨🚨 Oct 7th from someone who was on the other side. What I've learned since then.
398
263
63
1,774
196,901
I remember October 7th. October 7th is what genocidal intent looks like. Those who participated in, supported, or even sympathetically "understood", those actions are broken souls.
39
50
1
1,415
31,193
kaneda retweeted
empezar a aprender AI y agentes puede ser abrumador. hay demasiados conceptos, frameworks, modelos y cosas nuevas saliendo todo el tiempo. algunas cosas que me ayudaron a ordenar mejor qué estudiar y cómo avanzar: 1) empezá por fundamentos: LLMs, tokens, contexto, prompting, embeddings, tool use y RAG. 2) después entendé cómo funciona un agente: modelo + tools + estado + loop. 3) construí cosas chicas. un agente con 2 o 3 tools ya te obliga a entender cómo se conectan varias piezas. 4) no intentes aprender todos los frameworks. elegí uno y entendé qué resuelve por debajo. por ejemplo, usar LangGraph para aprender estado, tools y flujos te deja conceptos que después podés llevar a cualquier otro framework. 5) estudiá context engineering y orquestación: qué información darle al modelo, cuándo recuperarla, cómo manejar el contexto y cuándo conviene dividir una tarea entre varios agentes. 6) cuando avances, sumá evals, memoria, subagentes, planning, human-in-the-loop, retries, observabilidad y guardrails. ahí empezás a pensar en agentes como sistemas de verdad. 7) usá la IA para estudiar. pedile explicaciones desde first principles, ejemplos, ejercicios y preguntas que encuentren huecos en lo que entendiste. si algo sigue sin cerrar, bajá un nivel y entendé qué pasa por debajo. y probablemente el que más me sirvió: escribir/explicar lo que voy aprendiendo. si no podés explicarlo con tus palabras, todavía te falta entenderlo.
19
80
4
893
33,804