(Part 2) Best computers & technology industry books according to redditors

Jump to the top 20

We found 528 Reddit comments discussing the best computers & technology industry books. We ranked the 96 resulting products by number of redditors who mentioned them. Here are the products ranked 21-40. You can also go back to the previous section.

Next page

Top Reddit comments about Computers & Technology Industry:

u/mdaffin · 33 pointsr/devops

First, read The Phenoix Project and The DevOps Handbook as well as the Google SRE book.

After this you should have a good idea of what DevOps is really meant to be about and can start to learn how to implement the details. The key to it is not technology but instead process, don't settle on one particular bit of tech as it may or may not be relevant to any job you get. Instead focus on your problem solving skills and be able to find and pick up new technology to solve problems you encounter.

For this you should focus on the whole process of getting something from development into production. Starting with a simple application written in any language of your choice (learning to program is a key point of being able to apply DevOps principles effectively) and learn how to deploy and run it in production via manual means.

You should get very familiar with version control, especially git which almost all of DevOps revolves around.

From here figure out what are the most painful point of the process then attempt to figure out how to solve them - one by one, increasing the level of automation and tooling you introduce as you go.

Typically you will want to start out with environment automation first - being able to being up a environment with a single command that can be reused for dev, staging and production.

Then look at deployments and getting your code onto each environment. Typically Ansible, SaltStack, Chef or Puppet are used for this.

Next learn about CI and CD and how you can deploy your application from a push or tag to git.

Now that you have a basic pipeline you should add automated testing (unit and integration as well as static analysis such as with linters) to give you better confidence in your deployments.

Once your pipeline is fully automated it is time to look at metrics and logging. Prometheus + Grafana (metrics) and the ELK stack (logging) are good for this.

At the point you should have a good grasp of DevOps processes and can continue to expand from here. Start to look at containerisation including docker then kubernates and how they can solve some of the problems you had above - but also where they are less suitable.

The tech mentioned above is a good starting point, but are far from the only things you should be learning. The exact tech stacks you use are not very important - the important parts are knowing how to apply tech to solve problems. Every company you work for will solve these problems in different ways so to be good at DevOps you need to be flexible with which tech you use.

Note that a lot of roles labelled DevOps are not really DevOps, but more SysAdmin roles or Automation Engineers and while still useful roles can be very misleading, disappointing or not hugely suitable for properly learning DevOps principles.

I also do not fully believe there is a junior DevOps role - DevOps is a combination of both Dev and Ops roles and so tends to require a lot of knowledge of both areas. Typically people get into it from either the Dev or the Ops roles by cross learning to the other side by starting to apply DevOps principles in your day to day work.

Most roles that are labelled as Junior roles are really just junior SysAdmin roles with a heavy slant on automation. Which can be one way to start but keep in mind that you will be learning more of the sysadmin side of things that full DevOps and will need to branch out to the Dev side like with any SysAdmin role.

Even fully fledged DevOps roles can be missleading and can mean anything from Dev who works on deployment pipelines to a SysAdmin that automates infrastructure. There is no good definition of a DevOps roles as it is really a multi-team discipline and about bringing experience of Devs and Ops together rather than one person knowing both sides (though some cross learning is required).

You will find quite a lot of DevOps roles that do not actually follow DevOps principles at all - one key sign of this is the DevOps team being separate from the Dev or Ops team, in fact, if any team is separate you are not fully following DevOps principles.

u/TheBigLewinski · 20 pointsr/webdev

The best single resource, IMO, is The Devops Handbook.

Devops is a spectrum subject, like photography or design. Yes, a professional photographer would commonly use PhotoShop, LightRoom, and a Canon EOS 1D. But you don't become a photographer by using those tools, you become a photographer when the tools are solutions to what you want to accomplish.

Similarly, you don't "do devops" by simply building a Docker enabled CI/CD pipeline. You're doing devops when you create measurable visibility for productivity, when you create organizational memory and learning among teams, when you create autonomy and cohesion among engineers -unobstructed by meaningless process- to build a sustainable, performant and competitive product.

It helps to understand that devops is a largely a product of large corporations facing the challenge of maintaining a complex product which must always be available, secure, bug free (as possible) and performant over the course of years. And they must manage anywhere from a 4 person team to thousands of engineers who are constantly working on the product, and intrinsically challenging every one of the attributes above.

To that end, there are tenants of devops, more than there are hard rules, far too numerous and deep to cover in a reddit comment, but here are some surface level answers to your questions...

