Omega0 (![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small} omega0) wrote,@ 2008-11-21 19:34:00 |
|
Random Things.
Downloaded the new version of the PIC-Lite. It now supports about a hundred different microcontrollers. So without any compelling reason for sticking with the 16F690 I have a lot of datasheets to read.
Car gas gauge will cost too much to fix. Replacing it "260 miles = dead meat" on a post-it note.
Microsoft Outlook is evil. At work I switched over to it from Outlook Express since our current client sends a lot of Outlook-format meeting notices. Now I'm hooking on the program by a combinations of reliance on its useful features and curiosity of what the extra buttons do.
and to fill out the post, Screw Java! Why does a JComboBox's Constructor require a Vector or Array when any Collection will do? Heck, why doesn't JComboBox use generics in the first place? It wouldn't break the interface for old code.
Downloaded the new version of the PIC-Lite. It now supports about a hundred different microcontrollers. So without any compelling reason for sticking with the 16F690 I have a lot of datasheets to read.
Car gas gauge will cost too much to fix. Replacing it "260 miles = dead meat" on a post-it note.
Microsoft Outlook is evil. At work I switched over to it from Outlook Express since our current client sends a lot of Outlook-format meeting notices. Now I'm hooking on the program by a combinations of reliance on its useful features and curiosity of what the extra buttons do.
and to fill out the post, Screw Java! Why does a JComboBox's Constructor require a Vector or Array when any Collection will do? Heck, why doesn't JComboBox use generics in the first place? It wouldn't break the interface for old code.
