What’s on your mind?

[bousozoku]

Which Mac was it? Of course adding extra memory cards even to the soldered in ones is hard.

Lots of things earlier but now with modern IDEs we get code completion, AI pair programming, and even other things to automate writing tedious things versus reading Stack Overflow threads and scrolling for answers...

My first as the Performa 476, which was an LC475 with a 230 MB hard drive compared to 160 MB drive, but had the Motorola 68LC040, which didn't have the maths co-processor. I spent the money to buy the full 68040 25 MHz processor and boosted my 4 MB of RAM to 36 MB. I doubled the money I put into it with just those two pieces.

Working on enterprise-sized machines was easier for me to develop software. The stability of the operating system and the interfaces was incredible. The development environment was useful but not always the most productive.

I ended up writing extensions for our batch/scripting language that added While, Until, and Case, and the interpreter to spit out code the compiler could handle.

 

[goldmac2006]

My first as the Performa 476, which was an LC475 with a 230 MB hard drive compared to 160 MB drive, but had the Motorola 68LC040, which didn't have the maths co-processor. I spent the money to buy the full 68040 25 MHz processor and boosted my 4 MB of RAM to 36 MB. I doubled the money I put into it with just those two pieces.

Working on enterprise-sized machines was easier for me to develop software. The stability of the operating system and the interfaces was incredible. The development environment was useful but not always the most productive.

I ended up writing extensions for our batch/scripting language that added While, Until, and Case, and the interpreter to spit out code the compiler could handle.

Got it.

Even in some computer science classes, one of which was C++, I was required to document the code in a specific manner. Like comments, etc. As a result, I maintained a collection of comments pinned to my clipboard history. This included for loops like the one you demonstrated through batch execution, as well as the common public void methods in Java that accept a string array. Switch cases were also particularly tedious for me, including loops, so I kept some essential parts of them in my Universal Clipboard.

 

[scubachap]

As we’re talking about toasting (bread and CDs)… remember these…

 

[bousozoku]

Got it.

Even in some computer science classes, one of which was C++, I was required to document the code in a specific manner. Like comments, etc. As a result, I maintained a collection of comments pinned to my clipboard history. This included for loops like the one you demonstrated through batch execution, as well as the common public void methods in Java that accept a string array. Switch cases were also particularly tedious for me, including loops, so I kept some essential parts of them in my Universal Clipboard.

I professor talking about documentation. Be still, my heart.

I was migrating some code for a screen design application back when text displays were more common than graphics displays. Out of all of the source modules, I found one comment in a function called kibbles_n_bits() and the comment looked like /* kibbles_n_bits */ which was extremely helpful. Everyone else who was coding had recently graduated from Drexel University or the University of Pennsylvania. Apparently, there were no classes on style or documentation.

As I had been working on bigger machines where maintenance was as important as new development, documentation was necessary. I was a bit surprised.