Re:What I Learned from Watching Notch Code
by pnathan on Tuesday September 13, 2011 @09:32PM
(#2994493)
So I was working on developing a multicast serial driver. Since I was developing the serial driver, I had to take... over... communication... from the copied-from-ROM driver.
And since there was only 1 working communication port, how did I debug? How did I even run a test?
The board I was developing on was amazing. It had 1 (one) LED.
Blink.
Blink.
Blink (fast).
Re:What I Learned from Watching Notch Code
by JonnieCache on Wednesday September 14, 2011 @05:22AM
(#2995479)
You should have just taped a photoresistor over the LED and serialized your error codes back into your dev box with morse code.
But I guess then you'd have to debug that code and you'd be back where you started.
Re:What I Learned from Watching Notch Code
by shabble on Tuesday September 13, 2011 @11:57PM
(#2994824)
This setup is almost exactly like the one in which I first learned C (it had a massive 2048 bytes of SRAM!).
As a bonus, it used a dodgy proprietary compiler with a whole sack of undocumented "technical limitations."
The good part is I now have a really good understanding of pointer manipulation. The bad part is using it sometimes makes me twitch.
Edit: Here's someone who's got us both beat: http://web.archive.org/web/20070613032334/http://ipodlinux.o...
Re:What I Learned from Watching Notch Code
by mdwrigh2 on Wednesday September 14, 2011 @08:59AM
(#2996057)
What specifically would you like to see in terms of testing tools for Android? I ask this not because I don't think there are areas to improve (there are), but to get a better idea of where improvement is most needed.
Re:What I Learned from Watching Notch Code
by chrisrhoden on Tuesday September 13, 2011 @09:00PM
(#2994401)
Java has good unit testing frameworks. Try Obj-C/Cocoa.
* possibly an exaggeration, but it's definitely very very bad.