Not sure how I feel about the guy...sometimes he irritates me and others...not so much...I can't see he's ever amazed me or wow'ed me...but the following article on abstractions being...well...ummm...not so good...
I found the article interesting...despite being a *huge* advocate for forward thinking and abstraction...everything I do I try and further abstract...so it bugged me to read his cynicism's on abstraction...but there are a few valid thoughts...
In anycase...interesting read, incase you haven't read it already...
http://www.joelonsoftware.com/articles/ ... tions.html
Disscuss??? Comments, experiences, opinions, etc?
Joel on software
Moderator: General Moderators
-
alex.barylski
- DevNet Evangelist
- Posts: 6267
- Joined: Tue Dec 21, 2004 5:00 pm
- Location: Winnipeg
-
Charles256
- DevNet Resident
- Posts: 1375
- Joined: Fri Sep 16, 2005 9:06 pm
I don't think so unless http://www.joelonsoftware.com/AboutMe.html is a cover-up 
I agree with the article. It's not against abstraction in general but you should keep the perspective.
I agree with the article. It's not against abstraction in general but you should keep the perspective.
-
Charles256
- DevNet Resident
- Posts: 1375
- Joined: Fri Sep 16, 2005 9:06 pm
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
I learned about Joel from his "Absolute minimum every developer must know about Unicode" article. I'm not sure how much I learned from that article, but concerning this one...
...I did enjoy the analogy for TCP/IP.
Seriously though, I agree with what Joel is describing, although I'm still a little iffy about his motives: his strong belief that you need to be very familiar with the low level workings of a system before you work at a higher level. Maybe that's because I don't want to learn C++, but what he's describing is definitely true, and should definitely be factored into your decision making process before you use an abstraction.
...I did enjoy the analogy for TCP/IP.
Seriously though, I agree with what Joel is describing, although I'm still a little iffy about his motives: his strong belief that you need to be very familiar with the low level workings of a system before you work at a higher level. Maybe that's because I don't want to learn C++, but what he's describing is definitely true, and should definitely be factored into your decision making process before you use an abstraction.