Mike details his favorite python tools and his tricks for performance concerns.

Plus a bunch of workspace improvement ideas, feedback, and more.

Sponsored By:

• Linode: Receive a $100 60-day credit towards your new account. Promo Code: linode.com/coder
• A Cloud Guru: A Cloud Guru now includes Cloud Playground. Azure, AWS, or GCP Sandboxes at your fingertips.

Support Coder Radio

Links:

• Mechanical Keyboards Matrix Chat
• ThinkPad TrackPoint Keyboard II — The ThinkPad TrackPoint II Keyboard translates the ThinkPad notebook’s iconic typing experience into a stand-alone device.
• Gooseneck Tablet Holder — Flexible Arm Clip Tablet Stand Bed Desk Mount Compatible with iPad Pro Mini Air, Galaxy Tabs and More
• Portable Monitor — UPERFECT 15.6" 100% DCI-P3, 99% Adobe RGB, 500 Nits Brightness, FHD 1920x1080 IPS Screen
• Chris’ WFH Setup Pics on Instagram
• Welcome to Flask
• FastAPI — FastAPI framework, high performance, easy to learn, fast to code, ready for production
• Qt for Python | The official Python bindings for Qt — Qt for Python is the project that provides the official set of Python bindings (PySide2) that will supercharge your Python applications. While the Qt APIs are world renowned, there are more reasons why you should consider Qt for Python. The first official release of the PySide2 module is available now!
• Pylance - Visual Studio Marketplace — Pylance is an extension that works alongside Python in Visual Studio Code to provide performant language support. Under the hood, Pylance is powered by Pyright, Microsoft's static type checking tool. Using Pyright, Pylance has the ability to supercharge your Python IntelliSense experience with rich type information, helping you write better code faster.
• pylance-release: Documentation and issues for Pylance
• microsoft/pyright: Static type checker for Python — Pyright is a fast type checker meant for large Python source bases. It can run in a “watch” mode and performs fast incremental updates when files are modified.
• Jeremy Soller on Twitter — "I can no longer let things like this go. While System76 has been a part of the process, this should not be interpreted as consent to the new GNOME Shell design. We will do whatever possible to improve Pop!_OS UX even if it breaks significantly from GNOME's defaults."
• Carl Richell on Twitter — Yes, we were involved but our involvement had no impact on the design. Our design ethos and reading of the research differs. We raised our concerns and proposed a different design. We’re continuing our research and building prototypes.
• GNOME on Twitter — System76 was part of the entire process: setting up the research, doing polls, evaluating the results, suggesting changes
• KDE Architecture — Human Interface Guidelines documentation
• Plasma/Architecture - KDE Community Wiki