Basic workflow starts with TrunkBasedDevelopment. Everyone constantly publishes to master. This is typically achievable by having a set of (integration) tests run on each pull request to ensure the code is deployable. The level of testing done varies considerably for each corporation. Typically, unit testing is a minimum requirement, but there are security, performance, UI, QA and more.

It's important in devops that each developer is provided with immediate and thorough feedback. Tests and failures should happen quickly. If a developer is waiting for two hours each time new code is pushed, it decreases productivity. If messages or failures are unclear, this is also a detriment.

When tests are successful, and the pull request is granted, your code is merged in to master. This is the "delivery" end of continuous delivery.

"Deployment" is sending the code to production so its publicly available. This process varies tremendously by company, and even by project. Common approaches are "blue/green" and "canary" deployments which deliver the new code to a specific percentage of traffic to help find bugs before full deployment, test performance (make sure new queries don't kill the database when thousands of users hit it, for instance), or sometimes conduct marketing tests (A/B testing).

Engineers should also have simple access to perpetual, easy to understand feedback on the quality of their services after deployment, ranging from usage statistics, to performance, to failures. Again, plenty of tools available to help with this, but the end result of helping engineers refine the product is the goal.

Docker: In the theme of understanding devops, it might help to understand the problems being solved by Docker. They're numerous, and this is not exhaustive.

Docker is a "container" technology, but it's not the only one, it's just the most popular. Like what Kleenex is to tissues.

"Containerizing" your code means you deliver everything needed to run your code. This has cascading effects when it comes to operations:

It bundles all the configuration needed with your code. Before Docker, you would install xampp on your local machine in order to run the code base. Then, push it to a server, which had all of the configuration needed for its respective environment (e.g. dev, stage, live).

In this scenario, you're running an approximation of the live environment on your local machine. You have a different OS, maybe a different version of PHP, a different php.ini. Maybe production is running Nginx, and you're running Apache locally.

With Docker, your code is packaged, so your local development gets pushed to production and runs that way, as-is. Your nginx version and configuration, your php version and configuration, etc.

This has cascading benefits:

  • It's far simpler and more robust to setup local development (once your Docker image is setup). New team members can be provided quick, simple to understand instructions, and have the exact environment the rest of the team has, in moments.
  • It abstracts the server configuration away from the code configuration. So, if you want to run a Python 3 app, a PHP 7.1 app and a PHP 7.4 experiment on the same server, you can do so safely and easily.
  • Version updates, security updates and patches to the OS and languages no longer need to be delicately performed on live servers. They can be built and tested locally before deployment (and in the pipeline, if setup correctly).
  • Updates to entire operating systems or language version are often as simple as switching out version numbers in the build process.
  • All of your changes can now be captured in your github repo. Now we can track down the exact date an OS update or language version update was made, and we can easily roll back if it causes issues.
  • It provides deployment flexibility (the aforementioned blue/green and canary deployments), and since most container builds are stored in their own repo, it's simple to redeploy a known working copy in the event of a critical bug deployment.
  • Containers -or properly containerized apps- are easier, more granular and more efficient to scale. When everything is properly containerized, you can simply deploy more containers of the service receiving the most demand, instead of deploying more servers and code, just because of a specific subset of functionality.

    That's all I have energy for. There's a lot, lot more. Hopefully that helps somewhat.

    TL;DR Read The Devops Handbook.
u/SvenViking · 16 pointsr/vive_vr

The book comes out on Tuesday, by the way. Apparently Facebook gave the author a lot of access up until a point when they decided they didn’t like some of the things he was going to say and banned all employees from communicating with him.

> In a nutshell it was basically that for a period of about six months Facebook had been systematically lying to me, particularly with regards to Palmer Luckey and the reason for his exit, and once I began to reveal to them that I actually knew what the truth was they decided it was better not to talk to me and to tell all of their employees not to talk to me.

> And, you know, I guess I kind of envisioned at some point that maybe my access would end with Facebook... because I did come across a lot of pieces of information, not just related to Palmer but just in general that I felt, like, they would not be too psyched about getting out there... but what I found particularly fascinating and unnerving was the extent to which Facebook lied to me.

> And I make that distinction between lying and spin. You know, spin, to me, is embellishment; it’s trying to take real facts and bend them as much as you can to accommodate a more favourable version or a version that you want. And that’s what PR teams and communication teams do, and as much as it is annoying to deal with as a journalist I respect it, that’s their job. But being lied to, to me, is a whole other different thing. To me that’s even way worse than saying “no comment”.

> So that really bothered me, and it bothered me too because, as you are familiar with ... I write in a narrative non-fiction style... so it’s not always a case of attributing quotes directly to a source. ... So I almost felt like they were essentially trying to launder their misinformation through me, and in a way that they didn’t think would come back to them because it wouldn’t be sourced to them. But I ended up making an exception because I felt like it was important it be clear who the information was coming from. And that was the source of... the end of our relationship.

u/Zulban · 15 pointsr/TwoXChromosomes

This wouldn't be the only identifier. Say the video also has a bag of KFC in it, except the bag is unusual and specific to some region of the USA. Even if there's 10,000 KFCs that use that bag, and there are 600 hotels with identical rooms like that, investigators may find that there are only four reasonable matches, where both conditions align.

If this interests you I recommend this book.

u/ivanmarsh · 12 pointsr/funny

It's missing the first panel:

HACKER 1979: Someone who "improves" a system by creatively making it do something it wasn't necessarily designed to do in the first place.

Suggested reading: http://www.amazon.com/Hackers-Computer-Revolution-Steven-Levy/dp/0141000511

u/[deleted] · 11 pointsr/OutOfTheLoop

There is a more rational and alternative explanation to that. Namely that Assange doesn't really get along with Google. They attacked Hillary Clinton because Eric Schmidt supported Hillary and offered her campaign a service of analysing voter opinions via their data-gathering services. WikiLeaks has always spoken against the big power-players in world geopolitics. And what is bigger in the election time than the coalition between heads of Google and Hillary Clinton.

It really is quite clear for somebody who's been following WikiLeaks. They started talking about google before the election. For example here is one of their articles which has both google and Hillary: https://wikileaks.org/google-is-not-what-it-seems/

They even published a book targeted towards google right at the time of elections: https://www.amazon.com/When-Google-WikiLeaks-Julian-Assange/dp/1944869115

And if you look at the DNC leaks that they highlighted - it was, at least in the beginning, all related to google (Specifically E. Schmidt). In particular this email: https://wikileaks.org/podesta-emails/emailid/37262

u/KenshiroTheKid · 8 pointsr/bookclapreviewclap

I made a list based on where you can purchase them if you want to edit it onto your post:

This Month's Book


u/RayCharlizard · 8 pointsr/PS4

The Cell processor is incredibly powerful for certain types of operations, and the type of processing games require is not necesarilly one of them. The PS3 was really not designed for game developers, it was designed so that Sony could say it had the most powerful hardware on the market. DigitalFoundry actually goes over some of this history in their DF Retro on the Sony E3 conference the PS3 was revealed in, but basically there were many engineers at Sony thought fought against the idea of using this Cell processor in favor of something more developer friendly and ultimately failed.

Sony and Microsoft moved to x86 this past generation though because 1) it's way cheaper than paying for R&D on something totally new and different (Sony ate it big time during the PS3-gen for that, there's a couple of really great books about that time) and 2) video games have been designed for x86 processors for the past 2+ decades on PC so there is a wealth of resources available to designers and programmers.

