A book, which to buy?

W

wyrd

Senior Contributor
Joined
Aug 23, 2002
Messages
1,405
Location
California
After cleaning up my desk and counting all of the change on it, I discovered that it calculated to about $40. With this I plan on buying yet another book, unfortunately I can't decide which one. Here are the two books in which I'm debating on;

http://www.amazon.com/exec/obidos/tg/detail/-/0201633612/103-7781093-4373435?v=glance&s=books
http://www.amazon.com/exec/obidos/t...=glance&coliid=IQJGBM6EYT9PD&me=ATVPDKIKX0DER

If it helps at all, I already have one book on Transact SQL which happens to be Ken Henderson's The Guru's Guide to Transact-SQL. I do not however have any books on Design Patterns.

Suggestions? :)
 
As I remember you are programming stuff for fun during your vacation. I would go for the Design Patterns Book, because there is only so much SQL Server stuff you can learn without being in a business environment.

Juding from previous posts and the fact you have a book on Transact SQL you know the basics. Design Patterns are something, which are easy to put into use now, and sounds more fun developing frameworks for common business problems.

Certainly an area I am thinking of focusing on next...
 
As I remember you are programming stuff for fun during your vacation.
Click to expand...
Some for fun, some for learning. The primary goal is to to do both equally.

because there is only so much SQL Server stuff you can learn without being in a business environment.
Click to expand...
Isn't this true for just about everything? Can you please clarify?

Juding from previous posts and the fact you have a book on Transact SQL you know the basics.
Click to expand...
Well, yes, but I'd like to go far beyond the basics. Hence the name of the book. :) The one I already have by the same author (Ken Henderson) is most excellent, I recommend it to anyone who's looking to fine tune their Transact SQL skills and learn some neat tips and tricks. Make no mistake about the "Guru's Guide" in the book title.

Design Patterns are something, which are easy to put into use now, and sounds more fun developing frameworks for common business problems.
Click to expand...

I'd probably find both equally fun. Writing classes that are abstract enough to reuse in multiple programs intrigues me, as well as learning to actually program in Transact SQL which goes far beyond queries (yes, I consider Transact SQL a programming language)

So you can see I'm pretty split between the two.
 
Wow, only one response so far? :eek: Are my choices so equally good that no one can offer up any suggestions, except one brave soul? :D
 
because there is only so much SQL Server stuff you can learn without being in a business environment.
Click to expand...

Some stuff just isn't possible with limited resources, some stuff just doesn't seem to make sense why you would need to bother, well thats what I found anyway.

Take database tuning for example now I'm no SQL expert, but have mucked about with tuning databases on my home system, but in a business environment there are many factors, which I hadn't come across when tuning a database and it turned out to be a much more complex activity than I first thought requiring much of our DBA's time.

Not to say you can't learn it... Design Patterns strike me as something, which would be very beneficial. You will be amazed in business environments how much work is redone on each project because you never have the time to design a decent base framework, I have attempted it numerous times but with work loads you never get around to introducing it.

But it is something which you can muck around with limited resources, and produce some good design patterns to solve common problems.

For example: -
1. navigational elements on forms and only allowing access to users of appropriate security level.
2. database search forms, development of a generic search pattern to allow searching of multiple criteria.
3. base design for all systems allowing creation, deletion and ammendment of data and undoing of actions (see Rockford Lhotka's Component Scalelable Logical Architecture)

But your right both are interesting subjects, was just being biased my favorite is design patterns, more fun.
 
I'm going on vacation again. Not a Carribean island this time. Just a lake in Tennessee, but I'm going to need another book that will cause others concern for my mental well being. I don't own the Design Patterns book so I'm going to pick it up for the trip. I'll compare notes with you in a week or two Wyrd. Go to public places while you read, carry it with you in the mall, to the movie theater, out to dinner, on dates....see what a great conversation starter it is (or not).

Jon
 
jfackler: Eh?
Robby: *blink*

dsgreen57: Every bone in my body is screaming "get the SQL book!" Of course I'm being biased as well as it's my current love interest in programming ATM. I keep telling myself that I need to wake up to reality and learn more in a more broad manner until I get a job, because who knows what langauge(s) I'll be programming in when I do get one.

John Dewey was right, humans are an emotional animal.
 
Sadly enough I'll probably break down and buy both, even though I shouldn't because I don't have the $$ for two books and there's an Xbox game coming out next month that I may buy. :(

Decisions.. decisions.
 
Okay, decisions were made. I decided that despite my emotions I'm going to buy books that will help me become a better programmer in general, rather then limiting myself to one aspect of programming. I must try and widen my knowledge until I get a job, as it's impossible to predict what sort of programming job I'll end up getting in the future (I still have 2 years of school left, at least). I also felt that I should work on reusable and quality code rather then trying to master a language. After all, mastering a language is just a matter of time, but creating reusable and quality code (hence quality software) takes practice and dedication.. right? Probably not, but that's how I'm justifying my purchase and I'm sticking to it! :cool:

Oh.. and aside from Design Patterns, I decided to buy Code Complete. For only 25 bucks and the rave reviews on Amazon.com, how can I go wrong? Anything to improve my coding techniques is worth the $$ I'd say, because I can tell you after the mess I've been through with my current program, I could use the advice. It's such a mess that I'm not even sure if I'll post it here on the forums when it's done. *beats self with stick*

Okay enough rambling.. here's the link for the Code Complete book if anyone cares;

http://www.amazon.com/exec/obidos/A...5543287/sr=2-1/ref=sr_2_1/103-7781093-4373435
 
The greatest thing I've done for my reading is take the train to go to work, 30 minutes each way. In four months I read three books between 1200 and 1500 pages each. By the end of the year I'll have read every Wrox book. :)
 
Back
Top