ArjanCodes’ Post

Two lines of Python. Same result. Very different design. A method and a property can look almost interchangeable, but they communicate very different things about your code: cost, safety, and intent. Get that choice wrong, and you end up hiding work, I/O, or even async behavior behind what looks like a simple attribute access. In today’s video, I walk through clear, practical guidelines for deciding when something should be a property and when it should be a method. I’ll look at derived state, setters, Protocols, and why async properties are usually a design smell, even though Python technically allows them. 👉 Watch the full breakdown here: https://lnkd.in/eTHn7Rks. #python #softwaredesign #cleancode #objectoriented #apiDesign #developers

  • No alternative text description for this image

To view or add a comment, sign in

Explore content categories