u/wtf1sh · 6 pointsr/bigdata

This books has no math or programming. It concentrates on existing real-word applications of Big Data technologies, and how it is helping to make life better. I recommend it a lot : http://www.amazon.com/Big-Data-Revolution-Transform-Think/dp/0544227751/ref=sr_1_1?ie=UTF8&qid=1422216718&sr=8-1&keywords=big+data

u/noahlt · 4 pointsr/programming

Incidentally, Hackers is no longer out of print, and so you can buy it on amazon!

u/itstimeforanexitplan · 4 pointsr/eebooks

Embedded Systems: Introduction to Arm Cortex-M Microcontrollers , Fifth Edition (Volume 1) https://www.amazon.com/dp/1477508996/ref=cm_sw_r_cp_tai_lEcJBbGEZ1DE5

Digital Design and Computer Architecture: ARM Edition https://www.amazon.com/dp/0128000562/ref=cm_sw_r_cp_tai_aFcJBb49BEQFE

The Art of Electronics https://www.amazon.com/dp/0521809266/ref=cm_sw_r_cp_tai_AFcJBb6P452VQ

https://www.publishing.umich.edu/publications/ee/

Troubleshooting Analog Circuits (EDN Series for Design Engineers) https://www.amazon.com/dp/0750694998/ref=cm_sw_r_cp_tai_MGcJBbHN2BD9G

