Pybites Β· linkedin.com

IT Services and IT Consulting

Sydney, New South Wales 1,642 followers

We create Python developers.

About us

Operating successfully across over 120 countries, including direct agreements with government agencies and agencies

Industry
IT Services and IT Consulting

Company size
51-200 employees

Headquarters
Sydney, New South Wales

Type
Partnership

Founded
2016

Specialties
Python, Education, Coaching, Training, Software Development, and Programming

Employees at Pybites

Locations

Updates

  • Pybites reposted this

    Rust πŸ¦€ isn't replacing Python. It's replacing the parts of Python that hurt the most. β€’ CI too slow? β€’ Runtime bugs annoy you? β€’ AI writing code you don't fully trust? β€’ CPU and memory costs higher than they should be? Looking for a stack that rewards good engineering? First and foremost none of these problems exist because Python (or scripting language ___) is bad. They exist because software engineering is changing. We're entering an era where compile-time guarantees, performance, and predictable systems matter more. πŸ’‘ The fastest tools in the Python ecosystem increasingly have one thing in common: they're powered by Rust (uv, ruff, Pydantic v2's core, Polars, cryptography, prek). But speed πŸƒ is only part of the story. Rust catches bugs earlier. The compiler forces you to confront problems while coding instead of discovering them at runtime. LLMs are great at producing code. They're less good at guaranteeing correctness. Rust's compiler provides guardrails that help catch mistakes before they make it into production. As AI workloads become more common, CPU and memory costs matter again. Efficient software isn't just more elegant, it's also cheaper to run. Again, I don't see Rust replacing Python. 🐍 I see it becoming an increasingly valuable addition to every Python developer's toolkit. πŸ“ˆ That's one of the reasons Jim Hodapp and I built a 6-week Python β†’ Rust cohort. We help experienced Python developers add Rust to their toolkit by building real software, not toy examples. Which of these trends resonates most with you? Or is there another reason you've started or want to start looking at Rust this year? πŸ’ͺ

  • Pybites reposted this

    Day 13 Β· Custom Error Types πŸ¦€ Python: subclass a built-in exception (e.g. `Exception`) #Rust: define an `enum` of everything that can go wrong. From simple flags like DivisionByZero to variants that hold data like ParseInt(String), use match to handle each exhaustively. Errors as data, no surprises. πŸš€ Put it in practice coding bite #13 πŸ‘‡ https://lnkd.in/ep7BNcHc

  • Pybites reposted this

    We say "explicit is better than implicit" in Python and a lot of Python code you'll write confirms to that. But I feel #Rust takes it to the next level! Not only do we have required type hints here, we also see: - is the data moved (taken ownership of), or borrowed? - will it be mutated? As per the example, little code, but very expressive. So yes, this can be more painful to agree upon with the borrow checker when you start out, but this 'pain' upfront does lead to code you can more easily trust (even more important with AI nowadays). Also, usually in software locking things down by default is a good design decision. And although I often like a GC because the average code is fast enough, the side effect of having to deal with memory + scoping does add a new level / paradigm to your programming skills (similar to discovering functional programming after OOP).

  • Pybites reposted this

    We all love Unix tools, right? They're quite easy to emulate in Python, but how would you build them in #Rust? πŸ¦€ Enter the new Unix tools track: 10 bites reimplementing wc, grep, cut, sort, uniq and friends. Give them a go and practice writing idiomatic Rust with iterators. πŸš€

  • Pybites reposted this

    Some more good #rust learning today, wrapping up the intro Bites πŸ¦€ Especially tokenizer + parser (10 and 15) will throw a curve ball here and there, and they form a nice (simplified) sneak preview of things we have you build in our JSON parser cohort. πŸ’ͺ As usual the compiler was helpful guiding me. 😍 Also it's always a win (specially in this AI era) to try it yourself, problem solve, writing overly verbose code, and then learn from the solution that there is a simpler (and probably more efficient) way to do things. πŸ’‘ Interested in jumping into Rust? Join me here and let me know how these exercises go for you? https://lnkd.in/eKwR53gj

  • Pybites reposted this

    Something has been bothering me about how I use AI coding tools in my own work. So when Anthropic published a study in January demonstrating that their own AI assistant makes developers measurably worse at understanding code, it hit a real nerve. The finding that stuck with me: the skill that declined the most was debugging. That's the one skill AI most needs you to have, and it's the one it's quietly eroding from you. But the study also found that not all AI use is equal. *How* you use the tool matters more than *whether* you use it. Obviously, these tools aren't going away. That's why I broke down the four patterns of using these tools and what they mean for anyone trying to stay sharp while working with them. #coaching #softwaredevelopment #developers #ai

    The Company That Built the AI Coding Tool Just Proved It Makes You a Worse Developer Jim Hodapp on LinkedIn

  • Pybites reposted this

    Here's the artifact students walk away with from our #Rust πŸ¦€ cohort. A JSON parser: β€’ Written entirely in Rust β€’ Handles any valid JSON (nested objects, arrays, all types, Unicode) β€’ Callable from Python as a drop-in replacement for json.loads() β€’ 10–12x faster than Python json implementations (e.g. simplejson) β€’ Includes professional documentation and benchmarks   Built incrementally, one concept per week: β€’ Week 1 β€” Tokenizer, pattern matching, basic Rust types β€’ Week 2 β€” Error handling with Result<T, E> and ? β€’ Week 3 β€” Structs, methods, ownership and borrowing β€’ Week 4 β€” Collections, recursion, full nested JSON support β€’ Week 5 β€” Python bindings with PyO3, type conversion β€’ Week 6 β€” Benchmarks, documentation, release builds This isn't a tutorial you follow. It's a project you own. By the end you have something real, something measurable, and the mental models to keep building on Rust further. 6-week cohort for Python developers. No prior Rust experience needed. Bring your commitment to excellence and your enthusiasm. --- Here is what students from our first cohort have said after completing it: "The code reviews were really helpful, especially the suggestions of other ways to think about decomposing a solution using different idiomatic Rust patterns." "The quality of the materials, the topics are very well connected to real software development." "Handled the transition from Python to Rust really well. The fully integrated application tied it all together." "The deliberate learning was great: I felt it was very rewarding to not use AI to code at all, not until week 5." "I always felt supported and confident that I could reach out and get a thoughtful response." "The TDD style was super valuable, a clear 'definition of done' every week." --- After 6 weeks, students rated their confidence to start a new Rust project ranging from 7-9 out of 10. That's what deliberate, structured learning looks like. πŸš€ (Thanks Vikas Z. for sharing the numbers below)

  • Pybites reposted this

    From Python 🐍 to Rust πŸ¦€ β€” 6 weeks, Zero-to-One, building a JSON parser from scratch in Rust πŸ¦€ Last November, I came across Pybites hosting a beginner Rust cohort. Having followed Bob Belderbos for a while on X, I was quick to sign up. I had the privilege of being part of this cohort, coached by Jim Hodapp. πŸ›« Over 6 weeks, we built a complete JSON parser from scratch β€” tokenizer, recursive descent parser, error handling, PyO3 Python bindings, and performance optimization. πŸ‹β™‚οΈIt taught me to think like a library developer β€” every public interface is a promise, every allocation matters, and your users are developers who will push your edge cases harder than any end user ever would. A fundamentally different mindset from being an application developer. πŸš€ The result? Only 0.8x slower than CPython's battle-hardened C extension. 12–14x faster than simplejson. Zero dependencies. Zero unsafe. πŸ‘‰ Check it out on my Github: https://lnkd.in/gzm4icJw 🫑 Jim Hodapp's detailed PR reviews every week and the hands-on approach made Rust click in a way tutorials never could. ⚑ If you're curious about Python or Rust, check out Pybites β€” highly recommend it.

    GitHub - 13hulk/rust-cohort: Pybites Rust Cohort: Build a JSON parser from scratch github.com

  • 1,642 followers

    Our #Python platform is getting better and better, apart from docs, we also polished the UI last week ->

    Not having (complete) docs earlier has been a miss! And with AI, it's now easier to fix than ever. Last week we added the whole suite to our @Pybites platform πŸ‘‡ No more people abandoning the app because it's unclear how it works. 😱 The best developer tools (Stripe, Vercel, Linear) treat docs as a first-class citizen and so should we from here on for all our products ... πŸ“ˆ Good docs don't just answer questions. They remove the moment of doubt that makes people walk away. Have you ever abandoned a tool β€” not because it was bad, but because you couldn't figure out how it worked fast enough? πŸ’‘

Join now to see what you are missing

Join now

Similar pages

Browse jobs

Read the original on linkedin.com β†—