Comments on: Episode 148: Software Archaeology with Dave Thomas

By: Lisa

Lisa — Fri, 29 Jun 2012 23:29:05 +0000

I truly believe that reading the script is very important to write an effective code. Well, it is not that I am an expert in the field but I feel it is truly sensible. Anyway, after finishing my essay through the help of topessayservices.com, I plan to study html and website creation too.

By: 031 RR Code Reading

031 RR Code Reading — Fri, 02 Dec 2011 17:48:40 +0000

[...] Software Archaeology with Dave Thomas [...]

By: 034 RR Code Reading

034 RR Code Reading — Fri, 02 Dec 2011 00:46:03 +0000

[...] Software Archaeology with Dave Thomas [...]

By: Peter Pilgrim :: Java Champion :: Enterprise Blog » JavaOne 2011 JavaFX 2.0 Demonstrated on iOS, Samsung Galaxy Tab and Acer Windows Tablets

Wed, 05 Oct 2011 14:10:26 +0000

[...] Oracle’s strategy is to get Java ME, Java for embedded and Java SE to converge, because want to reduce the number of Java virtual machine Hotspot implementation to at least three codebases. With the modularisation piece in Jigsaw, and a modular HotSpot engine they can swap in and out the necessary adaptation for target devices. Seen or heard something like this before? I think some of you already have, if not then go and listen to Software Engineering Radio podcast, I suggest the episodes on Feature Oriented Software Development (Episode 172 and 173 of SE Radio with Sven Apel) and Product Lines (Episdoe 153 Jan Bosch on Product Lines Software Development) and I also think Software Archaeology (Episode 148 Dave Thomas). [...]

By: Rick Umali

Rick Umali — Tue, 28 Jun 2011 23:49:32 +0000

This was a very interesting episode. One of the insights from Dave Thomas is that “code rots”. Over time, assumptions and inputs can change, and the unit tests for code that is unmaintained can often begin to fail.

By: Jazz Lessons and Static Inner Classes | Code Cheese

Jazz Lessons and Static Inner Classes | Code Cheese — Wed, 20 Oct 2010 06:09:39 +0000

[...] This idea lends itself to Dave Thomas thoughts on software archeology. [...]

By: rfl4711

rfl4711 — Thu, 01 Jan 1970 00:00:00 +0000

… since there’s links to the prags, I guess this is PragDave this time (as opposed to OTI Dave). Right?

By: BramVanOosterhout

BramVanOosterhout — Thu, 01 Jan 1970 00:00:00 +0000

Thoroughly enjoyed this episode. Thought Dave was a bit hard on comments, but he fully redeemed himself with the statement: “Comments about ‘why’ are helpful” And so are “Comments that direct me to other relevant locations”

Also liked the references from this podcast. Could do with more. The ;;;; collaps is a neat idea.

Thanks again.

PS. Your CAPTCHA may be very safe, but I had 5 gos to get it right. Case sensitive is not easy if you dont have a base because the letters dance. The difference between Y and y is where they are positioned on the line. the shape is almost identical.

Bram van Oosterhout

By: Volker

Volker — Thu, 01 Jan 1970 00:00:00 +0000

Yes, this time it is PragDave.

By: Jbc1

Jbc1 — Thu, 01 Jan 1970 00:00:00 +0000

I was really disappointed with the sound quailty of this episode. There was a really annoying knocking noise in the background when Dave was talking. Shame really, as it’s very interesting otherwise.

By: jtkim

jtkim — Thu, 01 Jan 1970 00:00:00 +0000

I very much like the recommendation of reading the source of that which you use (Ruby, Perl, Python etc.). I’d like to add one recommendation, though: Don’t use quirky ways of coding in an interpreted language just because you found out from the source that they work with the current implementation of the interpreter. I may be stating the obvious here as such exploitations of quirks may, in time, turn into some future software archaeologist’s nightmare.

“Beware of evil wizards” — yes!! Personally, I find those who use generated code without understanding it are really the evil ones. In fact, writing a wizard that relieves coders of writing boilerplate code is perhaps misguided (as the root problem that ought to be fixed is the requirement of having all that boilerplate code), but using anything you don’t properly understand is always a step towards a dark age in which superstitions flourish.

By: weberdc

weberdc — Thu, 01 Jan 1970 00:00:00 +0000

I agree there are a few annoying buzzes and clicks and a few echos (presumably from mixing input from two microphones) but it’s perfectly intelligible. I also listen to the BrainSciencePodcast (.com) and some of the early (and even mid) episodes of that have dreadful audio, so this episode really isn’t so bad.

I found it really interesting and will be looking around for code to read. I’d really appreciate some links on repositories of good code, as was discussed in the episode. The book and article are interesting, but more recommendations of code to read would be great.

Thanks and keep up the great work SE Radio.

By: AlessandraFox

AlessandraFox — Thu, 01 Jan 1970 00:00:00 +0000

the way PragDave carried himself. He was totally awesome and at boring at the same time but you'll definitely say that he knows a lot of things. I was actually doing my paper writing when heard about PragDave.

By: adamholmes

adamholmes — Thu, 01 Jan 1970 00:00:00 +0000

So while software archeologists try to imagine how a system might work or have worked, we Smalltalk developers have the luxury of just starting the system up and live in there for a day or two. Since this episode was released, there have been a lots of reactions mentioned and sample essay came out all over the net. Interesting. Absorbing.