Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Editor's Note: The following is an article written for and published in DZone's 2021 Low-Code Development Trend Report.
If you ride on a sailboat in a steady breeze, it glides through the water effortlessly. Few things can compare to crossing a bay without the noise and commotion of a thundering internal combustion engine.
Before getting started, check out this GitHub repo with all the code you need for this demonstration.
So, without further ado, it's time to add type hints and learn some interesting lessons from it.
Let's take another look at F. L. Stevens's spreadsheet with agencies and agents. It's — of course — an unholy mess. Why? It's difficult to handle state change and deduplication.
Let's look at state changes.
Consider the following code:
def max(m: int, n: int) -> int:
if m >= n:
return m
elif n >= m:
return n
else:
raise Exception(f"Design Error: {vars()}")
The code has a super-simple email message with f"<html><body><p>stuff {data}</p></body></html>". It was jammed into an email object along with the text version. All very nice.
For a moment, I considered suggesting that f-string substitution wasn't a good long-term solution since it doesn't cover anything more than the most trivial case.
There are patterns to bad writing. I'll give some examples based on a blog post I was sent. It's also based — indirectly — on some of proposals I saw for PyCon and PyDataDC.
For the conference calls for papers, I can ask a few questions of the author, but that's about it.