OnlyMortal

You write code to fit the immediate business need and that shifts rapidly over a year or two.

If you do otherwise, you’re wasting your time and the money of the enterprise you work for.

You cannot see the future however smart you might be.

The likes of Copilot are ok at boiler-plate if it has an example or two to follow. It’s utterly useless at solving problems though.

I’ll get my coat.

Nonsense!

Source: Engineer

Admittedly this was from a Dr Karl podcast.

We were given old Macs running Classic to run Notes so we had two computers. One being MacOSX. Notes was the biggest pile of crap I’ve ever had to use. With one exception…

On the OSX box we were happily running svn until we were forced to use some IBM command-line system for source control. To add insult to injury, the server was in Texas and we were in Boca Raton (old PC factory as it happens). The network was slow.

It had so many command-line options a guy wrote a TCL for it.

Adding to that was the local IBM lan was token ring and we were Ethernet. That was fun.

Identifying similar blocks and, maybe sub-rechunking isn’t something I’ve ever considered.

It came with a UK language model as the US model didn’t recognise my accent.

I recall seeing IBM ViaVoice X on shelves a Circuit City. It was rather an ego trip.

If memory serves, this was with MPW C or maybe CodeWarrior.

You could see the jump (jmp) instructions use short jumps rather than long ones.

With knobs and buttons, you can feel for them whilst still having your vision in the road.

This must make it safer to drive.

As a MX5 (ND) driver, even having a knob to scroll around the screen is a poor design choice. Touch would have been better (you can hack that) whilst driving but, frankly, this kind of car shouldn’t have a screen at all. It’s a driving car, not a home entertainment system.