I've posted this before but I'll repost it here:

Now in terms of the question that you ask in the title - this is what I recommend:

Job Interview Prep

1. Cracking the Coding Interview: 189 Programming Questions and Solutions
   
2. Programming Interviews Exposed: Coding Your Way Through the Interview
   
3. Introduction to Algorithms
   
4. The Algorithm Design Manual
   
5. Effective Java
   
6. Concurrent Programming in Java™: Design Principles and Pattern
   
7. Modern Operating Systems
   
8. Programming Pearls
   
9. Discrete Mathematics for Computer Scientists
   
   

   Junior Software Engineer Reading List
   

   
   

   Read This First
   

   
   

10. Pragmatic Thinking and Learning: Refactor Your Wetware
    
    

    Fundementals
    

    
    

11. Code Complete: A Practical Handbook of Software Construction
    
12. Software Estimation: Demystifying the Black Art
    
13. Software Engineering: A Practitioner's Approach
    
14. Refactoring: Improving the Design of Existing Code
    
15. Coder to Developer: Tools and Strategies for Delivering Your Software
    
16. Perfect Software: And Other Illusions about Testing
    
17. Getting Real: The Smarter, Faster, Easier Way to Build a Successful Web Application
    
    

    Understanding Professional Software Environments
    

    
    

18. Agile Software Development: The Cooperative Game
    
19. Software Project Survival Guide
    
20. The Best Software Writing I: Selected and Introduced by Joel Spolsky
    
21. Debugging the Development Process: Practical Strategies for Staying Focused, Hitting Ship Dates, and Building Solid Teams
    
22. Rapid Development: Taming Wild Software Schedules
    
23. Peopleware: Productive Projects and Teams
    
    

    Mentality
    

    
    

24. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency
    
25. Against Method
    
26. The Passionate Programmer: Creating a Remarkable Career in Software Development
    
    

    History
    

    
    

27. The Mythical Man-Month: Essays on Software Engineering
    
28. Computing Calamities: Lessons Learned from Products, Projects, and Companies That Failed
    
29. The Deadline: A Novel About Project Management
    
    

    Mid Level Software Engineer Reading List
    

    
    

    Read This First
    

    
    

30. Personal Development for Smart People: The Conscious Pursuit of Personal Growth
    
    

    Fundementals
    

    
    

31. The Clean Coder: A Code of Conduct for Professional Programmers
    
32. Clean Code: A Handbook of Agile Software Craftsmanship
    
33. Solid Code
    
34. Code Craft: The Practice of Writing Excellent Code
    
35. Software Craftsmanship: The New Imperative
    
36. Writing Solid Code
    
    

    Software Design
    

    
    

37. Head First Design Patterns: A Brain-Friendly Guide
    
38. Design Patterns: Elements of Reusable Object-Oriented Software
    
39. Domain-Driven Design: Tackling Complexity in the Heart of Software
    
40. Domain-Driven Design Distilled
    
41. Design Patterns Explained: A New Perspective on Object-Oriented Design
    
42. Design Patterns in C# - Even though this is specific to C# the pattern can be used in any OO language.
    
43. Refactoring to Patterns
    
    

    Software Engineering Skill Sets
    

    
    

44. Building Microservices: Designing Fine-Grained Systems
    
45. Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
    
46. NoEstimates: How To Measure Project Progress Without Estimating
    
47. Object-Oriented Software Construction
    
48. The Art of Software Testing
    
49. Release It!: Design and Deploy Production-Ready Software
    
50. Working Effectively with Legacy Code
    
51. Test Driven Development: By Example
    
    

    Databases
    

    
    

52. Database System Concepts
    
53. Database Management Systems
    
54. Foundation for Object / Relational Databases: The Third Manifesto
    
55. Refactoring Databases: Evolutionary Database Design
    
56. Data Access Patterns: Database Interactions in Object-Oriented Applications
    
    

    User Experience
    

    
    

57. Don't Make Me Think: A Common Sense Approach to Web Usability
    
58. The Design of Everyday Things
    
59. Programming Collective Intelligence: Building Smart Web 2.0 Applications
    
60. User Interface Design for Programmers
    
61. GUI Bloopers 2.0: Common User Interface Design Don'ts and Dos
    
    

    Mentality
    

    
    

62. The Productive Programmer
    
63. Extreme Programming Explained: Embrace Change
    
64. Coders at Work: Reflections on the Craft of Programming
    
65. Facts and Fallacies of Software Engineering
    
    

    History
    

    
    

66. Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
    
67. New Turning Omnibus: 66 Excursions in Computer Science
    
68. Hacker's Delight
    
69. The Alchemist
    
70. Masterminds of Programming: Conversations with the Creators of Major Programming Languages
    
71. The Information: A History, A Theory, A Flood
    
    

    Specialist Skills
    

    
    In spite of the fact that many of these won't apply to your specific job I still recommend reading them for the insight, they'll give you into programming language and technology design.
    
    

72. Peter Norton's Assembly Language Book for the IBM PC
    
73. Expert C Programming: Deep C Secrets
    
74. Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming
    
75. The C++ Programming Language
    
76. Effective C++: 55 Specific Ways to Improve Your Programs and Designs
    
77. More Effective C++: 35 New Ways to Improve Your Programs and Designs
    
78. More Effective C#: 50 Specific Ways to Improve Your C#
    
79. CLR via C#
    
80. Mr. Bunny's Big Cup o' Java
    
81. Thinking in Java
    
82. JUnit in Action
    
83. Functional Programming in Scala
    
84. The Art of Prolog: Advanced Programming Techniques
    
85. The Craft of Prolog
    
86. Programming Perl: Unmatched Power for Text Processing and Scripting
    
87. Dive into Python 3
    
88. why's (poignant) guide to Ruby

Sounds like your interests may lie at the intersection of programming languages and computer architecture -- which also happens to be the case for me :-)

Personally, I'm partial to ACM Transactions on Architecture and Code Optimization (TACO) -- and not just because of the awesome acronym: http://taco.acm.org/

Nice advice in general: http://www.bailis.org/blog/you-can-do-research-too/

Papers We Love (mentioned in the above) may be worth attending:
http://paperswelove.org/ & https://github.com/papers-we-love/papers-we-love

The Morning Paper often highlights an interesting paper: https://blog.acolyer.org/

ACM Queue "Research for Practice" series has just recently started, and already looks very promising:
http://queue.acm.org/detail.cfm?id=2949831 / https://queue.acm.org/rfp/vol14iss2.html

In general, if you'd like to stay up to date, conferences are the way to go:
http://www.wikicfp.com/cfp/servlet/event.showtl?lownerid=22347

Conference proceedings aren't available in one, centralized location -- so, the algorithm to follow is to:

• find a conference website of a given year
  
• go to the "program" or "proceedings" section
  
• go through every item/paper/talk, taking note of the ones you find interesting (hint: worth expanding horizons, at least reading the abstract--and even better the introduction--for each)
  
• if a paper is available -- download PDF
  
• otherwise, use a search engine with the title
  
• end up with a fun reading list for the summer :-)
  
  SIGPLAN conferences often have interesting, high-quality submissions: https://en.wikipedia.org/wiki/SIGPLAN
  
  For instance, this year's PLDI has been excellent: http://conf.researchr.org/program/pldi-2016/program-pldi-2016
  
  PLDI 2016 Proceedings are still (limited time) freely available: http://dl.acm.org/citation.cfm?id=2908080 (click "Table of Contents" tab)
  
  Just to give two examples that may particularly match your interests:
  
  
• http://conf.researchr.org/event/pldi-2016/pldi-2016-papers-stratified-synthesis-automatically-learning-the-x86-64-instruction-set
  
