Reddit mentions: The best api & operating environments books

We found 21 Reddit comments discussing the best api & operating environments books. We ran sentiment analysis on each of these comments to determine how redditors feel about different products. We found 12 products and ranked them based on the amount of positive reactions they received. Here are the top 20.

2. Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming (Unix/C)

    Features:
  • Used Book in Good Condition
Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming (Unix/C)
Specs:
Height9 Inches
Length7.5 Inches
Number of items1
Weight7.936641432 Pounds
Width0.75 Inches
▼ Read Reddit mentions

3. Windows Registry Forensics: Advanced Digital Forensic Analysis of the Windows Registry

    Features:
  • Used Book in Good Condition
Windows Registry Forensics: Advanced Digital Forensic Analysis of the Windows Registry
Specs:
Height9.1 Inches
Length7.4 Inches
Number of items1
Release dateFebruary 2011
Weight1.099996456249 Pounds
Width0.9 Inches
▼ Read Reddit mentions

4. Operating Systems: Internals and Design Principles, Global Edition by Stallings, William (2014) Paperback

Operating Systems: Internals and Design Principles, Global Edition by Stallings, William (2014) Paperback
Specs:
Height9.21258 Inches
Length7.04723 Inches
Weight2.37658318436 Pounds
Width0.94488 Inches
▼ Read Reddit mentions

6. Operating Systems Design and Implementat: Design and Implementation

    Features:
  • Special flatlock construction
  • Tucano Anit-Slip System
  • Rugged 3mm neoprene
Operating Systems Design and Implementat: Design and Implementation
Specs:
Height1.85039 Inches
Length7.99211 Inches
Weight2.7116856455267 Pounds
Width9.99998 Inches
▼ Read Reddit mentions

7. The UNIX Programming Environment

The UNIX Programming Environment
Specs:
Height1.5748 Inches
Length7.874 Inches
Weight1.0141263389775 Pounds
Width5.5118 Inches
▼ Read Reddit mentions

11. System Programming with C and Unix

    Features:
  • Factory sealed DVD
System Programming with C and Unix
Specs:
Height0.9 Inches
Length8.9 Inches
Number of items1
Weight1.01853565044 Pounds
Width2.5 Inches
▼ Read Reddit mentions

🎓 Reddit experts on api & operating environments books

The comments and opinions expressed on this page are written exclusively by redditors. To provide you with the most relevant data, we sourced opinions from the most knowledgeable Reddit users based the total number of upvotes and downvotes received across comments on subreddits where api & operating environments books are discussed. For your reference and for the sake of transparency, here are the specialists whose opinions mattered the most in our ranking.
Total score: 31
Number of comments: 1
Relevant subreddits: 1
Total score: 8
Number of comments: 4
Relevant subreddits: 2
Total score: 4
Number of comments: 1
Relevant subreddits: 1
Total score: 4
Number of comments: 1
Relevant subreddits: 1
Total score: 3
Number of comments: 1
Relevant subreddits: 1
Total score: 2
Number of comments: 1
Relevant subreddits: 1
Total score: 1
Number of comments: 2
Relevant subreddits: 1
Total score: 1
Number of comments: 1
Relevant subreddits: 1
Total score: 1
Number of comments: 1
Relevant subreddits: 1
Total score: 1
Number of comments: 1
Relevant subreddits: 1

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Top Reddit comments about API & Operating Environments:

u/CSMastermind · 4 pointsr/learnprogramming

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
u/LaMaPuppy · 4 pointsr/computerforensics

Aside from SANS FOR508 (the course on which the cert is based) the following helped me:

Windows Registry Forensics

Windows Forensic Analysis Toolkit 2nd ed

Windows Forensic Analysis Toolkit 4th ed

The 2nd edition covers XP, the 4th covers 7/8

Digital Forensics with Open Source Tools

File System Forensic Analysis

This is a new book, but I imagine it'll help as well:

The Art of Memory Forensics

I read many of these in preparation for taking mine, but your best resource are the SANS class/books which is what the cert tests after. Having a good index is key.

There may be other classes out there that might help, but I have no firsthand experience with them, so I can't say what I recommend. All the above books, however, are amazing. Very much worth your time and money.

u/scriptsvcs · 3 pointsr/compsci

> Thanks for your time, my god this was longer than expected.

I suppose in the age of twitter that was a bit of a novel. For us old fogies, that's just a bit more than a post card :)

Introduction to Algorithms is the book for learning everything about algorithms. You'll learn all the standards; how to analyze them (space/time efficiency, Big-O, Big-Theta); and how to prove them; etc.

If you want to learn a great low-level language, the typical things to learn are assembly and C, but I would highly suggest learning Forth. There's tons on the web about it, but the seminal book was Starting Forth. You get all of the low-level detail of assembly, a bit of scaffolding, and you learn to build your higher level language structures as you need them. Great fun, and it's turned out to be very useful through the years, even though I never get to use it in production/release.

u/LiamMayfair · 31 pointsr/C_Programming

In short, the answer is virtual memory and the protected mode flat model that the past generations of CPU architecture and operating systems have been using.

