Angel Buzany (@abuzzany) header
Angel Buzany (@abuzzany) profile picture

Vibe code fixer

Joined August 2010
Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)Photo by Angel Buzany (@abuzzany)
Descansa el Trabaja aunque dia de muertos esté muerto
20
605
58
9,335
117,354
Angel Buzany retweeted
Aquel día, la humanidad recibió un triste recordatorio: el de que vivíamos con miedo a los titanes, y hundidos en la deshonra de vivir en estas jaulas a las que llamamos muros.
30
63
5
1,022
12,443
Angel Buzany retweeted
Una catrina de como 32 metros en el Zócalo de la CDMX 🇲🇽
123
2,819
228
40,081
626,637
Angel Buzany retweeted
Why people should learn to code by hand: it's a mechanism for learning and teaching. In much the same way you should still learn calculus, even if writing it by hand isn't that "useful" for your career. @karpathy's series on llm's is a wonderful example (it's incredible btw). Come in knowing a little calc AND python and you'll get a ton out of it very quickly. Following this would be much harder not knowing operator overloading, FP arithmetic, classes, etc. The future is not writing python, rust, or asm by hand. But just like learning mathematical notation, grokking one or a few PLs well is a foundation on which you can build a lot of other deep knowledge, and gain a strong sense of computing systems.
Next stream series: building an LLM from scratch. A lot of us "know how llms work." Prompts, context windows, tokens, kv caches. But if you're like me, you have a lot of holes in deeply understanding the math, training, and the way inference actually works. Given how transformative they are to the entire planet, I want to dig in wayyyy more. So join me! Going through this along with Karpathy's video series on stream the next few weeks. Starting tomorrow 10am PT
23
136
5
2,040
103,631
Angel Buzany retweeted
"Perdón oficial, olvidé mi licencia de conducir"
18
837
29
16,855
127,362
Angel Buzany retweeted
TESLA ROADSTER en Latinoamérica 👇🏼
242
4,582
415
38,925
535,657
Angel Buzany retweeted
“A ver lo que tienen preparado con el show de drones en el cielo…” - SANCOR SEGUROS
42
1,651
51
17,196
192,399
Hay que meterle durisimo a la primaria
This Post is from a suspended account. Learn more
5
176
Angel Buzany retweeted
A U R A
5
61
2
465
4,047
Angel Buzany retweeted
✍️ Writing is essential to how @Mercury communicates as a 1300 person remote-first company. I wrote on Writing At Mercury (inspired by @vxanand's post). Principles of Writing at Mercury 1. Writing is thinking: Spending time on writing is not wasting time, it helps you process ideas, analyze problems, and explore solutions. 2. Less writing is better: Good writing is concise, which makes it easier to understand. 3. Reading should be easy: If >2 people will read your writing you should spend extra time making your writing good + digestible + clear etc. It is not fair for people reading to do work that the writer could have done for them. 4. Writing is expression: Your writing will be taken as an expression of your identity, so give it the care it deserves and be authentic. 5. Writing is important: Writing is the main way we communicate internally at Mercury, as a remote-first firm. We frame important discussions, and document thought processes and ultimate decisions, with our writing. On Using AI for Writing It is very easy to use AI to write a lot of content. If you do so, then by default you have: 1. Outsourced your thinking 2. Created a verbose/long doc 3. Made it hard to read 4. Have a doc that is not expressive and very bland 5. Watered down our discussions and decision making In other words, heavy AI use for writing is diametrically opposed to the principles of writing laid out above. Some effective ways that AI could be used instead: 1. Critiquing your writing 2. Condensing your writing 3. Shaping initial drafts 4. Summarizing complex information On Using AI to Respond on Slack/Comments Slack threads and comments are a particularly bad use of AI writing. 1. Slack responses and doc comments should always be short. Large blocks of AI text don’t belong. 2. AI used here is often thoughtless and the other party could have just used the AI tool themself. It inherently shows a disrespect for the reader’s time. 3. Given our remote culture, one of the main ways we connect with each other is via Slack. Using AI often would obscure your authentic perspective. 4. It would be better to share the prompt you gave to the AI directly to the other person and they can just prompt their own AI tool. How to do Great Writing at Mercury We aren’t going to police whether someone is using AI or not to help them write. We will just have a high standard for your writing output. Here are some high-level rules that should help: 1. Always read and stand by 100% of your written output. 2. When it is important, spend time on your writing. You might spend time on the narrative arc, the tone, the structure, whether it clearly articulates an issue, explores solutions, and drives toward an outcome. 3. Think hard about how you can use fewer words and be more concise. 4. Be authentic. You don’t need to dress up your writing in corporate jargon to make it sound professional. Simple, plain writing is often more effective. 5. Never copy-paste AI responses to someone in Slack or to comment on a doc. 6. Sometimes it's better to write nothing at all. Don’t make a comment in a doc/slack because you want to be part of the convo, say it if it materially moves things forward.
22
34
12
531
46,586
Y no ha visto las macros que alguna vez me tocó meter mano en otra chamba
Replying to @dhh
The code really is hilariously hideous. But again, I don't intend to spend any time writing it or reading it. It's a prompt compilation target. So who cares.
98
Angel Buzany retweeted
Matz compiles Ruby and so we compile Ruby.
4
15
197
8,007
Es horrible la cantidad de spam que recibo al día vía Linkedin. No se en que momento de volvio un marketplace
1
72
Angel Buzany retweeted
"Have I now become your enemy by telling you the truth?" — Galatians 4:16 Reddit is coping with reality about as well as you'd expect.
361
209
70
6,853
286,301
Angel Buzany retweeted
For engineers having trouble with @dhh’s talk here some obvious truths about the future of programming: You will not write code You will not read code You will not choose a language You will design the architecture You will define outcomes You will build auto-delivery loops
130
79
26
1,078
84,521
We are not coders; we are Engineers
Software has never been about writing code. It’s always been about giving people more hands, limbs, and minds.
72
Angel Buzany retweeted
Software has never been about writing code. It’s always been about giving people more hands, limbs, and minds.
59
64
18
977
154,030
Angel Buzany retweeted
It's pencils down, people. Writing code by hand is no longer an economically viable skill for most programmers at most companies. But the future of making software has never been brighter. Don't you dare black pill this beautiful moment! youtu.be/vDjW_dRyKXY?si=6Fsf…
429
1,000
521
9,381
3,307,463
Fixed: I love Rust! Rust is amazing if you never ever have used fucking Macros 😁😁😁
"I love Rust! Rust is amazing ...if you never, ever, EVER have to look at it yourself." — @dhh
1
139