• http://conf.researchr.org/event/pldi-2016/pldi-2016-papers-polymorphic-type-inference-for-machine-code
  
  European Conference on Object-Oriented Programming (ECOOP) is also pretty good: http://2016.ecoop.org/program/program-ecoop-2016
  
  Computer Architecture -- and related -- conferences:
  
  

• ASPLOS (International Conference on Architectural Support for Programming Languages and Operating Systems): https://www.ece.cmu.edu/calcm/asplos2016/program.html
  
• ISCA (International Symposium on Computer Architecture): http://isca2016.eecs.umich.edu/index.php/main-program/
  
• MICRO (International Symposium on Microarchitecture): http://www.microarch.org/
  
• HPCA (International Symposium on High-Performance Computer Architecture): http://hpca22.site.ac.upc.edu/index.php/program/conference-program/
  
  More industry-oriented, but often very interesting: http://www.hotchips.org/archives/
  
  More on the intersection of software & hardware:
  
  
• International Symposium on Code Generation and Optimization (CGO): http://cgo.org/cgo2016/
  
• Principles and Practice of Parallel Programming (PPoPP): http://conf.researchr.org/home/PPoPP-2016
  
• International Conference on Parallel Architectures and Compilation Techniques‎ (PACT): https://sites.google.com/a/lbl.gov/pact2015/home/program-draft-1
  
  Last but not least: By no means should you limit yourself to the latest papers. In fact, one can often learn a lot from the classics (which can also serve as good introduction to the ideas, with readable, well-motivated explanations, needed when the concept is still fresh and new--and the audience has to be convinced that it's good): Lots of great ideas come back; take out-of-order (OoO) execution, for example. Even though Tomasulo's algorithm (at the core of OoO) was introduced in the 1960s -- we needed Yale Patt's et al. research (leading to precise exceptions support) in the 1980s for it to become the mainstream.
  
  In computer architecture, many of the great classics are in the "Readings in Computer Architecture": https://smile.amazon.com/Readings-Computer-Architecture-Morgan-Kaufmann/dp/1558605398
  
  Further worth-reading examples include the papers that have received awards like the MICRO Test of Time (ToT) Award or the Influential ISCA Paper award:
  
  

• http://www.microarch.org/Micro-ToT-Award/
  
• https://www.sigarch.org/awards/acm-sigarchieee-cs-tcca-influential-isca-paper-award/
  
  SIGPLAN Awards: http://www.sigplan.org/Awards/
  
  SIGARCH Awards: https://www.sigarch.org/awards/
  

I looked at the FreeCodeCamp curriculum, it looks good for an entry level javascript developer, so since you already started it, you might as well finish it (since, like I said, everybody implicitly expects you to know at least one of python/js/perl as well as HTML+CSS).

2 hours per day is a bit too little IMO - but I understand that it's hard to find time when you have a demanding job and a family that needs time and attention. Just study as much as you can, 2h being the mininum (do keep in mind that CS students, your competition, will be studying at least 8h/day for at least 4 years with tons of homework and more advanced material). So you should probably focus on studying more in the weekends (just typing and thinking about this, I'm actually lucky I started when I was a kid, with all my bills paid for!)

Anyways. You should focus on getting a job first - do keep doing the FreeCodeCamp, as many hours in the day and weekends as you can. Explain to your significant other, if you haven't already done so, your plan - that you're studying hard to upgrade your career, that it might take some time away from them but it will pay off in the long run, etc. Ideally you should be studying at least 4h/day, so try to keep close to that, study more on weekends if necessary. Check this guy for reference on his plan and what he's studying (and note that he's studying full-time - a luxury, I know, but just to put your 2h/day into perspective). This guide is helpful too. Note that you don't need to know all that to get an entry-level development job, but keep that plan in mind for the long run (as you progress your career).

Once you finish the FreeCodeCamp, or even before (I would say, once you finish "Basic Algorithm Scripting"), try doing some local interviews if you can do it without jeopardizing your current job just to get a feel of how interviews work. You won't be trying to get a job (but hey, if you do, awesome), this is just to get your feet wet on interviewing (which is a skill in itself). Since you're not shooting to get a job right now, you won't be as nervous, which is the state of mind you want to be in. If you're relaxed you can talk better, think better, make jokes, be more presentable, which is great - this will put you in the right mood for your future interviews. Try finding people online that can do mock interviews with you in the area you will be focusing on (web/javascript/frontend initially).

Once you're past the basic HTML/CSS part and you start studying JavaScript, I suggest you look into Python as well at the same time. It is a very simple language, quick to learn, and will double your opportunities for employment. As you study both at the same time, you might notice that you like one or the other better - if that happens, focus more on the one you like better, this will accelerate your learning and get you ready for a job faster in your chosen language.

At one point you'll finish HTML/CSS and JavaScript+Python (finish as in be comfortable with them - you'll see that you'll still learn new things as years go by, it will take a few years for you to "master" them). After you're comfortable with JavaScript and Python (and hopefully gainfully employed in development), start studying that book (where you'll learn a GREAT deal about many important things, it will be a dense read, and you will come out of it knowing assembly and C) and then you can focus on algorithms and exercising your thinking with algorithmic puzzles and how computer networks work, operating systems and everything that is generally on this list.

Then after studying all that and with 2-4 years of experience under your belt (and still studying 4h/day), you can start thinking about the next level in your career and preparing for it (larger companies, mid to senior positions, etc) - add a couple more years of experience and you'll be ready to interview for large Valley companies (Google, Apple, FB, etc).

If you plan to self-study all the way through and never join an University, you can look into full-fledged CS courses online and follow that to get a complete theoretical background on CS (that all your colleagues will eventually have and expect of you, at some point in the future).

This probably isn't the most helpful answer, but any resources I might have used to learn the fundamentals myself are probably pretty outdated now. Honestly I'd just try to find highly rated books on Amazon that are reasonably priced. I haven't read this one for psych research methods, but looking through the table of contents, it covers a lot of what I'd expect (ethics, validity and reliability, study design and common methods) and according to the reviews it's clear, concise, and has good stats info in the appendix. I had a similar "handbook" style textbook in undergrad that I liked. For practicing stats, I'm personally more of a learn-by-doing kind of person, and there are some free courses out there like this one from Khan Academy that covers the basics fairly well.

But if you can, take courses in college as electives! Chances are you'll have a few to fill (or maybe audit some if you can't get credit), so go outside of HCDE's offerings to get some complementary skills in research or design. I usually find classrooms to be more engaging than trying to get through a textbook at home on my own, and especially for psych research methods, you'll probably have a project that gives you hands-on experience doing research with human subjects (most likely your peers). There are lots of free online courses out there as well if you aren't able to take them for credit.

You guys are making me miss school.

Getting specifically into UX self-study, in addition to a UX-specific research methods book (this is a newer version of one I read in school) I'd also go through the UX classics like Don Norman's The Design of Everyday Things and Emotional Design, Krug's Don't Make Me Think, and Casey's Set Phasers on Stun (this last one being more of a fun read than a practical one).

Okay so there are a couple of good places to start with malware. The first is Malware Analyst's Cookbook. It is a pretty decent beginner level resource.

From there, Practical Malware Analysis is excellent and goes a lot deeper.

For free resources I've heard good things about Dr. Fu's Malware Analysis Tutorials.

You will need to have a strong understanding of reverse engineering. I like Practical Reverse Engineering or Reverse Engineering for Beginners. The latter is free.

With RE comes assembly. I learned from the free book PC Assembly Language. The RE books should have some info on assembly as well.

You should also know the systems programming API and OS internals for whatever OS you're interested in. This is most likely Windows, so I recommend Windows System Programming and Windows Internals. You can find similar books for Linux and macOS too. Having a good understanding of C and C++ is helpful for this. Also get comfortable using your assembly level debugger on your OS of choice. WinDBG, x64dbg, and OllyDBG are all good on Windows. GDB is pretty much the default on Linux, and LLDB on macOS.

