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.
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
Angel Buzany retweeted
“A ver lo que tienen preparado con el show de drones en el cielo…”
- SANCOR SEGUROS
✍️ 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.
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
Angel Buzany retweeted
Software has never been about writing code.
It’s always been about giving people more hands, limbs, and minds.
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…
Angel Buzany retweeted
Prediction time.
@dhh just asked over a thousand attendees at #railsworld how many people still write code by hand on a regular basis. Less than 10 people raised their hand.
Let that sink in.
Next year the question will be how many people are still doing manual PR code reviews or directly looking at code on any regular basis. Result will be similar.
Angel Buzany retweeted
I am a sucker for good books, and so especially O'Reilly books.
Here's one that is WIP, but in return, it is free, thanks to @AntithesisHQ
It's for CTOs / eng leaders who want to get AI to deliver *business value* which is... tricky.
Get it here:
pages.antithesis.com/oreilly…
🤝 Paid partnership
Just one engineer and a team of agents ported the GitHub Copilot agent runtime to Rust, shipping 800,000 lines of production code while retaining code quality. 🚀
How it worked 👇
github.blog/ai-and-ml/genera…
Angel Buzany retweeted
If you're been around software long enough, you've heard the expression: "It's always a people problem."
And what do engineers do? We solve problems.
Think about it.































