+972 52-548-6969
A session that I would like to see
time to read 1 min | 76 words
I get to see a lot of session listing about new technology, and I am getting tired of getting of seeing the entire list filled with new technology, as if that is the most important thing. I stole the idea from Udi, but something that I would like to see in those conferences is a talk like this:
Designing For Forward Comparability - or, what to do the next time MS changes the data access paradigm
Comments
<golf clap />
Being someone who has gone through DAO/RDO/ODBC/ADO/ADO.NET over the years I'd know what you mean.
My default answer:
Ignore it and wait for something good. Ayende will usually break it into a million pieces shortly before or after its release. ;-)
Seriously though, if I used everything as it came prepackaged from Redmond, I'd shoot myself. There has to be something built around it before I even want to touch it (unless I'm blazing the new trail). Otherwise you just get trapped in a tarpit.
Answer: ignore it, because something better is already out there.
I have been asking myself who they have in mind when they come up with some technologies for lately especially the .NET Framework 3.0 and some of the P&P bits.
[)amien
@Evan
Out of curiosity, do you have the same attitude towards OSS offerings?
@jdn,
I have the same standard for tooling from any vendor, regardless if it's OSS or not. If it causes more pain than good, it quickly gets tossed. Generally speaking, the MS stuff is very hard to toss (ie.. WebForms, ADO.NET, etc), so if it causes pain, it gets wrapped and/or abstracted. Testability and Maintainability are my biggest concerns for developer pain.
Comment preview