I also highly recommend some scripting language, whether it's Python, Ruby, Powershell or whatever for hacking up your own tools.

Lastly, there is a list on GitHub with a ton of helpful links.

I think that's enough for now.

As far as demand it's hard to say and probably depends a lot on where you're from. It's certainly not like the demand for webdevs but there's also not nearly as many people with the skillset. I'm not a malware analyst myself, I'm more focused on security research and embedded development.

I know those skills are especially high in demand around the Washington, DC area with defense contractors and government agencies. Especially if you can get a security clearance. Most other security firms I know of are always looking for good people with strong reversing and OS internals knowledge.

Let me know if you have any questions and I will try to answer.

I've used both of these books and I've workedat Intel and ARM.

The first one was my professor in UT. He does not get along with Patterson and Hennessey at all. He likes to claim, it's because they're wrong, but probably has more to do with with ego while he was at Berkeley.

Having said that, Hennessey and Patterson, does not go into details. There are mistakes. But therewill be an injection of everyone's favorite religion as absolute truth in any book.

So if you can read papers maybe try: http://www.amazon.com/Readings-Computer-Architecture-Morgan-Kaufmann/dp/1558605398/

To get a job at a chip company, all books are going to be outdated. You won't get to touch architecture anyway. Everyone starts in validation. At most performance monitoring if you have a masters. Patterson and Hennessey will let you know the basics. After that you need to read up on these topics:

• Two-level branch predictor - yes after all the research, branch predictors are effectively still the same as we've had in the Pentium Pro
  
• Trace caches - not really used, but you learn a lot of things about microcode, transactions, and thoughts on faults. Only processor to implement it was Pentium 4, as far as I know.
  
• Virtual Memory - No this down pat. Know how to do it it by hand. ARM one is fairly straightforward. Know each of the permissions settings
  
• Virtualization - This is something newly popular and no one will be teaching it. This blog might be a decent introduction on what is important http://www.futurechips.org/understanding-chips/arm-virtualization-extensions-introduction-part-1.html
  
• Prefetchers - Read up on a few prefetching algorithms.
  
  FYI - noone cares about cache replacement algorithms. LRU works surprisingly well, and most caches are two way set associative anyway - because of diminishing returns but if you really want to read on a new algorrithm try: http://researcher.watson.ibm.com/researcher/files/us-moinqureshi/papers-dip.pdf . But seriously, learning prefetcher strategies is a better use of your time.
  
  
  Edit: Also come to terms with you're not going to know anything about the devil in the details in chip design. That is just black magic, what works, and company culture. And they don't expect you to. Knowing Verilog is a must. Perl (because architects are old school) or Python for scripting. Having worked with a detailed simulator. FOr example adding i-cache prefetching or runahead execution to simplescalar is a useful exercise. Something that messes with fetch is useful because it hasa lot of implications. Also too many core people have no clue of the world outside core and that skill is quickly becoming irrelevant. http://scholar.harvard.edu/files/mickens/files/theslowwinter.pdf - As someone who fell in love with this field and left it running this is a must read for anyone interested in computer architecture. Take OS classes, and distributed systems. Hell learning about distributed systems is a better use of your time for doing computer architecture than learning anything in computer architecture. And bonus, when you get burnt out and pursue another area, you'll have a very strong foundational knowledge that will enable you to do cool things.
  
  Edit2: Two items missing from my checklist: Superscalar and Out-of-order execution.

No, I see the difference, but I attribute it to something else.

Haskell is a simple typed lambda calculus language with very simple, straightforward semantics. In actuality, there isn't really much you can do in Haskell that couldn't be done in Scheme just as easily; the basic constructs are the same.

The difference comes from the fact that Haskell has a powerful type system that ensures correctness, whereas scheme has (almost) no type system. So, doing something complex in Scheme requires you to get it right on your own with no correctness checking, whereas in Haskell, if you don't get it right, it simply won't compile. This attracts developers that want to do some very complex things since because the type system provides such a good safety net, they can actually be done correctly without the programmer having to manually do correctness proofs in their head. This leads of complex monads and arrows and abelian groupoids and all sorts of things that scare even seasoned programmers. This is not IMO a symptom of the complexity of the language, but rather a reflection of the community that the strong type system attracted.

Haskell as a language can be programmed very Scheme like with no knowledge of monads or arrows or any of that stuff... those are constructs tat grow up around the language in the same way that compile time metaprogramming grew up around C++, not because the language demands it, but because the language makes it possible. There is even an introductory text on functional programming using Haskell as a base that never needs to get into such things. I would no more call Haskell complex because of the availability of libraries for doing stacked monads and clifford algebras than I would call C complex because of the availability of BLAS and GMP, even though those are highly complex libraries.

Haskell programmers are not non-mortals :) Anyone who has gone through the above referenced book is a competent Haskell programmer and can do anything they need to do in the language. The language just happens to attract those super-programmers like Oleg K. and Don Stewart who use it to do brain melting tasks. You can program Haskell very effectively without ever even knowing what a monad is the same way that you can program C++ effectively without ever realizing that you can create compile time prime number generators with recursive templates.

At it's core, Haskell is just a normal order lambda calculus evaluator with a system F type system with a syntactic construct to parameterize types. The standard prelude offers pretty much the same functions any Scheme prelude offers and not much else. Anyone with any Lisp or ML under their belt is a competent Haskell programmer in about an hour.

In that case...
You may want to wait for the 5th edition of UNIX and Linux System Administration, as it should release near the end of this year and they don't release new versions that often.

A good way to get started building a college library is to see what the curriculum for the school is and what books are required by professors. Often other colleges will list their book recommendations for the courses online to get an idea of where to start looking. (I know my school has an online bookstore that lists the books for each course and is open to the public)

At least one or two good books in each of those categories, to get a rough idea to start:

• General Programming (A book for each core language, though a lot of information is online as well)
  C, C++, Java, Python and Ruby are popular to start with
  
  
• Web Development (a wide area, but an html/css/javascript text is basic)
  
  
• System Programming (Windows and Linux are wildly different, should probably have both even if not taught - though you already have one linux system programming text recommended, 'the linux programming interface')
  https://www.amazon.com/Advanced-Programming-UNIX-Environment-3rd/dp/0321637739
  https://www.amazon.com/Programming-Paperback-Addison-Wesley-Microsoft-Technology/dp/0134382250
  
  
• Computer Networking
  you already have a couple here
  
  
• Algorithms - the selected book (Introduction to Algorithms) is good, sometimes used for two courses, a complementary text wouldn't hurt too
  
  
• Artificial Intelligence
  https://www.amazon.com/Artificial-Intelligence-Modern-Approach-3rd/dp/0136042597
  
  
• Numerical Methods
  
  
• System Administration (Windows and Linux are different, the recommended text is good for Linux - here's a windows one)
  https://www.amazon.com/Windows-Internals-Part-architecture-management/dp/0735684189 (coming soon)
  
  
• Parallel Computing
  
  
• Distributed Computing
  
  
• Operating Systems - I personally like Stallings' text, though Tanenbaum and Silberschatz is popular too
  
  
• Databases - Nearly all the database books are not that good, in my opinion, but still should have something
  
  
• Cryptography
  
  
• Computer Security
  
  Edit: On second thought, pretty much every college teaches system programming on linux - so perhaps just the linux texts would be adequate for that.

Basically any SRE advice for a normal service but replace/compliment HAproxy / nginx / ingress controller / ELB with the Tor daemon / OnionBalance.

I run Ablative Hosting and we have a few people who value uptime over anonymity etc and so we follow the usual processes for keeping stuff online.

Have multiples of everything (especially stuff that doesn't keep state), ensure you have monitoring of everything from connections, memory pressure, open files, free RAM etc etc.

Just think of the Tor daemon onion service as just a TCP reverse proxy, with load-balancing capability and then follow any other advice when it comes to building reliable infrastructure;

• https://www.amazon.co.uk/Site-Reliability-Engineering-Production-Systems/dp/149192912X/
  
• https://www.amazon.co.uk/Infrastructure-Code-Managing-Servers-Cloud/dp/1491924357/
  
• https://www.amazon.co.uk/Architecting-Scale-Lee-Atchinson/dp/1491943394/
  
• https://www.amazon.co.uk/Building-Microservices-Sam-Newman/dp/1491950358/
  
• https://www.amazon.co.uk/Practical-Monitoring-Mike-Julian/dp/1491957352/
  
• https://www.amazon.co.uk/Cloud-Native-Infrastructure-Justin-Garrison/dp/1491984309/
  
• https://www.amazon.co.uk/Designing-Distributed-Systems-Brendan-Burns/dp/1491983647/
  
• https://www.amazon.co.uk/Databases-at-Scale-Operations-Engineering/dp/1491925949/
  
  
  Once you've got to grips with running a reliable service then you can start layering your Onion reverse proxy / load balancing on top.
  
  
• Isolate your daemons from the clearnet (clearnet example; CloudFlare 'Access' suggests you only allow CloudFlare's IPs through your firewall guaranteeing that only traffic scrubbed by them reaches your servers)
  
• Configure Onionbalance (clearnet example; using keepalive-d / CARP / F5 LTMs to have redundancy for the ingress controller)
  
• Harden your software Unlike the clearnet examples of security you'll want to ensure that your software can't be 'tricked' into making a call to a hostile server (e.g. "Please fetch and attach content at this URL") - you can do this with tricks like Ablative's "QuadHop" setup or simply ensure that your software doesn't have such functionality.
  
  
  All of this aside, check /u/alecmuffett's "Onions that don't suck" repo for examples that are both well setup and stable.
  
  
  TL;DR; Tor is just a TCP reverse proxy with load balancer capabilities go learn some DevOps dodads
  
  Edit: As per Alec's comment - clarify that Tor is technically a reverse proxy with load-balancing capabilities rather than a straight up TCP load balancer.

It's never too early to familiarize yourself with best and current practices within the field.

I'm not sure what your financial situation is as a student, but I would start by locating and getting in contact with the IIBA or PMI local chapter closest to your home or university. It is an invaluable way to build your professional network, discuss the field, and listen to lectures and presentations built on real world experience.

There are also a number of websites which have useful information about the field (white papers, articles, etc.):

• BA Times
  
  
• Modern Analyst
  
  
• Bridging the Gap
  
  
• Mastering Business Analysis - Dave Saboe also hosts a great podcast of the same name
  
  If you are inclined to purchase books, I've found the following very useful in my career:
  
  
• Software Requirements 3rd edition
  
  
• User Stories Applied: For Agile Software Development
  
  
• User Story Mapping
  
  I would say start with the free websites, immerse yourself in the culture/field and take in all you can. Participate in the r/BusinessAnalysis forum. Finally, network your butt off get a job and start your career.
  
  If you have any other questions feel free to ask or PM me.
  

When I was still in school a few years ago, yes there are universities that offer courses specifically on software architecture, usually as a senior-level or graduate-level course. Most require some industry experience as a prerequisite.

• Carnegie Mellon, SEI
  
• Georgia Tech
  
• University of Southern California
  
• Rochester Institute of Technology
  
  There's also apparently a free Udacity course by Georgia Tech.
  
  > I need to understand this fairly well to evaluate companies in the ecosystem.
  
  Much like design, there is no "good" or "bad" architecture; it is only useful in solving certain problems, or it is not useful. Architecture is influenced by the requirements of the product, products, or product lines they are delivering, but also the existing technical environment (I assume that's what you're thinking of evaluating), and the organizational structure of the company. See this excerpt from Software Architecture in Practice.
  
  Without understanding the full context of which the "architecture" was created, it is actually quite difficult to evaluate. Sometimes it is obviously underperforming because the negative effects are extremely visible. But even if it looks ok on the surface, it may be flawed on the premise of satisfying stakeholder requirements, which is even hard for engineers working on the product.
  
  > I imagine that learning it well enough to communicate with developers and understand business use cases and competitive advantages of certain innovations in the space is the end goal.
  
  If this is your goal, then learning more about software requirements sounds like the better approach. This aspect of software engineering directly addresses your business use case concern. Software Requirements by Weigers is pretty good.
  
  > I found a full stack web development specialization at coursera - does that sound like the type of course that might cover all this?
  
  No, that teaches implementation for a specific stack and a architecture - Angular, NodeJS, Ionic, Express, and MongoDB using a Client-server architecture. It doesn't teach you how to critically analyze a system.

Depending on your exposure to exploitation in general, it may be best to briefly introduce yourself to exploitation on Linux first to learn the basics, as there are some additional complexities with Windows exploitation not present in Linux exploitation.

That said, here is a great course that specifically focuses entirely on windows exploit development. Here is an equally amazing series that is probably best used as a supplement during and after that course

If you find that you're struggling with understanding the material (specifically for the OpenSecurityTraining videos), it might be best to follow along the prerequisite knowledge "chain", on the pages for each class (Ex: Confused by exploitation concepts that he doesn't explain in depth in Exploits 2 --> Try out Exploits 1 -- as he probably expects you to know a few things from it already. However, if you find that you may be rusty in assembly --> Sharpen up through their Intro to x86 course, and reviewing/learning C on the side. If you want to understand key differences between Windows and Linux binaries, their Life of Binaries course is pretty good too, but that course itself is not fully necessary for just getting started imo.

If it's a matter of you not being a fan of the teaching style for any reason, an alternative course is Sams Class (which I should let you know ahead of time, covers both linux and windows). Both courses include labs for you to work with as you learn (Sam's class even offering extra mile labs).

As for digging into WinAPI, Windows Internals is probably best used as a reference for when you need it (whether you come across something that specifically requires that information, or reach the point where you need new rabbit holes to dive into). If you can manage to get a course with any of the authors of the book, that may be best for thorough learning of that content. Here is a free alternative, by the co-founder of 'Trail of Bits'.
I personally learned a lot through Windows System Programming and Windows via C-C++, but nothing in this paragraph is necessary to initially jump into windows exploitation. If anything they may be helpful after you start to move beyond the basics.

It depends on how much it interests you.

You can play the whole game without reading any lore if you want.

To get the story of a certain area or zone - read the quests and do your best to do the whole area to competition.

> Also what is a good place to read about wow lore?

I actually don't know. o__o I've been thinking about looking more into myself. They have some books that are good. I enjoyed The Last Guardian. They useally do books before expansions such as War Crimes for WoD and The Shattering for Cata.

There are also a lot of youtubes that talk about it as well though I haven't watched them myself.

The book I learned with
It's old, but still the best C language DSA book.

Here's another by Alfred Aho and co.. It's more of a general programming book, but covers most of the introductory DSA topics, and does it well. Brilliant man and a great teacher.

You were not really clear about what you are hoping to get from it. At the simplest level a computer is little more than a calculator with memeory. If you are wanting to make a simple microcomputer you could base your design off of two of the earlierst ones, the Mark 8 and the Altair 8800. If you follow the external links you will eventually find your way to manuals and schematics. If you want to actually build your own processor you could do somthing like Magic-1 which is a TTL implemented minicomputer. That site is part of a webring of related sites. And finally, if you would like a relatively friendly high level overview of everything from basic circuits to software I would recomend The Black Art of Video Game Console Design. Hope some of this helps, and best of luck with the project!

https://landing.google.com/sre/books/

​

SRE book is free, workbook is not.


https://cloud.google.com/solutions/best-practices-for-operating-containers


https://cloud.google.com/solutions/about-capacity-optimization-with-global-lb


Some of this is google cloud specific but the principles are the same with on-prem or a different provider. "State-of-the-art" deployments are usually learned by using best practices since each distributed app's deployment will vary. These books will help with best practices:



https://www.amazon.com/Microservices-Patterns-examples-Chris-Richardson/dp/1617294543/


https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321/


https://www.amazon.com/Designing-Distributed-Systems-Patterns-Paradigms/dp/1491983647/

Pick up a copy of Mike Cohn's User Stories Applied for a great reference on this topic.

Once you have read that I highly recommend getting a copy of Gojko Adzic's Fifty Quick Ideas to Improve Your Stories (also available on amazon)

You could even roll all of that together and run a story mapping session with your team - this will give them a much broader understanding of what you want the app to do as a whole and you'll get a chance to explain your vision.

EDIT: Hit save early, added story mapping & formatting :)

This book: http://www.amazon.com/Black-Video-Game-Console-Design/dp/0672328208/ref=sr_1_sc_1?ie=UTF8&qid=1394671704&sr=8-1-spell&keywords=blackart+of+video+game+console+design (although a little dated) explains a lot of the basics of EE particularly related to computer design (a video game console is a microcontroller-- more or less-- with capability to read programs from some ROM or the like).

It explains how these things work from both the chemistry and physics view and all the way to digital circuit design. It is quite thorough, though may take some background in at least the relevant math/physics to be useful at the beginning. Other than that, quite easy to follow!

In any event, when it comes to learning computers, persistence is key! Just keep looking at the material and play with the material. Playing is key so you can see how things break and, ultimately, understand why certain things work the way they do. Good luck!

If you want to keep up to speed with the latest development I would recommend blogs like the official Google Analytics blog, Occam's Razor, The Daily Egg, The KiSSmetrics blog etc.

But if you want good tips on how to get started with GA I would recommend Web Analytics - An Hour A Day and Web Analytics 2.0. Both books are by Avinash Kaushik. They are old (for digital marketing litterature) but most of the messages are still very relevant and I found them a great inspiration to get started on structured analytics and how to incorporate analytics in your daily work in a digital marketing organization.

I'm with you, just starting on this. Luckily I have official vCAC training coming up but I've got a start with vCO. These videos are pretty good, although I'm still having some issues getting the examples in the AD Part to work.

 

http://www.cbtnuggets.com/it-training-videos/course/vmwr_vcenter_orchestrator_5_5

 

I also just got this book in the mail yesterday. I haven't read much but it looks promising. Note, after looking at this its for vCO 4.2 but alot of the concepts look like they line up. I'll try to post more about it after reading some.

 

http://www.amazon.com/Automating-vSphere-vCenter-Orchestrator-Technology/dp/0321799917

I think the GA courses put out by Google are pretty good.

https://analyticsacademy.withgoogle.com/

Optimize Smart has a bunch of really good shit as well.
https://www.optimizesmart.com/google-analytics-training-resources-and-tutorials/

I would also suggest reading Avinash's book as well. I know some people find him to be rather verbose. But i'm a big fan.
http://www.amazon.com/Web-Analytics-Hour-Avinash-Kaushik/dp/0470130652

Whenever I get an email about a new programming Humble Bundle, I hop over to Reddit to see if anyone else thinks it's worth buying. In this case, Reddit has failed me, because no one has shared their opinions. All is not lost, however, for I can share mine!

These are probably the most commonly recommended DevOps books:

• The Phoenix Project - written in the form of a novel to teach DevOps principles. (I've read it. It's awesome.)
  
• The DevOps Handbook - a non-fiction book from the authors of The Phoenix Project. (I've started it.)
  
• Site Reliability Engineering - "SRE" is more or less Google's term for DevOps. This book is more or less how Google does DevOps. (I've not read it. It's available online for free.)
  
• Accelerate: The Science of Lean Software and DevOps - Martin Fowler calls this the best programming book of this year. (I've not read it.)
  
• The Site Reliability Workbook - a sequel of sorts to Site Reliability Engineering. Probably less popular than the others I just listed. (I've not read it.)
  
  The Site Reliability Workbook is the only one of these that's included in this bundle. So the first question I ask myself regarding this bundle is, "Do I want to spend the time and money on this bundle's books, or should I spend that on one of the highly recommended books instead?" (Personally, I'm going with the latter.)
  
  Otherwise, most of the books here are technology-specific, so the second question is, "Do I want to learn any of these specific technologies now, and are e-books a good way of doing it?" (Personally, my answer is no.)
  
  Depending on how you answer the first two questions, the last question is, "Are the non-technology-specific books worth getting?" To answer that, here are Amazon links to the non-technology-specific books, for reviews and sales rankings:
  
  
• The Site Reliability Workbook
  
• Designing Distributed Systems
  
• Database Reliability Engineering
  
• Seeking SRE
  
• Cloud Native Infrastructure
  
• Practical Monitoring
  
• Effective DevOps
  

The Shattering. There's a pretty good storyline about both Magni and Anduin as well, and how Moira came to have a seat in Ironforge. It really does fill in a LOT of what happened between wrath and cata. If you care about the storyline of wow, I'd dare say it's essential.

http://www.amazon.com/gp/aw/d/1439172749/ref=mp_s_a_1?qid=1321816538&sr=8-1

edit: it's listed as hardcover, paperback, and ebook format, if anyone is wondering. I was just posting from my phone and grabbed the first link I came across.

I would recommend the Art of Electronics (or the ARRL Handbook) if you are looking for more of a reference style text. Very thorough, but not something you would want to read front to back.

Assuming you have your circuits basics down, a good text to really start learning how to design circuits would be Microelectronic Circuits by Sedra and Smith which is your undergrad text on introductory analog/digital circuits. This one you can definitely read front to back (but it's big). And then if you really want to get into the thick of things, you could read Analysis and Design of Analog Integrated Circuits AKA Grey and Meyer which is your advanced undergrad/graduate text on analog circuits. There are many alternatives to these texts, but these ones are basically bibles.

Ok, so now that I'm not at work and can actually post in detail-

yes. Everything /u/evilresident said is correct. If you take the entire story itself they're all fantastic. However, I think we all have those writers we do and don't like because of their writing styles that take you out of the story.

I am a major fan of Christie Golden's books. Her word choice and close attention to detail (along with Blizzard's obvious help) kinda brings the book to life and you can just FEEL what's going on. I also recommend from her The Shattering: Prelude to Cataclysm. Equally fantastic as Arthas.

The only thing I have about Richard Knaak is that although the books he writes are usually really good, his vocabulary is limited and it kinda shows. I want to say it was Stormrage where he used the word orbs to describe eyes like six times in a single chapter. The book was really good, but it was the lore itself that kept me involved more than the writing.

I'm also tend to nitpick. Either way, no matter which book you read you're in for a good time.

If she's interacting with a lot of users I would suggest reading Practical Empathy. Observing the User Experience is another great resource for learning about user research. User experience is all about people so it's always a good idea to read up on human behavior, psychology, cognition, perception, learning and memory etc. e.g. books like Hooked, Bottlenecks, Design for the mind, Designing with the mind in mind, 100 things every designer needs to know about people, 100 more things every designer needs to know about people, Thinking fast and slow, Predictably Irrational and I would also recommend Articulating design decisions and Friction.

Introduction to Algorithms by CLRS. Used in almost every algorithms class I've heard of, and a great reference book. It's about 1300 pages, so don't try to read straight through it.

C Programming Language by K&R. This is a C programmer's Bible.

Design Patterns by the Gang of Four

This is a little more of a topic book, but The Art of UNIX Programming by Raymond.

These are all either pretty common, or almost essential. You'll probably see these in your curriculum anyway, and you should. These are a good cornerstone.

I would very much recommend http://www.amazon.com/Black-Video-Game-Console-Design/dp/0672328208 ; it goes really far in explaining everything from quantum level up to a working game console. And after that; http://www.amazon.com/Operating-Systems-Design-Implementation-3rd/dp/0131429388/ref=sr_1_1?s=books&ie=UTF8&qid=1405346881&sr=1-1&keywords=minix . Then you'll be set.

Edit; Although the Black art is about game consoles; if you work through it, you can build your own computer in the end, or, what I really like, you can pick up old machines (80s/begin 90s) from Ebay for < $5, open them up , understand them and change them. As they are not 'one chip' with some power supply stuff, but almost everything is held in separate ICs, so you can follow the PCB and see actually what it is doing and how. Great fun. And it scales, as I have no issue making digital things with FGPA's etc because I know it at this level.

>would that mean, technical, that you have multiple Order classes based on context?

Yes. Generally you have a "source" domain where the order originates and the order in other domains generally build their order off of the original order one form the "source" domain.

>If so, do they have their own DAL or do they get mapped differently?

Similar to microservices, its recommended that each domain has it's own persistence mechanism. If you've got really big contexts, especially if they have multiple Order types, then you're probably doing it wrong. The ultimate idea is that an Order in each domain is allowed to evolve independently from any other domain.

>I haven't found a "from 0 to done" example yet

From my experience that's kinda hard, just because there's a lot that exists outside the code with DDD. You need to have the documentation and knowledge from the subject matter expert to really understand why certain things are structured the way they are and why certain terms might be used over others.

As far as resources go, the obvious answer is to go directly to Eric Evan's book, but I also feel that's a lot to chew and digest if you're just getting into the topic. My recommendation is to actually start with Vaughn Vernon's Domain Driven Design Distilled, as it gives a higher level overview and description of the concepts of DDD rather than diving into the deep end like Eric's book. From there, I'd either go to Eric's book or to Vaughn's other book, Implementing DDD. Once you get a lot of the concepts, I've found that Patterns, Principles, and Practices of DDD is a good book to get a handle on the code, architecture, and infrastructure implications of DDD.

There's not a lot out there. A short story on the wow website about Baine Bloodhoof: http://us.battle.net/wow/en/game/lore/leader-story/baine-bloodhoof/1

I'm pretty sure that "The Shattering" book about the Cataclysm also talks about Cairne and Baine: http://www.amazon.com/World-Warcraft-Shattering-Book-Cataclysm/dp/1439172749
Although I have not read that book.

You can also check sites like Wowpedia: http://www.wowpedia.org/Tauren

Jeff Raskin's book The Humane Interface: New Directions for Designing Interactive Systems is a classic source of inspiration. He was the original creator of the Apple Macintosh project, before Steve Jobs took over.

It's dated, but Methodology of Window Management is an interesting read to see how different and diverse user interfaces were before the sudden "standardization" of definitions and expectations that happened when the Mac came onto the scene.

After 1984, everyone tried to imitate the Mac, which itself was an imitation of some of the stuff developed at Xerox PARC. I agree with what Raskin wrote in Wired in 1993: "the first popularization of those ideas [was] on the Apple Macintosh in the 1980s, [and] we have had almost nothing really new in interface design."

Bill Buxton put it well: it is an unworthy design objective to aim for anything less than trying to do to the Macintosh what the Macintosh did to the previous state of the art.

Much of this stuff is learnable outside of work, too, at least at a superficially-passable level. Trust me.

Pick up a few seminal books and read them with vigor. That's all you need to do.

Here are some books I can personally recommend from my library:

Software Design

• A Philosophy of Software Design
  
• Clean Code
  
• Dive Into Design Patterns (Better than the GoF book IMO)
  
• Designing Data Intensive Applications
  
• Microservice Patterns
  
• Test-Driven Development
  
  ​
  
  Software Industry
  
  
• The Software Craftsman
  
• The Clean Coder
  
• Stealing the Corner Office

I found that a lot of the concepts it employs and hooks and the top-down design view only came into focus and understanding for me once I've read the book kubernetes up and running. The documentation is nowhere near the simplistic explanation of this book which made everything painfully clear.

Once I've read that I was able to come up with this post: Deploying clustered applications with Kubernetes where I'm deploying a multifaceted, distributed application with it.

Granted I still found some troubles along the way, but once I did that, everything made sense. :) I also wrote a bunch of beginner explanations which clarifies the main design of it. Hope this helped a little.

You are studying Computer Engineering. Why not study something more applicable to your field? C++, Rust, Golang? Go through Sedgewick and implement some algorithms and data structures in C? Do the cryptopals challenges in C? Try to implement some of the GNU coreutils for fun. Play with an arduino and\or Raspberry Pi and build a cool robot?

Course: UC Berkeley OS & Systems Programming

The Art of Unix Programming

There are many similar resources out there. Extract keywords, web search, repeat. Best of luck!

If you're the "intellectual type", buy a really high quality graduate textbook like (G&M) and read it cover to cover. Work all the problems and save your solutions, to review and update 9 months later. And again 36 months after that.

If you're the "pragmatic type", build things. Lots of different things - don't limit yourself just to guitar amps or radio receivers or test equipment or stereo gear or video studio electronics or alarm systems or automotive electronics or Arduino shields. Do all of them! Work your way through books of schematic diagrams like Horowitz and Hill, Pease, Camanzind and build, build, build.

If you're the "voracious type", do both.

A good place to start might be books like domain driven design distilled. https://www.amazon.com/Domain-Driven-Design-Distilled-Vaughn-Vernon/dp/0134434420

I've also found O Reilly's building microservice to be a decent primer. http://shop.oreilly.com/product/0636920033158.do

For server less, Martin Fowler is always a good place to start: https://www.martinfowler.com/articles/serverless.html

Pretty much did the exact same thing. I'm already planning on how I can make this into a self-service system. That vCO virtual appliance is awesome. Check out this for getting started: http://www.vcoteam.info/learn-vco/pimp-my-vcenter-orchestrator-virtual-appliance.html

Also I just picked up this book: http://www.amazon.com/Automating-vSphere-vCenter-Orchestrator-Technology/dp/0321799917

Start doing regular story time with your PM. Get him in the room with your team and go over each item in the next spring or better yet two sprints in advance. Make sure each story is broken down to minimal possible business value.

Bottom line is when you commit to a sprint you should know exactly what you're doing.

I would recommend this book: https://www.amazon.com/gp/aw/d/0993088104/ref=mp_s_a_1_4?ie=UTF8&qid=1526397738&sr=8-4&pi=AC_SX236_SY340_FMwebp_QL65&keywords=user+stories&dpPl=1&dpID=51aXTnhZj9L&ref=plSrch

Actually, if you want to know an even better one, this series for Data Structures and Algorithms: https://www.amazon.com/gp/aw/d/8192107590/ref=pd_aw_sim_14_of_16?ie=UTF8&psc=1&refRID=C98R4Q72Z8N155CN2C14

The covers are ridiculous, but these are the best.

I've found Haskell: The Craft of Functional Programming to be great. RWH is naturally better for real-world examples though. That would be CoFP's main downfall.

I always recommned two websites and a book. The two best marketing sites IMO are Moz and Econsultancy. Avinash Kaushik's book, Web Analytics An Hour A Day is a great book on the subject of analytics - critical to any marketing process.

You can read a good deal more about the Canon Cat and Jef Raskin's design philosophy generally in Jef's book: The Humane Interface.

I didn't realize it was written in Forth, however. Great link.

I would simply look at getting a book like "Docker up and Running"....if you're going the Docker route I'd also look at something like an orchestration platform (Kubernetes, Mesos, etc). Personally I'd say go with Kubernetes, it's what Google's been using in-house for about a decade or so. Kelsey Hightower just released the "Kubernetes up and Running" book recently. If you don't know Docker at all though, start there first, b/c the foundation for almost all Kubernetes setups is still Docker.

https://www.amazon.com/Docker-Shipping-Reliable-Containers-Production/dp/1491917571/ref=sr_1_1?ie=UTF8&qid=1493307612&sr=8-1&keywords=docker+up+and+running

https://www.amazon.com/Kubernetes-Running-Dive-Future-Infrastructure/dp/1491935677/ref=sr_1_2?ie=UTF8&qid=1493307612&sr=8-2&keywords=docker+up+and+running

Some vids of Kelsey's talks about Kubernetes: https://www.youtube.com/results?search_query=kelsey+hightower

Orchestration is big right now for Dockerized environments and webapp deployment, so getting to the point of being able to design a full CI pipeline around Github/CI (Jenkins, CircleCI, etc)/Kubernetes would give you a huge leg up in a job search right now.

Don't know why this wasn't mentioned yet - but this book is great.

"Algorithms in C"

http://www.amazon.com/Algorithms-Parts-1-4-Fundamentals-Structures/dp/0201314525

UX researcher in the making here. I am currently reading:

https://www.amazon.com/Observing-User-Experience-Practitioners-Research/dp/0123848695

So far, it’s been a great resource in learning the basics :-)

I recommend the Kubernetes: Up and Running book.

The demos are amazing and it explains everything you might need.

This book might interest you, second hand copys are cheap

http://www.amazon.co.uk/Black-Video-Game-Console-Design/dp/0672328208

His website

http://www.xgamestation.com

Or perhaps start with an amiga or older 8 bit emulator and program in that

I highly recommend Kubernetes Up & Running which you can read for free with an individual trial account at https://www.safaribooksonline.com/

Grey and Meyer?


Just curious - what have you got against Razavi, Sedra/Smith, and AoE that can be satisfied by another book? Those three cover quite the spectra of ECE textbook style.

I like this book. it had a section on data structures.
good thing is it comes with C code.

http://www.amazon.com/gp/aw/d/0201756080/ref=mp_s_a_1_5?qid=1452906633&sr=8-5&pi=AC_SX110_SY165_QL70&keywords=data+structures+c&dpPl=1&dpID=51Ea0S0MQwL&ref=plSrch

What's your background? If you've had some experience with the basics, then my recommendation for a good comprehensive overview of analog circuits would be Gray & Meyer:

http://www.amazon.com/Analysis-Design-Analog-Integrated-Circuits/dp/0470245999/ref=sr_1_1?ie=UTF8&qid=1346983358&sr=8-1&keywords=grey+and+meyer

Software Requirements (3rd Edition) (Developer Best Practices) https://www.amazon.com/dp/0735679665/ref=cm_sw_r_cp_apa_i_91JMDbRFCPG5X

https://www.amazon.com/Algorithms-Parts-1-4-Fundamentals-Structures/dp/0201314525

I am not sure if this meets your requirements directly, but it not only discuss the algorithms and the analysis of them, but detailed implementations in C.

There are ones in C++ and Java as well by the same author. Probably worth checking out if you prefer them over C.

The Humane Interface by the late Jef Raskin. It's amazing.

This one.

Amazing book, in my opinion.

Need TEST BANK for the following textbook. PM me ASAP!!!!

​



Software Requirements, Third Edition, Wiegers and Beatty, Microsoft

Press, 2014. ISBN-13: 978-0-7356-7966-5

​

Amazon link: https://www.amazon.com/Software-Requirements-Developer-Best-Practices/dp/0735679665/ref=sr_1_fkmr0_1?ie=UTF8&qid=1539023244&sr=8-1-fkmr0&keywords=Software+Requirements%2C+Third+Edition%2C+Wiegers+and+Beatty%2C+Microsoft+Press%2C+2014.+ISBN-13%3A+978-0-7356-7966-5

​

​

He used the word "bounded context" using its meaning from Domain-Driven Design approach https://martinfowler.com/bliki/BoundedContext.html and that's what triggered Vernon who is the author of 2 books on this topic https://www.amazon.com/Implementing-Domain-Driven-Design-Vaughn-Vernon/dp/0321834577 and https://www.amazon.com/Domain-Driven-Design-Distilled-Vaughn-Vernon/dp/0134434420/ . That's what makes this whole conversation funny.

My favorite book has always been The Humane Interface by Jef Raskin. A lot of the practical stuff he talks about (windows and buttons) was because he wrote this book from like a 1970's perspective, but he is a fucking genius.

Damn right.

The main reason I like my algorithms textbook is because of all the helpful pictures on every page. I forgot most of the stuff the book says, but I learned the algorithms and how to reason intuitively about algorithms by looking at the pictures.

For information architecture, information display books i can recommend:

Information Visualization: Design For Interaction by Robert Spence

The Humane Interface by Jeff Raskin

C Interfaces and Implementations has some decent advice for designing C programs. This is also a skill which you 'll develop with time (e.g. over your entire career) so don't worry too much about figuring it out immediately; it requires experience. As you work on various projects you'll get a sense for what works and what doesn't so that over time you'll have developed strategies for solving particular types of problems.

OOP concepts are still valid even though C may not have ways to necessarily implement them within the language proper. Object-Oriented Software Construction is a fantastic book for learning OOP concepts. As your C experience grows, you'll begin to see ways of implementing some of those design strategies with C, even though it's not an OO language.

Knowing when to use what type of data structure can also aid in simplifying your code base. The standard book for this is CLRS, but for C specific implementations and advice, see Algorithms in C.

This book covers a lot of the material that Beegram2 mentioned. If you want a cheaper version, there's also this. Both contain a number of errors but I think the latter is slightly worse. Still an amazing book, though.

As zabzonk pointed out , C and C++ are two different languages.

Algorithms in C

Algorithms in C++

Many schools are doing a disservice to the students by treating these languages as one.

C is a procedural language.

C++ is a multi-paradigm language.

Part of the design requirements of C++ was to be compatible with C programs. This was achieved for the most part with a few restrictions. So C++ compilers are capable of compiling most C programs. This is the source of the confusion.

No, no, no. The principle is great, but that book is bonkers.

You want the Vaughn books if you're doing DDD:

The bigger book: https://www.amazon.co.uk/dp/0321834577/ref=pd_lpo_sbs_dp_ss_1?pf_rd_p=569136327&pf_rd_s=lpo-top-stripe&pf_rd_t=201&pf_rd_i=0321125215&pf_rd_m=A3P5ROKL5A1OLE&pf_rd_r=83Y7X80HPERQ5AMCEXGG

The shorter book: https://www.amazon.co.uk/Domain-Driven-Design-Distilled-Vaughn-Vernon/dp/0134434420/ref=pd_sim_14_2?_encoding=UTF8&psc=1&refRID=M5QXQ063YDX0E768HE3S

Source: read all of them tried getting traction across multiple teams citing them as sources, and the Evans book is almost intractable to most. Vaughn also at least starts talking about CQRS in a reasonable way, and introduces it using DDD.

You can try this book: https://www.amazon.com/Black-Video-Game-Console-Design/dp/0672328208/ref=olp_product_details?_encoding=UTF8&me=

It covers the topic from first principles.

• Basic atomic physics and semiconductor theory primer.
• Introduction to circuit analysis; current, voltage, and resistance.
• Analog design using discrete components.
• Digital electronics and Boolean algebra.
• Physical hardware construction and prototyping techniques.
• Combinational logic and advanced integrated circuit building blocks.
• Finite state machine design.
• Computer architecture and design.
• Understanding and using microprocessors and microcontrollers.
• Developing software for embedded systems.

https://www.amazon.com/Algorithms-Computer-Science-Robert-Sedgewick/dp/0201514257/ref=sr_1_1?ie=UTF8&qid=1524305825&sr=8-1&keywords=%22Algorithms+in+C%22+by+Sedgewick

or

https://www.amazon.com/Algorithms-Parts-1-5-Bundle-Fundamentals/dp/0201756080/ref=sr_1_2?ie=UTF8&qid=1524305825&sr=8-2&keywords=%22Algorithms+in+C%22+by+Sedgewick

?

Analysis and Design of Analog Integrated Circuits by Paul Gray is considered the bible of analog design. If you are a beginner, I'd look for older editions since they are cheaper and won't make much of a difference.

Analog Circuit Design, 4 volume set D. Feucht

Analysis and Design of Analog Integrated Circuits P. Gray and R. Meyer

Analysis and Design of Digital Integrated Circuis Hodges and Jackson

Audio Power Amplifier Design Handbook D. Self

Optimizing Op Amp Performance J. Graeme

https://www.amazon.com/Designing-Distributed-Systems-Patterns-Paradigms/dp/1491983647

That or DDD Distilled https://www.amazon.com/dp/0134434420/ref=cm_sw_r_cp_apa_DogwzbS6XRA70

There's also a book by Cody Bunch
Automating vSphere with VMware vCenter Orchestrator

http://www.amazon.com/Automating-vSphere-vCenter-Orchestrator-Technology/dp/0321799917

I recently got this one.. Data Structure and Algorithmic Thinking with Python

Software Requirements

Beyond the recommendation for information theory, the application of this mathematics to user interfaces is present in the field. (I'm not particularly familiar with the field, but I remember The Humane Interface discussing this application.)

I think you really need to learn how to program windows in C, not this new .net or sharp stuff.

https://www.amazon.com/Programming-Paperback-Addison-Wesley-Microsoft-Technology/dp/0134382250

https://www.amazon.com/Programming-Windows%C2%AE-Fifth-Developer-Reference/dp/157231995X

edit: oops, you wanted courses, not books.

Take a look at the IIBA (International Institute of Business Analysis) and pick up Wiegers' book on Software Requirements.

Read his father's book.

https://www.amazon.com/exec/obidos/tg/detail/-/0131429019/104-5607387-8275944?v=glance

The Humane Interface: New Directions for Designing Interactive Systems by Jeff Raskin, cognitive psychologist and "Father of the Macintosh". This book fundamentally changed the way I think about designing software.

"The art of Unix Programming" by Eric S. Raymond. Not as intimidating or outdated as you might think - This book goes over the history and philosophical concepts behind not only Unix (and Linux), but also the Open Source initiative behind Linux. ESR's other work is "The Cathedral & the Bazaar" which is also worth a look, but I would argue is dated now, as much of what was suggested in this book has already come to pass with too many real world examples to mention.

Heres a book; but those expansions were bad. Lorewise, I thought still bad but if you like to read.

hummm

tried that buff/dodge/buff , doesn't work for me

plus since I have several buff to activate (4 at the very least, then optional luckbringer, pleiad, etc..) i simply cannot have them all in shortcuts..

pressing second buff on a specific frame is imho incompatible while in a fight which is the whole point of the mystic art. (again imho)

queueing the buffs was an awesome way to get them all applied in an efficient way and this is broken.

broken because you get the sound fx but not the buff, or the shortcuts square icon animates but the buff is not applied , etc etc.

the GUI is inconsistent.

I have to wait, then check if buff is activated. this is just not acceptable .

if i turn the steering wheel to the right, i expect the car to turn right, not to have to maybe turn the wheel some more.. basic interface design..

these devs should read Jef Raskin

I read that this change in the behavior was in response to the fact that you would sometime spend two buff when pressing the button only once. well the quick fix is badly in so many ways...

wrong decision : force a delay

wrong implementation : the gui response and the sound fx response is not dependant on buff activating but on activation button being pressed

how i would have done it:

have an extra settings : allow reapplying of buff: yes no combat / out of combat

yes => you can activate a buff ontop of itself, renewing its timer

no => if a buff is active, you cannot re-apply it.

with condition in combat out of combat.

> PS: jef raskin is the true father of the macintoch

It's long but you could watch this. https://www.youtube.com/watch?v=P0iKFASurHk

Also if you want to read the books, here is the order in which you should.

[World of Warcraft: Dawn of the Aspects] (http://www.amazon.com/World-Warcraft-Richard-A-Knaak/dp/147676137X)

[Warcraft: War of the Ancients #1: The Well of Eternity] (http://www.amazon.com/Warcraft-War-Ancients-Well-Eternity/dp/0743471199)

[Warcraft: War of the Ancients #2: The Demon Soul] (http://www.amazon.com/Warcraft-War-Ancients-Demon-Soul/dp/0743471202)

[Warcraft: War of the Ancients #3: The Sundering] (http://www.amazon.com/Warcraft-War-Ancients-Sundering-Bk/dp/0743471210)

[World of Warcraft: Rise of the Horde] (http://www.amazon.com/World-Warcraft-Rise-Horde-No/dp/0743471385)

[Warcraft: The Last Guardian] (http://www.amazon.com/Last-Guardian-Warcraft-Book-No-3/dp/0671041517)

[World of Warcraft: Tide of Darkness] (http://www.amazon.com/Tide-Darkness-Warcraft-Aaron-Rosenberg/dp/1416539905)

[World of Warcraft: Beyond the Dark Portal] (http://www.amazon.com/Beyond-Dark-Portal-World-Warcraft/dp/1416550860)

[Warcraft: Day of the Dragon: Day of the Dragon] (http://www.amazon.com/Day-Dragon-WarCraft-Book-No-1/dp/0671041525)

[Warcraft: Lord of the Clans] (http://www.amazon.com/Lord-Clans-Warcraft-Book-2/dp/0743426908)

Warcraft: Of Blood and Honor

[World of Warcraft: Arthas: Rise of the Lich King] (http://www.amazon.com/Christie-Golden-World-Warcraft-Arthas/dp/B00320J28G)

[World of Warcraft: Cycle of Hatred: Cycle of Hatred] (http://www.amazon.com/Cycle-Hatred-World-Warcraft-Bk/dp/0743471369/)

[World of Warcraft: Night of the Dragon] (http://www.amazon.com/World-Warcraft-Richard-A-Knaak/dp/0743471377)

[World of Warcraft: Stormrage] (http://www.amazon.com/World-Warcraft-Stormrage-Richard-Knaak/dp/1439189463)

[World of Warcraft: The Shattering: Prelude to Cataclysm] (http://www.amazon.com/World-Warcraft-Shattering-Book-Cataclysm/dp/1439172749)

[World of Warcraft: Wolfheart] (http://www.amazon.com/World-Warcraft-Wolfheart-Richard-Knaak/dp/1451605765)

[World of Warcraft: Thrall: Twilight of the Aspects] (http://www.amazon.com/World-Warcraft-Thrall-Twilight-Aspects/dp/143919663X)

[World of Warcraft: Jaina Proudmoore: Tides of War] (http://www.amazon.com/World-Warcraft-Jaina-Proudmoore-Tides/dp/1451697910)

[World of Warcraft: Vol'jin: Shadows of the Horde] (http://www.amazon.com/World-Warcraft-Voljin-Shadows-Horde/dp/1476702977)

[World of Warcraft: War Crimes] (http://www.amazon.com/World-Warcraft-Crimes-Christie-Golden/dp/1451684487)