11,489 karma · joined March 24, 2008
Available for smaller projects (sub-80 hours), consulting, or to just shoot the breeze.
littlemachines@cedarlakeinstruments.com
Anyone?
CoCo3 came with 128k out the box though.
At my first job, we used Model I's for testing hardware. Since we were live-plugging I/O boards into the bus to test quickly, we'd occasionally kill one (they were surprisingly robust, though). No matter: there was a shelf full of them because the owner bought a pallet at a garage sale.
If I had known there was a floppy for it, I'd have asked for one. Our BASIC test code had to be typed back in if there was a power failure, or we had to get a "new" one off the shelf.
Are you serious? That's fkn brilliant!
OTOH, some items were surprisingly cheap. A couple years after college, I had a small business running out of a spare bedroom making temperature monitors and there was a shielded audio cable with connector that I used for the sensor. Radio Shack's price was about $1.50 each but all the "real" parts houses were at least 5x that.
Few things impress me more than someone using shell sizes correctly :-)
Here in MN, we have a very large population of Somali immigrants. Their children, born in MN, have a higher prevalence of autism than the ones born in Somalia. To the extent that the community has begun to call it "the Minnesota disease."
I worked on a system that sat in the railroad right-of-way and by necessity had to detect an oncoming train from at least half a mile away due to our response time. We were aware that the railroad already had the data on where the trains were, but for RR safety, there was no way that we could get access to that, so we had to place our own sensor next to the track.
You raise an interesting point that if you're near a switching point, you need to know the point's position to determine if there's a potential collision. For my system, it was placed far enough away so that was not an issue: if we detected a train, we knew it was coming our way.
Many more. There isn't a fixed amount of software needed in the world: the amount will expand to fit the capacity. There's a reason it's been consistently difficult to find good programmers: there's more work than the existing population can handle. By expanding to use AI, I expect that the amount of programming work will grow, not shrink. However, the amount of programmers may decline.
I had a hen who was sitting on a clutch of eggs this summer. Did everything right: kept them warm, turned them regularly, etc.
Then one hatched and she promptly lost interest in the rest, leaving them to die.