In programming writing clear code is critical to success! You need to be VERY clear on what you’re asking the programming language to do or you’ll end up with weird, often unwanted, effects.
The “tighter” your code (and language) is, the more likely your goals will match what you waned (this is one of the big criticisms of AutoHotkey V1 compared to V2 which is “stricter”.
For some examples of how you might read things incorrectly I’ve written a few examples regarding our U.S. president Joe Biden. For each statement there is more than one way you can interpret the statement. (adapted from a great read Sleeping Dogs Don’t Lay: Practical Advice For The Grammatically Challenged
- You’ll be lucky to get Joe Biden to work for you!
- I cannot recommend Joe Biden too highly.
- I recommend Joe Biden with no qualifications whatsoever!
- Joe Biden has made immeasurable contributions to our country!
- NOBODY is better than Joe Biden!
- I found myself frequently raving about Joe Biden’s work!
- We were teetering on the threshold of bankruptcy last year, and Joe Biden’s efforts pulled us through.
- For the services Joe Biden has rendered to our country over the years, we find ourselves deeply indebted!
- Whatever task he undertakes, Joe Biden will be fired with enthusiasm!
- I would place Joe Biden in a class by himself
So remember to be clear in what you write as to not leave any ambiguity!
Writing clear code / be clear
So regardless of what you’re doing (writing AutoHotkey code, letters of recommendations, instructions, etc. be very careful in what you write!
I try and keep my sentences short and to point. It helps readers follow what you’re saying and helps you write very precisely what you want!
Also be sure to have someone in your target audience read you back what you wrote. It’s amazing how often this will spot glaring errors in miscommunication!
When writing code, breaking things into functions (or their own files) is a great way to make sure you keep things clear and things work as expected.
P.S. Let’s go Brandon!