Should help your for microcontrollers

u/AndrewMcafee · 3 pointsr/IAmA

I am super pessimistic about the ability of bitcoin and other cryptocurrencies to unseat the world's fiat currencies. Cryptocurrencies might well be useful for remittances, ransoms, darknet purchases, gambling, and a few other pretty specific cases, but I think that's it. We talk about this a lot in the chapters 12 and 13 of "Machine | Platform | Crowd"

https://www.amazon.com/dp/B01MAWT25I/ref=dp-kindle-redirect?_encoding=UTF8&btkr=1

u/srm561 · 3 pointsr/AskNetsec

I keep seeing the new book Tribe of Hackers by Marcus Carey and Jen Jin pop up on my twitter feed. Want to read it and let me know if it's worth picking up? :)

u/tfandango · 3 pointsr/thinkpad

There's 8 reviews on Amazon. One is apparently the author but everyone else is probably people from this sub, but anyway, positive reviews there:

https://www.amazon.com/ThinkPad-Different-J-Gerry-Purdy/dp/0672317567/ref=sr_1_2?ie=UTF8&qid=1503524071&sr=8-2&keywords=a+different+shade+of+blue

Thurrott did not like it much apparently, too dry for his tastes

http://windowsitpro.com/windows-server/reviewed-thinkpad-different-shade-blue-building-successful-ibm-brand

u/Glock43 · 3 pointsr/The_Donald

I haven't bought a book in a long time, buy just received this: When Google Met Wikileaks by Julian Assange

u/robber9000 · 3 pointsr/cscareerquestions

I had this book as required reading for my "Software Engineering" course in college:

https://www.amazon.com/Team-Geek-Software-Developers-Working/dp/1449302440

It goes over all the different types of "toxic" behavior and how to treat them. I still have a copy as I find it valuable.

u/grauenwolf · 3 pointsr/business

> Microsoft spent about a decade creating mediocre products and leveraging their OS monopoly to drive competitors out of business.

That's not what happened.

Microsoft made best in class products for a decade during a time period where other operating systems and office productivity companies were actively shooting themselves in the foot. Microsoft won their OS monopoly thru hard work and luck, not by being ruthless or amoral.

ref: http://www.amazon.com/In-Search-Stupidity-Marketing-Disasters/dp/1590597214

But that was the Microsoft of the past. The Microsoft of today is acting just like the companies that they so easily crushed.

u/bedulia · 3 pointsr/nonprofit

I would say the "project" is what you hope the person you are hiring will accomplish. You want to talk about the organization and the people or things you will be helping. What will you be able to do better or more of since you're able to hire this person? In six months, you report on your progress toward that goal.

I'm sure you know this, but it never hurts to have a reminder: just make sure you're connecting this employee/hire to THEIR mission, not just your own.

Best of luck!

ETA: I really like The Only Grant-Writing Book You'll Ever Need though it isn't. But it is a great help.

u/iceman-p · 3 pointsr/slatestarcodex

