Have you read these?

Not Active

Ennis Ray Lynch, Jr. wrote:

rather than apply critical thinking he or she will blindly apply patterns even if they are inappropriate

Is this fault of the book or its authors though? This can be said for just about anything. VB allowed low caliber developers to think they were good. There are great books on database normalization but when it is taken to extremes in can decrease performance. The trick is to understand the concepts and know when, and when not, to use them. Don't shoot the messenger.

I know the language. I've read a book. - _Madmatt

Vark111

I've read the Requirements book. Haven't read McConnell's Pro Software Development. Is it much different from Code Complete (which I have read - and recommend)?

Not Active

I don't know whether to laugh at the ridiculousness of this statement or cry at what is happening to our industry that produces such thoughts

I know the language. I've read a book. - _Madmatt

Not Active

Trollslayer wrote:

I give a copy to my intern each year

Doesn't your intern get tired of receiving the same book every year. ;P

I know the language. I've read a book. - _Madmatt

Nemanja Trifunovic

Mark Nischalke wrote:

which do you recommend as essential guidance for our profession?

Structure and Interpretation of Computer Programs[^] Writing Solid Code[^] (old, but still very relevant) Code Complete[^] Writing Secure Code[^] The Art of Computer Programming[^] (as a reference) Advanced Windows Debugging[^] (of course, only for Windows developers). Elements of Programming[^] There are many other good books that are language/technology specific, so I won't mention them here.

utf8-cpp

Ennis Ray Lynch Jr

It doesn't matter whose fault it is, the premise in the original post was that the book benefits our profession. It does not. Although, I have not read it, "The Mythical Man-Month" has been almost universally praised as being a benefit to our profession.

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost

Not Active

It is more about the development of the software developer them-self rather than the code they produce.

I know the language. I've read a book. - _Madmatt

modified on Thursday, December 30, 2010 10:31 AM

Ravi Sant

I haven't heard, seen or read any of two books. But, one book, i would recommend developers is: » The Pragmatic Programmer: From Journeyman to Master It is a wonderful book :) Also, i like to read several books on design patterns and uml, beside this.

Simon_Whale

Mark Nischalke wrote:

Design Patterns (Gof)

Hardest thing I have done while learning Design patterns myself is to explain to my colleague that you design the application on paper and then see if you have an appropriate case for using a design pattern not the other way around. But otherwise I read books and Google a hell of a lot while learning new topics

As barmey as a sack of badgers Dude, if I knew what I was doing in life, I'd be rich, retired, dating a supermodel and laughing at the rest of you from the sidelines.

Dalek Dave

Heaven forfend, you are starting to sound rather cynical, unlike your usual, carefree and charitable self!

------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC League Table Link CCC Link[

Marc Clifton

Mark Nischalke wrote:

Have you read them?

No.

Mark Nischalke wrote:

What level of professional do you consider yourself?

Yoda ;) Marc

realJSOP

This IS me being my usual carefree and charitable self... :)

".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997

Not Active

Marc Clifton wrote:

Yoda

Don't sell yourself so short ;P I thought is was Pete[^] though

I know the language. I've read a book. - _Madmatt

wizardzz

My old org tried to get everyone to read a book on SCRUM. SCRUM books should be shredded and burned. Everyone interprets how it should be implemented their own way. At my old job, SCRUM just gave management another way to look busy and feel involved in the production of the company's product.

Rama Krishna Vavilala

Mark Nischalke wrote:

Software Requirements, 2nd Edition[^] by Karl Wiegers

Yes, I think code complete is the one essential book. The books mentioned on cc for different levels come next.

Ian Shlasko

Like Ennis said, I think those design patterns books do more harm than good. Good programmers see a pattern in a book and often think "Oh, there's a name for that... I've been doing that for years." This makes communication slightly easier, but doesn't improve software quality very much. If it's actually new, then sure, it might inspire some new ideas. Below-average programmers, the ones who really need the books the most, will often see this pattern and think, "Wow, that's really cool! I should start using that for EVERYTHING!" And they do. And the rest of us die a little inside, while simultaneously chuckling and groaning at the new posts in the "Hall of Shame" forum. In my experience, I've seen more of the latter than the former... Patterns are nice, but the message needs to always be "Use the right tool for the right job." And that message just doesn't sell books.

Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)

Dan Mos

Mark Nischalke wrote:

Have you read them?

No

Mark Nischalke wrote:

which do you recommend as essential guidance for our profession?

VB for dummies.

Mark Nischalke wrote:

What level of professional do you consider yourself?

Dummy chieftain :cool:

All the best, Dan

Jun Du

Many developers have gone through all the stages you mentioned, developer, team lead and architect. The distinctions between them are becoming less important. In many companies, team leaders and architects also code significantly. The difference seems to be that more experienced developers have more responsibilities and do more integration and trouble-shooting. No. I haven't read the two books you listed. Everyone probably has their own reading list. My two handy books are the Gang of Four's "Design Patterns" and Jeffery Richter's "Programming Applications for Microsoft Windows".

Best, Jun

Not Active

Jun Du wrote:

Many developers have gone through all the stages

In most cases they have not gone through these stages but rather been given the title or responsibilities. An important distinction I believe. I'm sure we can all relate experiences with a lead or architect that had no idea what they were doing and only got the position through seniority.

I know the language. I've read a book. - _Madmatt

Member 96

Never heard of them and never read them and I absolutely disagree. I consider myself quite professional having made a living on apps I designed and coded in a highly competitive market for well over a decade now. Books are strictly 20th century, anyone can learn anything they need online now and the school of hard knocks can't be substituted by any book or course of study.

There is no failure only feedback