As you may know, programs are never given full, direct access to the RAM banks; the operating system abstracts this layer away from them in the form of virtual memory. Virtual memory is basically a system whereby you can map physical memory addresses to non-physical ones the OS controls and can readily re-arrange. Thanks to virtual memory the OS can trick an application into thinking it has way more RAM than it actually has and this also enables swapping processes out to disk when the system is running out of memory because there are too many processes being run at the same time. As I pointed out before, since virtual memory is fully managed by the kernel, it can move out chunks of a program's address space to disk, a process known as "paging".

Now, back in the DOS era, virtual memory followed the real mode segmented model, which, in very simple terms meant that, even though processes could be shuffled back and forth between RAM and disk, there were no safeguards in place to prevent a process from messing up another process' memory space via a dodgy pointer pointing to a memory address beyond the scope of the faulty process.

One of the major goals of the successor to this virtual memory model, "protected mode flat model" was to allow the kernel to create a completely isolated address space for the processes it spawns and stopping a rogue program from altering other processes like before. Whenever such an attempt is made, a "segmentation fault" (SIGSEV) or "general protection fault" is raised by the kernel, which in the case of Linux, will prompt the kernel to swiftly kill the offending process.

In practical terms, this means your application won't be able to reach beyond the virtual memory address space it has been allocated (unless it's a kernel-space process, like a kernel subsystem or device driver) and can in no way communicate with other processes by reading or writing memory that belongs to them. In order to accomplish that, you'll need to make use of inter-process communication (IPC) techniques like Unix sockets, pipes, RPC, etc.

This is by no means an in-depth or 100% accurate explanation though. If you've got any follow-up questions I'm more than happy to answer them.

As for the literature, pretty much any textbook about operating system architecture will cover virtual memory to a great extent. I can recommend Operating Systems: Internals and Design Principles and Modern Operating Systems.

Here are a few more books that touch upon the topic of virtual memory:

Assembly Language Step-by-Step: Programming with Linux covers the topic of virtual memory and the different models that have evolved over time over its first few chapters.

The Linux Programming Interface: A Linux and UNIX System Programming Handbook covers this subject (and many, many more) from a Linux systems programmer perspective.

What Makes It Page?: The Windows 7 (x64) Virtual Memory Manager, in case you're interested in learning how Windows does it.

EDIT: added IPC info

u/[deleted] · 2 pointsr/askscience

Sure!

The Physics of Solar Cells by Jenny Nelson is a nice book. Very dense, a little mathy, and assumes some prior knowledege.

This book by Martin Green is the gold standard, though it is probably less accessible than Nelson's and harder to find.

It's probably necessary to have a good grasp of freshman physics, and it would certainly be helpful to understand classical electrodynamics and some solid state physics, which itself requires a little bit of quantum mechanics.

Necessary math for all of this is some calculus, some differential equations, and some linear algebra.

There may be a much friendlier resource out there; I understand if this is a formidable stack.

u/MegaMuffindude · 1 pointr/electronics

According to the CP/M wikipedia page, you need the following to run it:

  • A computer terminal using the ASCII character set

  • An Intel 8080 (and later the 8085) or Zilog Z80 microprocessor

  • At least 16 kilobytes of RAM (beginning at address 0)

  • A means to bootstrap the first sector of the diskette

  • At least one floppy disk drive

    So with the parts list above along with the UART should be enough to meet the requirements. You will need to use banked memory or a similar mechanism (since you need the bootstrap code at address 0, but CP/M needs RAM at address 0 as well). Only problem is the floppy drive, which you should be able to overcome with a Compact Flash card, an CF to IDE converter, and a IDE interface. I haven't tried this myself but I think something like this would work.

    If you were interested in writing your own OS, Operating Systems by Woodhull Tanenbaum is a good book on the topic.
u/Jeff-J · 3 pointsr/Gentoo

Books that I find very useful:

Beginning Portable Shell Scripting: From Novice to Professional

From Bash to Z Shell: Conquering the Command Line

Unix Power Tools, Third Edition

The UNIX Programming Environment

Running Linux (mine is old, but still useful)

I have bought lots of other useful books from O'Reilly.

Anything written by Michael W Lucas.

u/fatso784 · 2 pointsr/compsci

Some books on my wishlist (not sure if you're okay with math):

TAOCP

Operating System Principles

Computer and the Brain

Path to the Quantum Computer

u/r_notfound · 1 pointr/C_Programming

Huh. TIL. For the record, I'm older than the average Redditor, and I learned make about 20 years ago, from the 1994 2nd edition of "Mastering Make". Fortunately, SUFFIXES still works for backwards compatibility old farts like me.

Edit: This one.

u/kefeer · 0 pointsr/programming

There is a whole book about how to not screw up in C++ called Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming. And this book does not criticize the language, just tries to be helpful.

Also http://yosefk.com/c++fqa/index.html while may be too snarky too often, has some valid points.

u/entvillager · 1 pointr/Clemson

System Programming Concepts for ECE 222. The book is this.

u/panicClark · 3 pointsr/italy

> pure le istruzioni della carta igienica

Nah, un vero ingegnere 10x al bagno legge questo.

u/FRedington · 1 pointr/programming

Allan Holub, "Enough Rope to Shoot Yourself in the Foot", 1995
http://www.amazon.com/Enough-Rope-Shoot-Yourself-Foot/dp/0070296898

A good thing for removing some "bad behavior" from your coding practice.