Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. The Lounge
  3. Have you read these?

Have you read these?

Scheduled Pinned Locked Moved The Lounge
comdesignalgorithmsbusinesscollaboration
54 Posts 25 Posters 3 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Lost User

    I've read Code Complete by Steve McConnell, essential reading for real world projects. In fact, I give a copy to my intern each year.

    Join the cool kids - Come fold with us[^]

    N Offline
    N Offline
    Not Active
    wrote on last edited by
    #17

    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

    1 Reply Last reply
    0
    • N Not Active

      Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

      N Offline
      N Offline
      Nemanja Trifunovic
      wrote on last edited by
      #18

      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

      1 Reply Last reply
      0
      • N 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

        E Offline
        E Offline
        Ennis Ray Lynch Jr
        wrote on last edited by
        #19

        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

        J 1 Reply Last reply
        0
        • V 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)?

          N Offline
          N Offline
          Not Active
          wrote on last edited by
          #20

          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

          1 Reply Last reply
          0
          • N Not Active

            Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

            R Offline
            R Offline
            Ravi Sant
            wrote on last edited by
            #21

            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.

            1 Reply Last reply
            0
            • N Not Active

              Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

              S Offline
              S Offline
              Simon_Whale
              wrote on last edited by
              #22

              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.

              1 Reply Last reply
              0
              • realJSOPR realJSOP

                Mark Wallace wrote:

                and maybe a bit of judicious Googling

                Googling of *any* kind is only really exercised by people that have the drive and determination to actually find the answer and discover new ideas rather than waiting to be spoon-fed by others who can only make wild-assed guesses due to the low quality and lack of applicable information and/or requirements in the posted question. I'm not bitter. Not me...

                ".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

                D Offline
                D Offline
                Dalek Dave
                wrote on last edited by
                #23

                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[

                realJSOPR 1 Reply Last reply
                0
                • N Not Active

                  Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                  M Offline
                  M Offline
                  Marc Clifton
                  wrote on last edited by
                  #24

                  Mark Nischalke wrote:

                  1. Have you read them?

                  No.

                  Mark Nischalke wrote:

                  1. What level of professional do you consider yourself?

                  Yoda ;) Marc

                  N 1 Reply Last reply
                  0
                  • D 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[

                    realJSOPR Offline
                    realJSOPR Offline
                    realJSOP
                    wrote on last edited by
                    #25

                    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

                    1 Reply Last reply
                    0
                    • M Marc Clifton

                      Mark Nischalke wrote:

                      1. Have you read them?

                      No.

                      Mark Nischalke wrote:

                      1. What level of professional do you consider yourself?

                      Yoda ;) Marc

                      N Offline
                      N Offline
                      Not Active
                      wrote on last edited by
                      #26

                      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

                      1 Reply Last reply
                      0
                      • N Not Active

                        Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                        W Offline
                        W Offline
                        wizardzz
                        wrote on last edited by
                        #27

                        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.

                        1 Reply Last reply
                        0
                        • N Not Active

                          Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                          R Offline
                          R Offline
                          Rama Krishna Vavilala
                          wrote on last edited by
                          #28

                          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.

                          1 Reply Last reply
                          0
                          • N Not Active

                            Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                            I Offline
                            I Offline
                            Ian Shlasko
                            wrote on last edited by
                            #29

                            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)

                            N 1 Reply Last reply
                            0
                            • N Not Active

                              Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                              D Offline
                              D Offline
                              Dan Mos
                              wrote on last edited by
                              #30

                              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

                              1 Reply Last reply
                              0
                              • N Not Active

                                Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                                J Offline
                                J Offline
                                Jun Du
                                wrote on last edited by
                                #31

                                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

                                N 1 Reply Last reply
                                0
                                • J 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

                                  N Offline
                                  N Offline
                                  Not Active
                                  wrote on last edited by
                                  #32

                                  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

                                  1 Reply Last reply
                                  0
                                  • N Not Active

                                    Going back to a discussion with co-workers I was somewhat surprised to learn that senior architects had not heard of these books let alone read them. I view both of these as classics that all developers should read if they want to move beyond just hacking out code all day. The questions are: 1) Have you read them? 2) What level of professional do you consider yourself? (Developer, Team Lead, Architect, etc.) Software Requirements, 2nd Edition[^] by Karl Wiegers Professional Software Development[^] by Steve McConnell There are several thousand books on the subject but which do you recommend as essential guidance for our profession? (Design Patterns (Gof) is a given :) ) Perhaps CP could add a recommended reading list with rankings, sort of a book review forum, to help people in searching a subject matter.


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

                                    M Offline
                                    M Offline
                                    Member 96
                                    wrote on last edited by
                                    #33

                                    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

                                    N J 2 Replies Last reply
                                    0
                                    • M 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

                                      N Offline
                                      N Offline
                                      Not Active
                                      wrote on last edited by
                                      #34

                                      John C wrote:

                                      the school of hard knocks can't be substituted

                                      but it can certainly be augmented with addition learning from other sources and other subjects. IMO that is the mark of a professional, always trying to improve oneself beyond the narrow skills of ones immediate position.


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

                                      M 1 Reply Last reply
                                      0
                                      • I 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)

                                        N Offline
                                        N Offline
                                        Not Active
                                        wrote on last edited by
                                        #35

                                        And what is the difference between the good programmer and the below-average one? How does the below-average become good? Do you discount the message because some misuse it or don't know how to interrupt it correctly?


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

                                        I 1 Reply Last reply
                                        0
                                        • N Not Active

                                          And what is the difference between the good programmer and the below-average one? How does the below-average become good? Do you discount the message because some misuse it or don't know how to interrupt it correctly?


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

                                          I Offline
                                          I Offline
                                          Ian Shlasko
                                          wrote on last edited by
                                          #36

                                          Don't discount the message... Change the message... Instead of "Here's a great new design pattern that will make everything work better!" it should be "Here's another possible way to design your system, and here's when it should be used: ..." Unfortunately, that wouldn't sell as many books, so it'll never happen.

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

                                          N 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups