Where we find out what Dave will be talking about, and maybe get
enough information to form an opinion as to whether it might be worth
paying attention to or if it's just a bunch of mindless blathering.
I'm Dave. And, well... this is my blog. But you probably already
knew all that.
What's it all about
So.. the title.. "Shift your paradigm!" Just what do I mean by that?
It's an exhortation based on the idea of a "Paradigm Shift". OK, some
of you may be saying, what exactly do you mean by that? It goes back
to Thomas Kuhn in 1962 when he wrote "The Structure of Scientific
Revolution". In that work, Kuhn put forth the idea of the Paradigm
Shift to illustrate scientific advancement: "intellectually violent
revolutions" that occur occasionally. His observation was that
scientific advancement was not evolutionary, but rather it was
revolutionary. With periods of calm, slow, evolutionary advancement,
separated by these rather violent revolutions. These revolutions are,
or involve, a paradigm shift: a change from one way of thinking to
We can see various paradigm shifts if we look back at
history... agriculture (nomadic hunter/gatherers to settled
crop-growers), Copernicus (earth-centered to sun-centered), Einstein
(Newtonian physics to Relativistic/Quantum physics), The printing
Now what's all this got to do with software (and if that didn't occur
to you, you may well be here by accident). Well... there are several
examples of paradigm shifts in the recent history of computing (albeit
not as earth shattering as, say agriculture.. but some on the scale of
the printing press maybe):
the transition of the computer from being (in a) special room to
being on your desk... on your lap... or in your hand.
object oriented programming
textual to graphical interfaces
and (based on much of, maybe all of, the above list) pretty much
anything Alan Kay has done
Nice history lesson... but what about this blog?
Right.. I was getting to that.
What I want to do here is explore and talk about neat stuff.
Specifically, that subset of neat stuff that has potential to
fundamentally change how we, as programmers, do our thing... that
So, I'll be talking about new languages (and some old languages that
were ahead of their time then but aren't now), new techniques,
technologies, ideas, processes, and practices.
Some examples? OK. Here are some that a flitting about my mind as
Dynamically typed languages like Smalltalk, Python, and Ruby
Agile Software Development
Aspect Oriented Programming
and well... lots of stuff I haven't found out about yet.
Hopefully I can occasionally (I'll be quite happy with once)
introduce you to a new idea that will change how you program in a
revolutionary way. A bit much to ask? Maybe. But sometimes the
simplest idea can have incredible effects.
I'm planning to have fun writing here, and I hope that you have fun
reading. I won't be getting things proofread or copy-edited before
posting... though I will run a spell-check when I remember to.. and
I'll try to remember what I learned while sleeping through grammar
lessons. This'll be fairly "off the cuff". A thin wrapper over what
I happen to be thinking about or playing with at the time. Oh, and
I'll post little announcements regarding where I'll be speaking, or
conferences I'll be attending, and so forth.
Dave has indicated that he has no plans to get a haircut.. or a real job for that matter. All of this has given his parents great angst in the past, but they're over it now.. having given up all hope in these matters.
> Also, is it true that Dave was sighted eating meat at a > hot stand in Halifax recently?
That is uncategorically untrue. Dave, in fact, has not been in Halifax recently... not since April in fact.
However, we have it on good authority that Dave was sighted eating Alligator in New Orleans earlier this week.
> Also, what insights can Dave provide in the context of > junit data setup / teardown re: tools et al for enterprise > applications spanning multiple dbs.
Well. not really. Isolate yourself from the dbs. Fake 'em... Mock 'em.. do what you have to. Dbs are an implementation detail and should have no impact on your business logic.
> And when is dave getting a haircut?
That question has been dealt with and we have no further comment.