https://signal-and-syntax.com/categories/python-techniques-and-tooling/Recent content in Python Techniques and Tooling on Signal & SyntaxHugoen-usWed, 17 Sep 2025 13:00:00 -0700https://signal-and-syntax.com/posts/python-integer-division-and-modulus/Wed, 17 Sep 2025 13:00:00 -0700https://signal-and-syntax.com/posts/python-integer-division-and-modulus/numbers with // and % for speed and clarity." }} When you need to parse a number, the first instinct is often to convert it to a string and slice it. That works well for data that comes from people — like phone numbers, credit cards, or postal codes — where formatting and leading zeros matter. But when you are working with raw numeric data that is guaranteed to be fixed-width and free of formatting, numeric parsing with integer division (//) and modulus (%) is the better option.https://signal-and-syntax.com/posts/python-sympy-vs-numpy/Fri, 05 Sep 2025 11:45:00 -0700https://signal-and-syntax.com/posts/python-sympy-vs-numpy/Most of us reach for NumPy whenever math shows up in a project. But sometimes, you don’t want approximate answers, you want exact math. That’s when you pull SymPy out of your programmer’s toolkit and get to work. It’s easy to think of SymPy only in academic terms, like running physics simulations where small rounding errors can snowball into nonsense, or checking algebraic identities where a value such as 0.0000001 should really be treated as exactly 0.https://signal-and-syntax.com/posts/python-dispatch-maps/Fri, 22 Aug 2025 10:38:20 -0700https://signal-and-syntax.com/posts/python-dispatch-maps/Let’s be honest: argument validation code is rarely the proudest part of anyone’s repo. Most of us start with the usual suspects: ❌ The dreaded inverted-V tower of if/else statements ❌ A graveyard of guard clauses scattered line after line Both work fine… until they don’t. Then you’re left maintaining a wall of conditionals that feels like it was designed by a committee of goblins. There’s a better way: dispatch tables!