|
|
|
Sponsored Link •
|
Summary
Yes, that's the question we should all be asking ourselves.
|
Advertisement
|
I saw this the other day. It seems like this issue has come up periodically. I find it incredibly boring.
I saw this today. It seems like this issue has come up periodically. I find it incredibly sad and embarrassing.
Perhaps, just perhaps, it's time to raise the level of discourse in the industry. It seems to me there is a lot more fun to be had figuring out how to build working systems that are elegant, useful and extendable than in building yet another damned persistence layer for some language that happens to be in vogue because it's, say, dynamically typed.
I think I can safely say that none of the real problems I face have much to do with the fact that I need to do casts, or the fact that I can't express something with less typing or whatever. In fact, none of the problems I face have much at all to do with the language I'm using. No, the problems I have now are the same problems I had 15 years ago. Reducing complexity, increasing robustness, enhancing expressiveness. Stuff like that. I suppose it's possible I'm missing something, but I don't see any language that helps me with those things at the fundamental level I'm looking for.
Perhaps that's why I'm not a Thought Leader.
Have an opinion? Readers have already posted 6 comments about this weblog entry. Why not add yours?
If you'd like to be notified whenever Rick Kitts adds a new entry to his weblog, subscribe to his RSS feed.
| Rick Kitts has been making a living writing software for a little while. He's started a company or two, worked at bigger companies, but mostly at startups. Constantly on the look out for things to help him build better systems he's a bit of a tool and process slut, though he can't bring himself to try C# or get serious about UML. Go figure. He's convinced being invited to have a weblog on Artima is the result of some glitch in the matrix. He's keeping quiet about it though. |
|
Sponsored Links
|
Digg
del.icio.us
Reddit