If this video is what I think it is, the transcript is the book When Google Met Wikileaks (which also has a forward which I don't believe is in the video).

Using that title, I'm sure you can find it on your own, either by paying for it on Amazon or...otherwise.

u/ildiroen · 2 pointsr/devops

The DevOps Handbook, Team Geek and Debugging Teams come to mind.

I don't think there is something specifically for "devops managers" (what is that even?). General leadership books would work for you as a manager I suppose. Just keep the principles of DevOps in mind when you do manage away.

u/Otownkid81 · 2 pointsr/oculus

PSA/LPT/SLPT(?): The book is coming out on Amazon for $14.99 on Kindle or $19.71 on Hardcover

u/tapo · 2 pointsr/programming

It was primarily gaming, with other use cases being an afterthought. Most of the bad decisions came down to Ken Kutaragi.

One of the engineers behind the PPC core used in the Cell and Xenon wrote a book on it (interesting tidbits but meh):

The Race for a New Game Machine: Creating the Chips Inside the XBox 360 and the Playstation 3 https://www.amazon.com/dp/0806531010/ref=cm_sw_r_cp_api_i_IrEYDb75CB92V

u/alreadyheard · 2 pointsr/DataScienceJobs

For books, I recommend Data Science Design Manual, Practical Statistics for Data Scientists and wzchen's list of free books. I recently accepted a job as a Data Scientist and used these books as resources.

u/emcniece · 2 pointsr/devops
u/rsamrat · 2 pointsr/programming

Not included in this bundle, but has anyone read Steven Skiena's new data science book? https://www.amazon.com/Science-Design-Manual-Texts-Computer/dp/3319554433

u/TheSpoom · 2 pointsr/webdev

C For Dummies, Volumes 1 and 2, by Dan Gookin. At almost 1200 pages, it goes through everything a beginner should know in a very readable way, with no preconditions on prior knowledge. These books will take you from a complete novice to the sort of programmer who can pick up another language similar to C (most of them) in a couple of weeks.

Unfortunately it looks like they shrunk these tomes into a single book that doesn't even mention pointers in the most recent version. C All-in-One Desk Reference may be closer.

Peopleware, by Tom DeMarco. If you ever want to manage a software development team, or even really work with a team, you owe it to yourself to read this book. Team Geek is in the same realm.

JavaScript: The Good Parts, by Douglas Crockford is a necessary read if you're doing anything significant in modern web development. JavaScript is a weird little language and if you don't know best practices, it's very, very easy to get lost. This book will tell you where not to look.

How about yourself, OP?

u/caligolae · 2 pointsr/devops

By its very nature, DevOps roles are typically not "junior", and you'll have to have earned your mid-level stripes in systems/operations/cloud engineering to graduate on into DevOps.

Read [0] "The Phoenix Project" and [1] "Leading the Transformation" for an introduction to what DevOps theory/philosophy is all about. It's really worth taking the time to study these books, even if what is in them may not be something you're going to apply at your current job.

Get an [2] AWS certification. As a difficult and rare exam, companies looking view those who hold the DevOps Engineer certification in high esteem.

[0] http://www.amazon.com/Phoenix-Project-DevOps-Helping-Business/dp/0988262592

[1] http://www.amazon.com/Leading-Transformation-Applying-DevOps-Principles/dp/1942788010

[2] https://cloudacademy.com/learning-paths/devops-engineer-professional-certification-AWS-13/

u/canard_glasgow · 2 pointsr/linux4noobs

Browse the link in the side bar

http://www.reddit.com/r/Ubuntu/comments/bbnkp/ive_tinkered_in_ubuntu_before_but_its_the_primary/c0lzpwk

The linux wikibook is okay (bit sparse in bits)

http://en.wikibooks.org/wiki/Linux_Guide

I'd recommend using Ubuntu to start off and reading through some of their excellent documentation. Ubuntu is just one of many Linux distros, but it is good for beginners with a very friendly community.

https://help.ubuntu.com/

Just find something that interests you and play about with it. If you get stuck don't be afraid to ask for help. For some literature on where Linux came from and general history on computing I can recommend:


http://www.amazon.com/Hackers-Computer-Revolution-Steven-Levy/dp/0141000511

http://simson.net/ref/ugh.pdf

http://www.catb.org/jargon/

u/Chris_in_Lijiang · 2 pointsr/selfpublish

I use an designer on fiverr and he always does a great job for a tenner.
Here are a couple of examples.

https://www.amazon.com/dp/B00L7DRU02

https://www.amazon.com/dp/B00B1UKZC6

https://www.amazon.com/dp/B01CI6SZOQ

u/planetjay · 2 pointsr/security

https://www.amazon.com/Tribe-Hackers-Cybersecurity-Advice-World/dp/1793464189 That was quick!

​

Edit: lol already 1 used for sale. (not mine)

u/ferstandic · 2 pointsr/ADHD

I'm a software developer with about 5 years of experience , and I used to have the same sorts of problems where I would over-commit to getting work done and under-deliver. To summarize, I changed to where I only commit to tasks that will take 1-2 days or less at a time, and I make it very very public what I'm working on in order to manage both my and my team's expectations. Here are the gritty details (ymmv of course):


  1. I got my team to start using a ticketing system and explicitly define what we are working on with explicit acceptance criteria for each ticket. That way you know where your finish line is. There other huge benefits to this but its outside of the scope of your personal workflow. This of course takes buy-in from your team, but at the very least start a board on trello with "todo", "in progress", and "done" columns, and try to keep the number of items "in progress" to a minimum, and work on them until their finish. A cardinal sin here is to move something from "in progress" back to "todo". This thing you're setting up is called a kanban board

  2. I break the work I do into 1 or 2 workday 'chunks' on our team board, so I don't lose interest or chase another issue before the work I'm doing gets finished. Keep in mind that some workdays, depending on how heinous your meeting schedule is, a workday may only be 4 (or less :[ ) hours long. An added bonus to this is that its easier to express to your team what you're working on, and after practice chunking up your work, you and they will reasonably be able to expect you to finish 2-3 tasks a week. There are always snags because writing software is hard, but in general smaller tasks will have a smaller amount of variability.

  3. As I'm coding, I practice test-driven development, which has the benefit of chunking up the work into 30 or so minute increments. While I'm making tickets for the work I do, i explicitly define the acceptance criteria on the ticket in the form of tests I'm going to write as I'm coding ( the bdd given-when-then form is useful for this ) , so the flow goes write tests on ticket -> implement (failing) test -> implement code to make test pass -> refactor code (if necessary)

  4. This is a little extreme but I've adopted a practice called 'the pomodoro technique' to keep me focused on performing 30-minute tasks. Basically you set a timer for 30 minutes, work that long, when the time elapses take a 5 minute break. After 5 or so 30-minute intervals, you take a 20-30 minute break. There's more to it, but you can read more here. Again, this is a little extreme and most people don't do things like this. Here is the timer I use at work when its not appropriate to use an actual kitchen timer (the kitchen timer is way more fun though). There's a build for mac and windows, but its open source if you want to build it for something else.


    Side note: in general I limit my work in progress (WIP limit) to one large task and one small task. If there are production issues or something I break my WIP limit by 1 and take on a third task (it has to be an emergency like the site is down and we are losing money), and I make sure that whatever caused the WIP limit to break gets sufficient attention so that it doesn't happen again (usually in the form of a blameless postmortem ) . If someone asks me to work on something that will break the WIP limit by more than one, then I lead them to negotiate with the person who asked me to break it in the first place, because there is not way one person can work on two emergencies at the same time.

    Here's some books I've read that lead me to work like this

u/EricTboneJackson · 1 pointr/OculusQuest

> Palmer is amazingly egotistical

WTF are you talking about? o.O Read History of the Future. You couldn't be further from the truth.

> you can never know if something better will come along

If you believe that, you don't understand what VR is.

VR is the "final platform", because it ends in the Matrix, where you can literally do or be anything. Any other form of entertainment, from sex to playing football to being a fucking whale can be done in VR.

u/ffemino · 1 pointr/nonprofit

I'm a student with no degree or professional experience in the field and I'm a grant writer. It's certainly possible to get into it. Fortunately, I had a lot of opportunities in high school to get solid training in writing (i.e. debate team, student publications, newspaper staff and stuff like that). So talent and solid writing skills are a must. But here's what I did to build up a good skillset in this particular field:

  1. Network - talk to everyone you can in the field, ask questions and show enthusiasm. I worked on political campaigns as a volunteer and ended up making a contact who worked at a nonprofit.
  2. Volunteer - I volunteered at a few nonprofits and got a good sense of how they operate
  3. Intern - The contact I made at the political campaign gave me an email and a good word. I was asked to come in for an interview the next week. Interning was really hard, I spent 500 hours over six months and was so confused and not confident. Once I got the job I have now, I realized that I was actually well prepared. Volunteering at a nonprofit is a good way to get into it.
  4. Buy some books that will teach you - I borrowed this book from the library and it was extremely informative http://www.amazon.com/Only-Grant-Writing-Book-Youll-Ever/dp/0465018696/ref=cm_lmf_tit_6
  5. Pay your dues and bust your a** - I get paid very little, but I'm just looking to build a reputation, samples, accomplishments and a resume. And of course I'm very very passionate about the cause. I've dreamed of running a nonprofit similar to the one I work for one day and that's how I got into it in the first place.
  6. Find events aimed at teaching organizers to build up straight from the ground. My boss sends me to some, she is aware that I have very limited experience and pays for me to train at workshops. I go to workshops every month at a college that runs a nonprofit resource center - you don't need to belong to a nonprofit to go to some of these.
  7. Google - You can learn anything from google if you look in the right places. You'll find templates and guides.
  8. Have writing samples and always get a letter of recommendation from every nonprofit you volunteer at.

    This is a good way to start. I got my job sort of by chance, I just happened to be talking to someone at the right time and had the right connections.

    warning- if you really don't think a nonprofit can make it, don't jump onto a sinking ship. Ultimately, funders don't fund programs because of the programs themselves. I do a lot of brainstorming with our staff and have the ability to speak my peace/give advice and they hear me out because for the most part I know enough to know what works and what doesn't.

    I still have a long way to go for sure, but the above is how I got this far.
u/amazon-converter-bot · 1 pointr/FreeEBOOKS

Here are all the local Amazon links I could find:


amazon.co.uk

amazon.ca

amazon.com.au

amazon.in

amazon.com.mx

amazon.de

amazon.it

amazon.es

amazon.com.br

amazon.nl

Beep bloop. I'm a bot to convert Amazon ebook links to local Amazon sites.
I currently look here: amazon.com, amazon.co.uk, amazon.ca, amazon.com.au, amazon.in, amazon.com.mx, amazon.de, amazon.it, amazon.es, amazon.com.br, amazon.nl, if you would like your local version of Amazon adding please contact my creator.

u/SmileAndDonate · 1 pointr/IAmA


Info | Details
----|-------
Amazon Product | Machine, Platform, Crowd: Harnessing Our Digital Future
>Amazon donates 0.5% of the price of your eligible AmazonSmile purchases to the charitable organization of your choice. By using the link above you get to support a chairty and help keep this bot running through affiliate programs all at zero cost to you.

u/csixty4 · 1 pointr/AskReddit

"After Sams told Gates and Ballmer not to get their hopes up, IBM went silent for a couple of weeks, but that didn't faze Gates and his people at Microsoft."

Big Blues: The Unmaking of IBM

u/dewgazi · 1 pointr/datascience

Big Data: A Revolution that will Transform how We Live, Work, and Think by Mayer-Schonberger and Cukier (https://www.amazon.com/Big-Data-Revolution-Transform-Think/dp/0544227751)

Data Science for Business: What you Need to Know about Data Mining and Data Analytic Thinking by Provost and Fawcett (https://www.amazon.com/Data-Science-Business-Data-Analytic-Thinking/dp/1449361323/ref=pd_bxgy_14_img_3?_encoding=UTF8&psc=1&refRID=XSYTKYEVG8W52XART2BD)

Data and Goliath by Schneier (https://www.amazon.com/Data-Goliath-Battles-Collect-Control/dp/039335217X)

Cathy O'Neill's book is ok. It is worth reading, I thought it could have been better.

Dataclysm is great.

u/pertymoose · 1 pointr/PowerShell

>Read powershell books. Read C# books. Read .NET books. Read C++ books. Read infrastructure books. Read modeling books. Read architecture books. Read everything.

Powershell books

C# books

.NET books (and chromebooks)

Infrastructure book


Data modeling books

Enterprise/application architecture books

If it has a reasonable rating then read it, evaluate it, form your own opinion on it, and learn something.

u/Jallmanua · 1 pointr/Entrepreneur

join us r/msp if you do not know what a MSP is i highly suggest you follow the sub Reddit. I would also read https://www.amazon.co.uk/Managed-Services-Month-Successful-Consulting/dp/1942115474/ref=sr_1_1?keywords=managed+services&qid=1569417482&s=books&sr=1-1 and I have no idea about the LLC compared to the UK . I would say register your llc over sole trader

u/jjmc123a · 1 pointr/technology

Again Actually it was this book I was thinking of.

u/danellender · 1 pointr/Futurology
u/Jolandeer228 · 1 pointr/Futurology

I haven’t read many books solely on AI but mostly learned my knowledge because I study AI at university and the internet. But I would definitely recommend to read this book about future society with advanced AI.

https://www.amazon.com/Life-3-0-Being-Artificial-Intelligence/dp/1101970316/ref=mp_s_a_1_1?ie=UTF8&qid=1543566035&sr=8-1&pi=AC_SX236_SY340_QL65&keywords=Life+3.0%3A+Being+Human+in+the+Age+of+Artificial+Intelligence&dpPl=1&dpID=41mc05UgX8L&ref=plSrch

u/xblackdog · 1 pointr/thinkpad

Amazon is our friendo! $30 isn't bad though for a hardback.

u/Slashff_lifts · 0 pointsr/programming

Heres a book about this topic.

Architecture of a Technodemocracy: How Technology and Democracy Can Revolutionize Governments, Empower the 100%, and End the 1% System https://www.amazon.com/dp/B07CMPKGXD/ref=cm_sw_r_cp_apa_i_MQCnDbXYKMNV7