Abinash

@johncrickett I still write by hand every single day, and I love it.

This week I went back too 100% writing my code by hand. It was the most productive path.

@boshen_c Sometimes, having fewer resources forces us to be more efficient with what we do. I still use Vim without an LSP because my laptop can't handle rust-analyzer.

I spent $6k worth of tokens in the last 3 months but why do I feel so empty inside. Did I do meaningful or impactful work? Did I actually learn anything? Did my engineering skills improve? Did my peers liked my slop PRs? Nope!

@fayazara Can I get the dark version of it?

If you want to make these animated code snippet videos. Runs is the browser, made with Shiki + Remotion + Mediabunny reelcode.fayaz.workers.dev

@typecraft_dev @PlanetScale Wait, what? That means we will get Database stuff instead of the terminal.

I'm so excited to announce that I've joined @PlanetScale as a content creator / educator! This is going to be huge. Lots of great stuff coming up. Stay tuned...

@rustrover @LoriLorusso @rust_foundation I am starting to like JetBrains efforts towards Rust content.

''Is Rust really that hard to learn?" We asked @LoriLorusso from the @rust_foundation 4 quick questions about Rust. Here's one of them.

@StefanTMD I thought to comment "Because you don't have me in your team". But after seeing the comment, I changed my mind.

ryan is the funniest person on our team

@johncrickett Sorry to say it again, but I think you should link the video, not the channel.

@implabinash Yup, my bad, copied the LinkedIn announcement post.

@GergelyOrosz Kind of outside of the topic: Watched the latest episode with Dax on dev tools. Is there any chance of getting an episode about building core system software as a startup, like a debugger or something like that?

Amusing: I'm hearing that at several tech companies, a more frequent topic on internal knowledge sharing sessions is about efficient AI usage. Cannot really remember topics like "techniques for faster CI/CD" or "how to speed up builds" being THIS widely discussed in the past!

@rough__sea I think you should save your energy to spend on @deno_land.

I really don't want to be vegan. Because actually I have no problem with killing animals for food - it's just the way of the world. I don't even really mind torturing animals for food - as long as they're low cognition (fish, insects, etc) However - I really don't want to participate in the active (often life long) torture of high cognition animals like pigs. Chickens are pretty dumb, but I'm not down with stuffing them into small cages their whole lives to peck at each other. Not ok with dairy cow-calf separation. And the more you look into it, the more you realize that humane sources of meat, dairy, and eggs are VERY hard to come by. Buying the more expensive brand at the grocery store does not imply torture free. If you're eating bacon, an egg, cheese from a random restaurant - you are participating and enabling animal torture. These labels "vegan", "vegetarian", "pescatarian" don't work for me. A vegetarian who eats dairy and eggs still participates in torture. I would lustfully eat a steak that had a good life, or an egg from a non-factory farm. For all the daily political bullshit that happens - the torture of billions of animals is so rarely discussed.

@GergelyOrosz I think companies are facing difficulties due to a huge no of AI and fake resumes, and I think this is just a surface-level problem.

Been doing research on the job market for devs: and it's still a weird market. Job openings are up, but devs don't seem to feel that it's a much better market? Meanwhile, companies are also struggling to fill roles. Take this full remote (US) sr eng role at $155-184K salary at a nonprofit. No AI-related anythign at all:

@penberg I think people won't be mad if he hadn't merged into the main. If he admits, it's an half backed idea, it should be in a different branch until it replaces Zig's implementation in terms of correctness, efficiency, and code quality.

It’s both funny and sad that many people are complaining about how ”terrible” the Rust code in the Bun port is. It’s like that on purpose because Jarred took the safe and correct path of mechanical translation from Zig. Idiomatic Rust should be incremental!

@GergelyOrosz Is there any chance of getting some episodes on compilers, more specifically, the Rust compiler? (Note: I have already watched the episode with Chris.)

Later today on The Pragmatic Engineer podcast: a new episode with Anders Heljsberg, the creator of Turbo Pascal, Delphi, C# and TypeScript. This was such an interesting one!

I agree with this one. I think checking and making sure your code is up to the standard is the correct way to use AI. And I was wrong to assume we were talking about vibe coding. Personally, I use AI a lot to build some tools for my workflow, and I couldn't do it without AI (because will take a lot of time), but I also have to edit a little bit by myself.

@implabinash @ashtom And IDK about you but my AI-generated code I form until it’s as minimal as I want it to be… it’s my code, my responsibility to not push slop! If you let it rip that’s vibe coding

“People claiming that AI is slowing them down because of all the slop are not all that different from people that claimed DevOps is slowing them down.” - from @ashtom A new tool is just a tool, and there are many ways to use it, including productively and counter-productively!

@jarredsumner That means, Bun will be the first AI-written runtime. Will it be reliable?

Bun v1.3.14 releases tomorrow. If we do merge the Rust rewrite, this would be the last version in Zig

13. High Performance Browser Networking

10. The Design of Everyday Things 11. Emotional Design 12. The Visual Display of Quantitative Information

My Current Reading List: 1. The Crafting Interpreters (currently reading) 2. Operating Systems: Three Easy Pieces 3. Rust Atomics and Locks 4. Bootstrapping Computing 5. The Making of Prince of Persia 6. The Art of Computer Programming 7. The Unicorn Project & The Phoenix Project (not sure yet) I will be extremely happy if someone or some company sponsor me some books.

@GergelyOrosz Are you sure that you are a human?

Discord's "are you human" captcha went from "a human can solve it immediately" to "sit down and do some work for it." I can do it, but captchas were meant to be dead simple for humans, hard for bots. This is NOT dead simple for humans...

Resources: 1. Let's Build A Simple Interpreter by @rspivak Start with this one; it will teach you the absolute fundamentals of building an interpreter. Here, the author is building a Pascal interpreter in Python. Link: ruslanspivak.com/lsbasi-part1/ 2. Crafting Interpreters This is the gold standard when it comes to learning about interpreters. Here, you are building two interpreters in Java and C, also in two different ways. Link: craftinginterpreters.com

Let me teach you "Interpreter 101" in 1317 characters. From the 1960s, interpreters have been made more or less in the same way. We have 3 major processes: lexing, parsing and interpreting. 1. Lexing: Process of converting characters into meaningful tokens. In simple terms, it takes your source code and converts it into individual tokens like "Int(42)", "Plus", "Minus" or "Semicolon", etc. This is the very stage that identifies the unexpected characters like "@". 2. Parsing: Process of converting a stream of tokens into an abstract syntax tree or AST, in short. It takes all the tokens we produced during lexing and converts them into a tree-like structure by forming relations between those tokens. Here we got errors like expected ";" or expected "else" but got "else if", etc. 3. Interpreting: Process of evaluating the abstract syntax tree into the end result. It is the last stage of an interpreter. Here we walk through the AST, compute results and give output to the user. This stage is responsible for runtime errors like "can't divide by 0" or "integer overflow", etc. Note: This is just a brief overview of a simple interpreter, but if you are interested in learning more about interpreters, I highly recommend these 2 resources: - Let's Build A Simple Interpreter by @rspivak - Crafting Interpreters #Interpreters #Lexing #Parsing #Parser #Scanner #Compilers