Jeff's Ranting Ground

For those of you who are techies at heart, I'm sure you know what MIMO, FIFO and their siblings are. For those that aren't, it's as follows.

• FIFO - File in, File out (like a queue)
• MIMO - Multiple input, multiple output
• WORO - Write once, read once
• WORM - Write once, read many

I've now started writing C# code for smart-devices. What does this mean? Windows mobile devices, things running Windows CE and Windows for Embedded Systems, all .NETtified to make the transition ultra sleek. The problem? The code looks damned ugly, and not through any immediate fault of mine. Sure, I could find ways of making it more readable, but compared to nicely streamlinable languages like PHP with loose types and associative arrays at your beck and call, I'm reduced to some nasty instances of multiple-type-casting to get the IDE to work properly, and all sorts of embedded function calls so I don't have to assign memory to a variable where it isn't needed.

Hence, my new standard, WONTRA. Write once, never try to read again. Once I get this code working, I think I'll happily forget it ever existed, and go back to blissful ignorance in languages that are a little easier on the eye