Reddit reviews Object-Oriented Analysis and Design with Applications (3rd Edition)
We found 6 Reddit comments about Object-Oriented Analysis and Design with Applications (3rd Edition). Here are the top ones, ranked by their Reddit score.
We found 6 Reddit comments about Object-Oriented Analysis and Design with Applications (3rd Edition). Here are the top ones, ranked by their Reddit score.
There's OO design, and there's particulars as to how to implement things in C++. I'm totally with unapersson as to, that the Os you make are as often conveniences or design helpers as representing real world objects. Ie that it's implementation objects. I don't remember how much OO design advice Effective C++ has, but it's a good book to get someone to intermediate C++ programmer. C++ Coding Standards by Herb Sutter and Andrei Alexandrescu talks at a fast clip about a lot of taste and design issues; I haven't looked at the 3rd edition of Eff. C++ but, from earlier editions, the difference is that Coding Standards is more dense, and sophisticated; Eff. C++ more basic (from what I can see, Coding Standards does cover the same material as Eff C++, but in a very compressed form, only the most minimal discussion; maybe not what you want when you're seeing the material for the first time.
As for pure OO design, I've heard that straight-up Grady Booch is still the best, but I have no experience of it.
I will say, if you want to be good at C++, you'll have to spend money on books (but get your company to buy them perhaps - compared to programmer time, books are free), and time on reading them; there are a lot of best-practices, technicalities and real pitfalls that are not immediately obvious.
edit:
> Also, should I be studying data structures/algorithms in unison with OOP?
Definitely. Have you learned the basics, stack, tree, queue, hash tables (or set, map, vector, unordered_set, unordered_map)? You /must/ know these. (priority_queue and list too, less so maybe.) If you can though I'd read (somehow) about other data structures, spatial ones especially in your case; they can really make your program more efficient and thus able to do more.
edit edit:
I have to say, the above books are for long-lasting code; probably for games your best bet is to look at how other programmers write their games (smaller, simpler, even in other languages - it can be hard to understand large, sophisticated codebases) and, just the necessary experience you gain from writing your own.
Where is this from? It looks like a botched print run or something, since the copies of the book that I can find look fine:
https://www.amazon.ca/Object-Oriented-Analysis-Design-Applications-3rd/dp/020189551X
Senior Level Software Engineer Reading List
Read This First
Fundamentals
Development Theory
Philosophy of Programming
Mentality
Software Engineering Skill Sets
Design
History
Specialist Skills
DevOps Reading List
Object-Oriented Analysis and Design with Applications (3rd Edition) https://www.amazon.com/dp/020189551X/ref=cm_sw_r_cp_apa_i_8YeDCbQEWN9ZY
Grady Booch
http://www.amazon.com/gp/aw/d/020189551X/ref=pd_aw_sbs_14_2?ie=UTF8&dpID=51-uo4HUPCL&dpSrc=sims&preST=_AC_UL100_SR100%2C100_&refRID=110KGH6M22KWAJHKWZ5F
Eric Evans
http://www.amazon.com/Domain-Driven-Design-Tackling--Software/dp/0321125215
Martin Fowler
http://www.amazon.com/Patterns-Enterprise-Application-Architecture-Martin/dp/0321127420
Booch is the classic. https://www.amazon.com/Object-Oriented-Analysis-Design-Applications-3rd/dp/020189551X