Anyone who refuses to compile an open source project under any circumstances doesn’t really believe in open source: they believe in other people working for them for free.
Being considered the best speaker in a computer science department is like being known as the tallest of the Seven Dwarfs.
This is from Randy Pausch The Last Lecture book, I got it yesterday and find it really hard to put it down.
I wrote this today while discussing configuration mechanisms with my colleagues.
I love the unixish way of configurating things because the configs are:
The opposite of this is the M$ hell of opaque configurations managed by (sometimes even more opaque) GUIs, and unfortunately Sling leans more towards that opposite at the moment. We’ll have to fix this.
I’ve been getting at least one, if not several invitations for new social networks every day lately.
So, please don’t feel offended if I ignore them, it is sometimes hard to select between timewasters and…more timewasters ;-)
(seriously: some of this stuff is very useful, but as with any new tool it looks like we’re in the explosion of new offerings phase right now).
Example isn’t another way to teach, it is the only way to teach (Albert Einstein).
Sounds so obvious…you don’t teach babies to speak by explaining how to move all the organs involved in speech: you start by talking to them, and once they get the basics you explain a bit and move to the next stage of examples.
Using automated tests as reference documentation means that the docs will always be in sync with the code – assuming you’re using continuous integration to run those tests often.
People might object to having to read source code, so maybe creating a filter that presents the code in a nicer way would help?
Literate programming for test cases…the idea sounds worth pursuing.
I’ve been listening to a few podcasts recently, which were obviously recorded using Skpye or another VoIP technology. Probably Skype, judging from the bad voice quality – my SIP phone sounds much better than that, but of course SIP is not always practical.
The problem is that it’s usually the interviewer who records the conversation, so it’s the interviewee’s voice quality that suffers, although it is in most cases the one that we want to hear.
How about recording both side’s voices locally, and mixing the two at post-production time? That’s a bit more work, but aligning the two tracks on an initial pulse or beep should make it easy to get the timing right, and depending if the recordings can be reasonably isolated, not much more processing would be needed. Worst case, you’d have to adjust each track’s volume according to who is speaking.
That wouldn’t work for interviewing people who don’t have a clue how to record their own voice, but geeks should manage ;-)