We’re that bad type.
Make your coding sad type.
Make your scoping mad fright.
Might seduce your stack type.
We’re the bad guys, duh.
Who are we?
That’ll do.
Performant code is important, and often something that gets overlooked with the abundance of resources we have today. You’re eventually going to have a bad time if you decided on a solution that added 50 million operations to your system when it could’ve just as easily been a few hundred thousand.
Know what performs well and what doesn’t. Don’t let your codebase become the sum of a bunch of “that’ll dos”.
Know thy language.
If you say you’re proficient with a specific language, what level of understanding do you really have? Immerse yourself in the language’s internals, advantages, and shortcomings.
What do you dislike about your favorite language?
Bug relocation services now available.
When rewriting an existing application, take a deep look at all of its features, and don’t blindly squash bugs during the rebuild.
Have your users lovingly adopted any of your bugs?
The war on entropy.
The environment and systems surrounding your application will change, even when your code remains the same. Does a rarely-used filter play nicely with the new software you installed? Are some of the features you added two years ago bugs now? Left unchecked, code will ultimately descend into chaos.
Fight back entropy by becoming a good maintainer of code today!