> That's a problem with specs, the most concise and complete way to write them is by writing your program.
I've never dealt with formal specs/design, certainly nothing like those described here. Your comment (however in/accurate) strikes me as interesting and leads me to wonder...
What if we took the code and processed it to generate a "spec"? (I quote "spec" here b/c I wouldn't consider it a spec, but don't know what else to call it.) Basically, a document that explains verbosely what the written code does... hopefully in a way that is reasonably, humanly digestable.
Then we might get a doc that says, "Function add(...) accepts two integers/nulls and returns the sum." And Joe-coder looks and realizes it shouldn't accept nulls, goes back to the code, fixes the issue.
This is essentially what static code analysis attempts to do. Unfortunately, there are many ways of writing programs that today's static code analysis cannot understand.
If there was a rule that functions could only return named variables (vs expressions that evaluate to a value that is returned) it would get closer to "this function accepts paramName1 and paramName2 and returns sumOfParams".
White on orange is not great for readability. Especially the calculation results block which animates from white on orange to white on pale-orange: even less readable.
Mostly self-taught: BASIC/ASM on a C64 using the Programmer's Reference and Compute!'s Gazette. Taught myself C on a Mac Plus by writing a game over winter break during my first year at university.
There's so much documentation available now (more than was available years ago) for so many open-source and free resources out there.
For me, though, the biggest assist to really learning something is having a project. Whether it's at my employer or a personal thing, a project drives me much better to learn something than documentation alone.
I learned C over 1990 Christmas break from university. At home, I programmed my father's Mac Plus and wrote a game similar to Light's Out but on a playfield not a square grid.
Would this be a good tool for finding air leaks (i.e. cold air coming in during the winter) in an old house? I might drop the $200-300 for one of these if it will help me find all the leaks.
Even better if the $40 Adafruit one mentioned elsewhere (https://www.adafruit.com/product/3538) worked just as well, once configured/programmed adequately.
I bought one for that purpose. What it does best is show you relative temperature levels, which you can then investigate further to see if they're real or not. In my experience, some are actual air leaks, some lack of air circulation, and some lack of backing insulation.
Yup, definitely agree. I've got one of the Seek Thermal units, and while the absolute temperature measurements aren't always that accurate, the relative temperature measurements are fantastic for finding hot/cold spots.
In Chrome (103.0.5060.114), after a few attempts, the game became very lagging/low framerate that it was mostly unplayable.
Nice simple clicker!