![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Oh my, what a throwback. Nicely done.
Oh my, what a throwback. Nicely done.
I sometimes name booleans after the action that will be taken rather than the condition they represent For example, I might have booleans called “doQuickInit” or “invertResult”. I find this very useful when the value of a boolean is determined by a complex series of conditions that are not actually true or false.
Embedded software developer here.
Oh damn, I thought I was going to be the only one here!
I don’t know how you get by with only one. Between source code, simulators/emulators, datasheets, requirement specs, log files, e-mails from senior devs with tribal knowledge not written down anywhere else, and a bunch of other bullshit, I sometimes find 3 24" monitors to be lacking.
Distractions aren’t a problem because I can easily use up all that screen real estate for a single task.
From the hovertext: “I wrote 20 short programs in Python yesterday. It was wonderful. Perl, I’m leaving you.”
After years of a dozen other languages, I finally tried Perl the other day.
Never again, if I can help it.
Everyone at Mentor Graphics did before it got gobbled up by Siemens in 2017. I don’t know if they still do.
“Chilrdren don’t already know the things they’re in school to learn about? Their brains must be rotting.”
I love this way of thinking about it.
I haven’t been interested in AI enough to try writing code with it, but using it as an interactive rubber ducky is a very compelling use case. I might give that a shot.