Pybites

Helping people worldwide to improve their #Python #developer skills.
Created by @bbelderbos & @juliansequeira.

[Pybites @pybites]

Reading about #Rust doesn't make you write it.

What works: write a bit of Rust every day and let the compiler push back.

[Bob Belderbos @bbelderbos]

Thanks 🙏 @realpython for featuring my #Python + #Django design patterns article, where I walk through the design decisions behind my Commit Graph habit-tracking app. 🚀

I really liked how you framed it as a “this worked in this case, and here's why I did it” kind of article.

Those are my favorite pieces to write. They help us move beyond “this library does X” toward “how should we think about software?”

And I believe that kind of engineering judgment is becoming more of a moat these days as well.

🎧 Listen to the discussion here:
https://t.co/UFPh3jPmGy

I'm already working on Part II… 👀

[Bob Belderbos @bbelderbos]

Just published a new crate to https://t.co/uKAxMrAu4H: bob-json-parser 🦀

It's a JSON parser written from scratch in #Rust: a hand-written tokenizer and a recursive-descent parser, with no serde.
PyO3 bindings let you call it from #Python as a native extension.

It's the 6-week capstone of our <Scripter to Rust> cohort, and I built it alongside last cohort.

I published it so I can use it in another tool I'm building that needs to parse JSON logs, simply: `cargo add bob-json-parser`

Check it out -> https://t.co/iAZVFQs7eV

Curious about leveling up with Rust?
DM me or join our community -> https://t.co/YgcIZKhwO9

[Pybites @pybites]

Start here: https://t.co/2EsxkNXaid

[Pybites @pybites]

Reading about #Rust doesn't make you write it.

What works: write a bit of Rust every day and let the compiler push back.

[Pybites @pybites]

80-second walkthrough 👇
https://t.co/j5lDOEQD7e

[Bob Belderbos @bbelderbos]

LLMs can write syntax, but they can’t replace human engineering judgment.

As AI agents generate more of our codebases, live design sessions become *more* valuable, not less.

Juniors still need to learn how experienced engineers THINK, something async code reviews only partially answers.

Ensemble (mob) programming makes live architectural thinking, trade-offs, and micro-decisions visible in real time.

I co-hosted live ensemble sessions back before AI agents, and developers loved verbalizing *why* they chose specific patterns.

So I built a lightweight tool for it:

👉 Try the MVP: https://t.co/SXIrNT80z9 (zero installs and signup, Pyodide Python, driver/navigator timers)

👉 Help test drive it: https://t.co/cb7jXn3mX0

I'm curious to gauge interest: in an agentic world, do you feel the need for live, human-to-human design and coding sessions has grown? How would you use this? 👇

[PyCoder’s Weekly @pycoders]

How Libraries Run Rust Inside Python (With PyO3) https://t.co/pexsmT9r6v

[Bob Belderbos @bbelderbos]

I just hand-coded a simple FSM (Finite State Machine) in #Python 💡

Some people might ask:

It’s 2026. Why even code by hand?

Because the thinking, debugging, and deeper understanding that go into an exercise like this are still valuable.

I had to reason through the design, trace what was happening, debug it, and really understand the code.

It's slower, but now I own it.

And I can teach it better.

It was also one of my happier moments this week.

Only reading code and managing agents is not the same as being in touch with the code and understanding how something works at all levels.

(I also had to explain Rust ownership / the borrow checker this week 💪)

Now I'm going to do it again for my YouTube channel.

We'll see how much hand-coding remains in the industry, but I do think regularly writing code yourself is a great way to keep your technical skills and intuition sharp.

And judging by the feedback I get, this is also what people seem to value most in my videos: watching the thinking behind the code so the 'how' + 'why', not just the 'what'.

[Bob Belderbos @bbelderbos]

Scripter to Rust cohort: https://t.co/E66KUa9Vqh

Rust coding platform: https://t.co/1nf1r8w8I5

[Pybites @pybites]

@unit0r nice!

[Pybites @pybites]

What are you building with #Python this week?

[Pybites @pybites]

@driscollis when do you guys plan on using it? eager to hear how it works for you...

[Pybites @pybites]

The best features come from listening to your people 💡

&gt; my local Python users group wanted to know if the free tier included a leaderboard or not as they thought it might be a fun activity for one of their meetings.

[Pybites @pybites]

@driscollis Thanks Mike, hope you like it, photos welcome :)

[Bob Belderbos @bbelderbos]

Learning #Python 🐍 syntax isn't the hard part.

It’s everything around it where beginner devs typically get stuck:
- the terminal / SSH keys,
- git and the GitHub PR flow,
- virtual environments,
- dependencies and packaging,
- writing your first tests,
- linting,
- etc.

Overkill for a single script.
But all needed for shipping / sharing an app.

I'm building a free, self-paced 6-week course to help Pythonistas learn all this and more.

We do that by building a command line app from scratch using these tools + workflows.

Week 1 - Project Setup & Data Model - is live now 🎉
https://t.co/vZctIPqEvD

Each Friday I'll launch the next week of content - more info in my launch post ->
https://t.co/BjQAlttBTW

Hope this helps more Python developers ship their projects with confidence. 🚀

Enjoy and any feedback welcome, let's go! 💪 🙏

[Bob Belderbos @bbelderbos]

My goto for a swappable backend in #python has been an abstract base class (ABC).

There is a flexible alternative though: Protocol (typing module).

Take LLM providers as an example.

An ABC comes with a requirement: every provider has to inherit from your base class.

Fine when you write every provider yourself, less so when they're third-party plugins.

`typing.Protocol` uses "structural typing" instead. Conformance lives in the method shape, not in a shared base class.

So a provider can evolve freely as long as the shape holds, and inherits no methods it doesn't use.

And the type checker still catches a missing method or wrong signature at lint time.

I still reach for ABCs when providers share concrete behavior, but protocols are the more flexible default.

So next time ask: shared contract, or shared implementation?

More in my new article: https://t.co/hOkZpfuzoz

[Pybites @pybites]

Increasingly #python libraries get rewritten in #rust.

Curious about this safe + performant language?

Start from scratch on our Pythonista-friendly platform: https://t.co/2EsxkNWCsF

[Bob Belderbos @bbelderbos]

How do libraries run #Rust inside #Python?

It all comes down to 4 steps:

1. Write Rust code.

2. Annotate it with PyO3 macros.

3. Let maturin compile and install it.

4. Import the result.

New article seeing this in action for a hand-rolled JSON parser: https://t.co/uAUPkgN1Nh

[Pybites @pybites]

We've just added this. 🎉

Docs page: https://t.co/8AWsEb0PWV

We hope that people running #Python meetups, workshops, or classrooms will benefit from this feature to make those events more engaging adding live coding + friendly competition. 🏆

[Bob Belderbos @bbelderbos]

AI made building fast. That includes building the wrong thing faster.

Before writing code, you need a tight scope: what to build, and more importantly, what NOT to build.

I built a simple tool to pressure-test your idea before you spend weeks building it:

[nikhil · sys/quests @nick_realm_01]

Why Rust does not need OOP

have a read guys.
https://t.co/V62lPtTpXN