Skip to main content

Posts

Micro$oft is FAT!

Judge Kathleen Kottler-Kavein ruled that Microsoft must be broken up into two companies. The name of the two companies will be MICROS~1 and MICROS~2. HAHA!! The Bug: (not in reference to the car or the insect) So... today I stumbled upon something weird with FAT16 partitions. Why FAT16? Because the manufacturers of the SD memory card formatted the card with FAT16... your own USB flash drive might also be FAT16. Anyways... here's what happened: I had 126 files (totaling over 1.4 GB) on the SD card. If I added one more file, Windows would complain, saying that it could not create the file. And, here's the strange part... if I deleted a 4 MB file and copied a 1 MB file, it would still not let me create a new file. And, even stranger... if I deleted all of the files and created 1000 small files, it would let me. So... the problem doesn't seems to be a file size limit or a # of files limit. What is it then? WTF, mates? Here's a strange bug in FAT16: http://www.cocoa...
Post a Comment
Read more

Java is Disappointing Sometimes...

What's Java's number one problem?  If you said "efficiency," then you win!  Why do we still use C and C++?  If you said "efficiency," then you also win! And so... yesterday, we learned about templates and generics and so forth, and I was able to ask a question that's been bugging me for quite some time.  "When you declare an ArrayList<Integer>, are Integer Objects being stored internally, or are primitive ints being stored?" Prior to yesterday, I had given this quite a bit of thought, actually.  I'd say about a year ago, I determined that since the classes like Integer, Byte, Float were final, non-inheritable classes, that Java could actually optimize the language by artificially storing primitive ints, auto-unboxing and auto-boxing them, as appropriate.  But, as it turned out, I was wrong! Java does not do that.  Instead, when you store a bunch of "primitive ints" in an ArrayList<I...
Post a Comment
Read more

Headaches

Writing computer software sometimes goes a little something like this: Brainstorm Believe that writing software is easy Design Change the design Bang your head against the wall Wish you hadn't banged your head against the wall... ouch... Change the design... again... Write some senseless code Wake up the next morning and delete the senseless code Write gibberish on a whiteboard Erase the whiteboard Realize that your gibberish was actually somewhat important Finally get a design together Write some senseless code COMPLETELY SCRAP THE DESIGN AND THE CRAPPY CODE! Draft a decent design Write bad code Realize the code sucks Fall asleep on your keyboard Wake up at 3 AM and realize you did nothing except type 2000 pages of the letter L. Bang your head against your pillow... ahh... better than the wall.  Commence sleeping. Hide underground and crank out some code Attempt to compile code Add include statements and the semicolons you forgot.  Attempt to compile code... round 2 Begi...
Post a Comment
Read more

Today's Quote

This is simply a brain dump.  I'm sleepy, and I want to type out some of the thoughts currently in my head. "Luck is where preparation and opportunity meet."  This is so remarkably true, and today I'm making it a mantra.  I believe that luck is merely an illusion that we perceive, but it truly when we have prepared ourselves for the right opportunity... and then a great opportunity comes along.  Many great opportunities pass us by every day.  Once we begin to recognize them and prepare for them, then we start to experience the thrill of luck. Interestingly, as described in "Good to Great", Mr. James Collins talks about how "Level 5" leaders often attribute their great success to luck .  That's a humble way of saying, "I planned on taking advantage of every opportunity ."   Hmmm...
1 comment
Read more