Best desktop publishing books according to redditors

We found 168 Reddit comments discussing the best desktop publishing books. We ranked the 59 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top Reddit comments about Desktop Publishing:

u/tb2571989 · 24 pointsr/battlefield_4

It's 9780321480910 which is this book.

u/alanbowman · 22 pointsr/technicalwriting

This is a copy and paste from a few months ago. There isn't really a "bible," so to speak, because the field is so varied. But this list should get you started. There are also some technical writing textbooks on Amazon that might be useful.

  • The Chicago Manual of Style, 17th Edition - the classic reference. This covers pretty much everything you ever wanted to know about grammar and usage, including things you didn't know that you didn't know.

  • The Chicago Guide to Grammar, Usage, and Punctuation - this is an expanded version of chapter 5 of the CMoS mentioned above.

  • The Microsoft Manual of Style, 4th Edition - if you write for Windows-based software, this is the book you need.

    If you're looking for more mechanical things like document structure and organization, I'd recommend the following:

  • Information Development - look for this one used, it's been out of print for awhile. Good information on managing documentation projects. I'm a bit of a broken record on this subject, but a LOT of a technical writer's job is managing projects.

  • Handbook of Technical Writing (this is apparently a textbook now...?) - just what it says on the tin. Good overview of various topics related to tech writing.

  • Developing Quality Technical Information - another overview of various topics related to tech writing. This isn't a "read cover to cover" kind of book, but more of a "open to a random location and just start reading" kind of book.

  • The Non-Designer's Design Book - one thing that tech writers have to think about, or at least should be thinking about, is document design. This is the best book I've found on that subject, bar none. The principles taught in this book guide the layout and design of pretty much every document I've created in the past 9 years.

  • The Insider's Guide to Technical Writing - a good overview of some basic technical writing topics.

  • Every Page is Page One - I've been trying to move more towards the concepts covered in this book as I redo and update the current mess I inherited from the previous tech writer.

u/ilikeUXandicannotlie · 15 pointsr/userexperience

Here are some things I (and I know others) have struggled with. I think the web is exploding with resources and information, so I don’t necessarily think we need to explain what a prototype is. There’s better places elsewhere to learn things about UX, but I think we could provide some good resources for not just people new to UX but everyone else too. I’m coming at this from what I wished I would have access to when I was trying to get into the field. I know that /u/uirockstar has some good walls of text that probably should be included as well. Feel free to suggest any changes to what I have here.




I really want to begin a career in UX/UI. What do I do?


Well, first it’s important to know that UX and UI are not synonymous. While many job postings combine them, UI is a subset of UX, just as research and information architecture are. UI is still important and if you can do both, you do increase your value. While many see UX as a research field at its core, the UX/UI title implies that it’s only about creating pretty things.

The first step is learning more about the field, which brings us to…



What kind of education do I need?


If you are still in school, there are more places recently that are offering courses in human-computer interaction. You can even try to create your own internships. There are very few UX specific schools, though they are starting to pop up, like Center Centre and General Assembly.



Yeah, yeah, that’s great. But I already graduated, so where do I start?


Any focus on people or technology can act as a solid foundation for learning UX. Because there has never been a set entrance path into the field, UX roles are filled with people from many different backgrounds. The most common degrees for those in the field though are design, psychology, communications, English, and computer science. link

There are a number of people in the field who are self-taught. There are tons of books, blogs, and designers (here are some helpful resources) which provide enough UX stuff to keep us all busy. When I first started reading about it, I quickly got overwhelmed because there was so much information available and most of it was intended for those who already had a pretty good grasp on things. The Hipper Element’s crash courses in UX and user psychology are great places to get a fairly quick overview.

There are books like The Design of Everyday Things by Donald Norman, 100 Things Every Designer Needs to Know About People by Susan Weinschenk and Don’t Make Me Think by Steve Krug that make for great first books.

UX Mastery has a great eBook for getting started, appropriately titled Getting Started in UX. Kevin Nichols’ UX for Dummies is both very readable, yet detailed. You can even buy the eBook if you don’t want people on the bus to think you’re a “dummy.”

Lastly, Fred Beecher has a very extensive Amazon list of recommended UX books, depending on what area you are looking to learn more about.



Great. I’ve read a whole bunch of stuff and have a pretty good idea how UX works. Now how do I get someone to hire me so I can gain experience?


Hey, easy there. While, yes, there are lots of UX jobs out there, very few are entry level and not many employers will hire someone who has only read about it and not actually done it. You can’t get a job without experience and you can’t get experience without a job. I know. Frustrating, right?

You have to prove that you can do it. One way to do this is site redesigns.

Go find a website that lacks in it’s user experience and figure out how to fix it. Maybe it’s a small business down the street from you or maybe it’s a feature on eBay you think could be better. Redesigning sites is a good way to practice a process and make mistakes on your own time. If you can involve the owner from that small business down the street, that’s even better because then you can get a sense of the customers (users) that you will be designing for.

Once you have done this, you have (some) experience! Start a portfolio and add to it!



But I have a resume. Why do I need a portfolio?


Resumes are great. But resumes won’t get you a job starting out. It’s a million times more effective to show potential employers what you have done, rather than showing them a resume showcasing that you are a team player and proficient in Microsoft Office. But you should still have a resume that outlines your UX skills.



But I’ve never worked in UX! What should I put on my resume?


You don’t need to put all of your old jobs on your resume if they are unrelated to the field. Most places still want to see some work history so they know you haven’t been living in a cave for the last four years, but they don’t care about how you sold vacuum cleaners or trained circus horses. Maybe you can relate some crossover UX skills to your previous work.

Back to portfolios. They are a lot like elementary math class in that you want to show your work. Potential employers are much more interested in how you made a design decision rather than the final result. If your portfolio just has a bunch of fancy wireframes, that doesn’t tell them how you took specific personas into account and you are simply showing them something that looks pretty. And just because it looks pretty doesn’t always mean it makes sense.



Okay. I have a portfolio with a few unsolicited site redesigns in it.


Congratulations! But I have some bad news. Are you sitting down?

No one wants to hire you yet. You haven’t worked on any “actual” projects that showed how your UX skillz helped a business. I know I suggested you do site redesigns to get practice and you should because that is work you can take to a nonprofit or another small business and say, “here are some trial runs that I’ve done that prove I know what I’m doing and now I can help you for free in exchange for adding it to my portfolio.”

They’ll probably be skeptical and say, “hmmm… I don’t think my website needs this newfangled user experience you speak of and—wait did you say free?”

You both get something out of it and you’re doing it pro bono, which relieves you the pressure of making one tiny mistake. (There is a great site called Catchafire that matches non-profits all over the country with people looking to donate their time and skills.)

Once you have a portfolio displaying your work and some experience, start applying! But there is one more aspect that goes into getting hired and that is the people who will hire you.




Ugh, but isn’t networking just using people for my own professional gain?


I had this same mindset and it probably delayed my entrance into the field. I wanted to rely only on the quality of my work and trusted the rest would follow. I avoided networking and meeting people in the field because I didn’t want it to seem like I was only mooching for a job.

But the fact is people are altruistic in nature and like helping others. Many people also enjoy talking about themselves, and those are the two main principles of an informational interview. You’ll also find that people are excited to help others get started since they remember how difficult it was (see: this blog post).

It wasn’t until I started getting those informational interviews and talking with people at UXPA and MeetUp groups that I learned another side of UX, but also got more familiar with more hiring managers or those that knew them. Whenever possible, people will hire those they know and like. Until you get out and start shaking hands and kissing babies, you will be just another faceless name in a stack of resumes.

Meeting with recruiters/staffing agencies is also a good route as they make money by finding you a job, so they have a vested interest in giving you constructive criticism.




I've heard that you have to live in a big city to get a job in UX.


Move. Just kidding. But while it’s true that larger cities like New York, San Francisco, and Seattle are full of opportunities, there are plenty of other places around the country that have jobs. Here are the top 20. If you live in a tiny city, expect a tougher time finding a position.



Okay, I got an interview. How do I not mess this up?


Some great advice is to go all UX on your preparation and treat the interviewer like a user.

.......to be continued.



Blogs:

u/amrcaspastime24 · 13 pointsr/technicalwriting

Professional writer and hiring manager here. A strong portfolio and a relevant degree like English will help interview at entry level assuming the posting doesn't require strong advanced toolset experience like Framemaker, Robohelp, or DITA. Your folio should have technical communication type stuff like SOPs, policies , and help documentation. Google some templates or use the books I list below. Make them up for existing programs you know if you don't have real world examples. Managers will want to see that you you know the language and will ask for samples at some point during interview if not up front (If they don't ask for samples they probably don't know what they are doing ).

Recommend you at least familiarize yourself with staple toolsets like the Adobe technical communication suite (there may be a free trial or it is like $50 a month or so for subscription) until you are comfortable with it then cancel. Also diagram software like Visio. Screen capture software like Snagit. That will cover the typical core tools in the field. A lot of places will still use MS Word but more advanced places will use technical communication software.

Invest in some theory books to learn and reference. An English degree is great but there are theory and best practices behind technical writing that will help you in the long run and being familiar will help set you apart from all the other English majors that don't know what to do with their degree (it is quite common ).


Get these must have books to read and reference in your career :

(How to write as a tech writer )
https://www.amazon.com/gp/aw/d/0133118975/ref=dp_ob_neva_mobile

(How to design documents)
https://www.amazon.com/White-Space-Your-Enemy-Communicating/dp/1138804649

(Reference document for just about everything )
https://www.amazon.com/Handbook-Technical-Writing-Tenth-Gerald/dp/1250004411

Arguably most popular style manual
https://m.barnesandnoble.com/p/microsoft-manual-of-style-microsoft-corporation/1104743122/2678008132375?st=PLA&sid=BNB_DRS_Core+Catch-All,+Low_00000000&2sid=Google_&sourceId=PLGoP79700&gclid=EAIaIQobChMIycubtNvO1wIVTiOBCh232wKvEAQYASABEgKsUPD_BwE

Look for junior level jobs or contract to hire. A lot of companies will hire temp writers or contract to hire to see If they will work out. Worst case you get title experience on your resume and most recruiters know there is a lot of contract work in the field and it won't look odd.

Try to be open and communicative in your interviews. A lot of the gig is building relationships and getting information out of people you don't know well. Personable people that can communicate quickly, effectively, and confidentlly are desirable.

Good luck !

Edit: Ensure your resume is flawless. It is the first and most important document you will ever make as a technical writer and should be considered the first page of your portfolio.

Look up if there is an active STC chapter in your area. If they have meetings consider going as that is a good place to start networking. I can't recommend joining it if there isn't an active chapter as the ROI is meh ( I may get downvotes for this ).

Get setup with local temp agencies and let them look for jobs for you. Like I said before s lot of companies will go through them to fill temp or contract to hire positions.

Edit edit :

Last thing. It isn't a bad idea to get familiar with some coding languages to strengthen your resume and open doors when applying. W3schools has good , free online lessons to get your feet wet. You can get a certification after a test for $90. It is inexpensive and a good way to prove you are familiar. Html , xml , and css are good starters and you may want to expand from there depending on Your interest and Your local market.

u/sickhippie · 7 pointsr/incremental_games

Okay, I'll give it another shot and try to get at least to the newer botanical and potions stuff you mentioned earlier. I definitely sympathize with revisiting old code, it's always a roller coaster ride.

Also I can suggest a couple good UI/UX books if you want a step up on that front: User Experience of One, 100 Things Every Designer Needs to Know About People, and UI Is Communication. They won't make you the best UI/UX designer in the world, but they might give you a better understand of the goals of UI and how they relate to the people using them. Understanding what people need out of a UI (which is often different than what they say they want out of a UI) goes a very very long way towards longer interaction periods. Good luck!

Edit: also feel free to hit me up if you want to talk more about UI/UX (or any dev-related) stuff. I'd be happy to help out.

u/cecilaz · 7 pointsr/DIY

It has been a long time that I do book binding, so to elaborate on the book corner, here is a visual guide I quickly drew up on illustrator that my instructor taught me. She didn't strictly said it has to be 45 degree but from her experience is somewhere along this line. This is the glue that we use, and you don't need that much glue to get a good adhesive, the key is lightly and evenly spread. I like to dab a little water on the paintbrush to get a smoother spread. There are book fabric that you buy if you don't want to use decorate paper as cover. Book fabric is expensive, but is easier to use than regular fabric if you are still getting hang of the material. This was the book that my instructor recommended, but I am a very hands on and visual learner. so I prefer her demonstration than reading the material. If you are visual learner, I would recommend finding local class that teach book binding to get the basic down. Good luck on your new found hobby!

Edit: forgot to mention there should a piece of paper or any material you like to use on the inside of your book cover. It is more of decoration purposes and to cover the book board, so you don't have to paint the book board. Like this

u/robotjonny · 7 pointsr/macrogrowery

My advice to you is to get yourself a good book, like this one :https://www.amazon.com/Marijuana-Growers-Handbook-Complete-Cultivation/dp/0932551467/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=&sr=

Read it cover to cover - it'll give you a well rounded education if you pay attention. Everything else can be learned on the job

u/EdwardCoffin · 6 pointsr/books

I don't think that just being somewhat old is enough to make the book valuable. For instance, ABE Books lists over 8,000 history books published between 1880 and 1890 that are $20 or less that are located in the U.S.A..

If you want to try restoring it yourself, that could be fun. In that case, I recommend that you get a copy of Aldrin A. Watson's Hand Bookbinding: A Manual of Instruction. It talks about both creating new books from scratch, and how to restore old books, and also talks about how to make the requisite equipment.

u/Godd2 · 6 pointsr/AdviceAnimals

Web development or application programming? If you want to get into web dev, just pick up a book! Just read something like HTML for dummies cover to cover and then CSS and Javascript.

After that, you move onto jQuery, PHP (or Ruby), SQL, etc.

In fact, that's a good list of things to read to get into web dev. HTML, CSS, Javascript, PHP, SQL, jQuery (in kinda sorta that order).

For CSS I recommend CSS: The Definitive Guide. If you read that at least once through, you'll be ahead of the curve in CSS understanding, no joke. Pretty easy read, too, especially if you have the basics of HTML under your belt (hence the HTML for Dummies recommendation).

Javascript and PHP are a bit different. They are full-fledged programming languages. But don't let that intimidate you! They're super easy to learn, and they have a lot in common in the way you write them out.

If you're better at video than books, check out Lynda.com . They have a video tutorial (very comprehensive) for almost every software you can think of (Adobe Suite, HTML, PHP, Ruby, Javascript even videos for LinkedIn).

And, as always, everything I've listed here is equally available on the high seas wink wink.

Good luck! Oh, and if you want to do application programming, pick up a book on C++ or Java.

u/NotRobot_Aero · 5 pointsr/gamedev

If you are going the book route, I have a few suggestions for you!

Not sure if he's a reader? Check out Challenges for Game Designers Basically a collection of game problems to solve, flexing those 'be creative within a bounded scenario' muscles that a lot of big dreamers don't have enough experience with.

Another solid choice is this one,
100 Things Every Designer Needs to Know About People (Voices That Matter). In general it's talking about layouts/formatting, but super solid read for our industry as well.

Both of these are light and fun reads. If you think they might be interested in something heavier, I can post some in that vein as well.

u/thusly · 5 pointsr/books

I do bookbinding as a hobby. Some great introductory books are:

  • Manly Banister - The Craft of Bookbinding
  • A.W. Lewis - Basic Bookbinding
  • Aldren A. Watson - Hand Bookbinding: A Manual of Instruction

    Two good resources to order bookbinding supplies online are:

  • Hollander's
  • Volcano Arts

    If you're having trouble finding Davey board (the most common material used to make the "hard covers") you can also look in craft, art, and hardware stores for millboard/chipboard. It's much better if you can find somewhere local to purchase it -- shipping is a pain, and large sheets are out of the question. Personally, I buy millboard from an art supply store called Opus.

    --

    In terms of tools, you'll want a lying press and plow, and some sort of book press. You'll quickly find that prices for these items from sellers of bookbinding equipment can be exorbitant. Thankfully they're obtainable or reproducible through other methods -- you could sub in a cloth-wrapped board with some weights on it instead of a screw press, for example.

    --

    A sewing frame is definitely something you'll need to look into purchasing or making. If you can't afford either option, here's a great tutorial on turning a chair into one:
    Evilrooster Bookweb: Chair Sewing Frame

    Some slightly more vague instructions on making one out of an encyclopedia:
    papergail: sewing frame and cradle in one

    Further, this seller on eBay has some on the cheap:
    sq12tk | eBay
u/eriknstr · 5 pointsr/Design

The article image reminds me of a book about web design I saw once. I think it was green and it had a pixelated photo of a guy with a hat looking up from either behind the title or from the bottom. Does anyone know which one I'm thinking of?

At first I thought it might have been Eric Meyer on CSS but the cover of that one looks nothing like it. Neither does More Eric Meyer on CSS. I thought it might be about web usability instead but the book I was thinking of then was Designing Web Usability by Jakob Nielsen and that one has no images on the cover at all. I tried to google green book webdesign but none of them look like the one I had in mind :/

---

Edit: Found it!

I searched for web design site:goodreads.com using Google and then I spotted it through http://www.goodreads.com/genres/web-design under "Popular Web Design Books". Designing With Web Standards by Jeffrey Zeldman. No wonder the article image reminded me of the book, it's the same guy!

https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0735712018 - First edition, red

https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0321385551 - Second edition, green

https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0321616952 - Third edition, blue

u/cehak · 5 pointsr/microgrowery

http://www.youtube.com/watch?v=IHJufksP67Y

this is part 1, they're all on youtube.
I highly recommend Ed Rosenthal's Marijuana Grower's Handbook

My personal method is aimed towards hydroponic growing if this is what you're doing, you can shoot me a message. Germinating before soil is explained in the video series.

u/TheStudyOf_Wumbo · 4 pointsr/UofT

Most important thing IMO is /u/MysteryMo 's response cause if you don't like it, then you probably won't finish it.

Projects that got me into what appears to be high places in this field were things that are very painful to do due to the amount of things you need to know. For example, making your own game engine with a renderer is a very obnoxious task and you have to not only be good at linear algebra/math/physics/networks/etc, but your programming skills and debugging strategies cannot suck. Even then when you're passing stuff off to the GPU with OpenGL (or w/e library here), sometimes even then you have no idea why suddenly all your polygons aren't rendering and no output message as to why. There probably are tools to help with this but I could only find one and it was outdated. You will be probably reading a literal fuckton of articles, considering learning assembly to use SSE if you're not using a GPU to do all the good stuff for you, and also dealing with the aspies of the internet when you try to get help on some problem you run into. For example, to get a software renderer running, I had to read tons of textbooks in my free time and spent countless hours absorbing tomes like this just to understand the higher level concepts and play around with optimized implementations.

Maybe a combination of all the above is why some of these projects look really good, since they're generally a pain in the ass to do right even if you know what you're doing.

If the project does something epic like has distributed system components that serves people stuff, this will look a lot better than the next run-of-the-mill-CRUD-app.

I sometimes wonder if maybe taking some cutting edge algorithm and coding it or implementing some advancements with it would be less painful than the journey I took, and also look better.

u/s1e · 4 pointsr/userexperience

Here are a few:

Elements of User Experience, Jesse James Garret: What a typical experience design process is made up of.

Designing Interactions, Bill Moggridge: Seminal thoughts on Interaction Design, holds up to this day

Don't Make Me Think, Steve Krug: One of the first books to gave the issues of IA and UX design a human, customer point of view.

About Face, Alan Cooper: Another take on the whole process, dives a bit deeper into every stage than Garret's book.

Designing For The Digital Age, Kim Goodwin: Human-centered digital products

Sprint, Jake Knapp: A condensed prototyping methodology

100 Things To Know About People, Susan Weinschenk: How people think

There are a few more Product Design related books I recommended in another thread.

IDEO's design thinking methodologies are also a great resource:

Design Kit, A book and toolkit about human centered design

Circular Design, A guide for holistic design, organization friendly.

Cheers

u/mrkite77 · 4 pointsr/programming

It's hit and miss. A lot of it deals with outdated assembly language minutia, to the point where he actually reorders assembly by hand to handle pipeline stalls on the pentium. But there's a lot of good left in it.

Take the chapter on string searching, for example. He'll start out with the simplest string searching, and then introduce concepts like searching for less common characters first, and eventually lands on the boyer-moore algorithm. Even though the book is 90% assembly, he repeatedly makes the point that algorithmic changes gives you 100x speedups, while assembly rewrites only give you modest speedups.

However, if you're into game and graphics programming, I recommend going straight for Abrash's compilation book:

https://www.amazon.com/Michael-Abrashs-Graphics-Programming-Special/dp/1576101746

It contains pretty much everything he's ever written. The entirety of the Zen of Code Optimization, the Zen of Graphics Programming, and a whole bunch of stuff from when Abrash was developing Quake with John Carmack.

u/zonker4965 · 4 pointsr/trees

http://www.youtube.com/watch?v=kO6GhtrgxJ8&feature=c4-overview&playnext=1&list=TLvZ8Qg1uyzSA

Watch all three parts. Also get his book, http://www.amazon.com/Marijuana-Horticulture-Outdoor-Medical-Growers/dp/187882323X/ref=sr_1_1/180-5748622-0703640?s=books&ie=UTF8&qid=1372344635&sr=1-1

I think Jorge is the easiest to learn from. Apparently he isnt a grower but works closely with growers so he has pretty good advice.

If you want to take it up a notch you should also get Ed Rosenthals book http://www.amazon.com/Marijuana-Growers-Handbook-Complete-Cultivation/dp/0932551467/ref=sr_1_1?s=books&ie=UTF8&qid=1372344700&sr=1-1&keywords=ed+rosenthal

With these videos and books you should be able to really get a understanding of the reality of MMJ horticulture.

u/whitesooty · 4 pointsr/italy

Ecco la mia lista/elenco disordinato.

Mi piacerebbe spiegare il perché su ogni libro letto ma sarebbe troppo lungo. Se sei interessato ad un feedback in particolare, fammi sapere in un commento.

In generale: in questo periodo si trova molta letteratura; io consiglio i classici, perché in giro c'è molta bullshit e ho elencato anche tutta una serie di libri per acquisire conoscenza su skills complementari (es. negoziazione, persuasione).

Ho elencato i libri di Codice Edizioni a parte perché uno dei pochi editori che pubblica saggi su argomenti contemporanei come tecnologia e media.

Una parola in più la spendo per i libri di Mari e Munari: sono dei classici che vanno letti. Punto.

LIBRI

UX

u/stoneousmaximus · 4 pointsr/microgrowery

I strongly recommend reading these two books:

u/hamcake · 4 pointsr/web_design

Here's a book I recommend to designers, just so they know a useful amount of HTML, CSS, and graphic formats: Learning Web Design: A Beginner's Guide to (X)HTML, StyleSheets, and Web Graphics

One topic in the book that I'm surprised more designers don't know about is the differences between JPGs, GIFs, and PNGs.

u/igloochan · 3 pointsr/web_design

Not exclusive to web design, but the best design book I ever read was '100 Things Every Designer Needs to Know About People' by Susan Weinshenk.

http://www.amazon.com/Things-Designer-People-Voices-Matter/dp/0321767535/

It deals with a psychological understanding about how people view and interact with works of design, putting it in relevant terms to help make design decisions. Fascinating stuff.

u/gundy8 · 3 pointsr/trees

Ed Rosenthal has a book that would probably answer most of your questions. As for seeds, it's probably your best bet to try and find them through people.

u/ewiethoff · 3 pointsr/learnprogramming

Okay, so run to the book store and get something like HTML, XHTML, and CSS Visual QuickStart. You probably don't need to concern yourself with XHTML. Anyway, pore through that book, and if it turns out you need to learn the latest and greatest HTML5 and CSS3 stuff, you'll have a better idea how to shop for something newer (or how to dig for online tutorials/references) once you get the fundamentals down. Oh, and fill out a company expense sheet for your purchases. :-)

u/Evdawg · 3 pointsr/web_design

The Zen of CSS Design, by Dave Shea. Picks apart the best design's from the CSS Zen Garden. I think a lot of people were disappointing when they found out this book had little code content-- but it sounds like exactly what you're looking for.

u/HammyPBB · 3 pointsr/battlefield_4

This is the ISBN# for The Unicode Standard, Version 5.0

http://www.amazon.ca/The-Unicode-Standard-Version-Edition/dp/0321480910

We should be using Unicode to decipher characters?

u/Boye · 3 pointsr/web_design

somehow I knew that was a link to cssZengarden. I have the book which explains quite a few topics based on some of the designs on cssZenGarden. Great read ;)

u/jspot · 3 pointsr/web_design

I was in a very similar position to yours, albeit with a bit more of a web background but years out of date. I found two books to very useful to get me up to speed, I'm sure there are others but these were the one's I got:

Sams Teach Yourself HTML and CSS in 24 Hours

CSS: The Missing Manual

u/AMSFarmer · 3 pointsr/microgrowery

I started by reading these two books first. It gives you a nice solid foundation and makes reading information on the internet a lot easier.

Ed Rosenthal - Marijuana Grower's Handbook: Your Complete Guide for Medical and Personal Marijuana Cultivation

Jorge Cervantes - Marijuana Horticulture: The Indoor/Outdoor Medical Grower's Bible

u/trucanadian84 · 3 pointsr/microgrowery

Marijuana Grower's Handbook: Your Complete Guide for Medical and Personal Marijuana Cultivation https://www.amazon.ca/dp/0932551467/ref=cm_sw_r_cp_api_i_JN6VCbJJPZHHD


I have this book and it’s full of good info.

u/WhiteCastleHo · 3 pointsr/learnprogramming

No, not really. I learned CSS by finding a bunch of online tutorials, and every few days I would apply what I had learned by doing the CSS Zen Garden thing. I also read Transcending CSS, which is old and was published before CSS3, but it gives some insight into how visual designers approach CSS. At times, it's hilarious, because technical developers hate CSS because it's a shitty language that was designed for visual designers; but visual designers also hated it because it's a shitty language that was designed by technical developers, lol!

But yeah, I'd suggest maybe reading that book and also going through the Net Ninja CSS tutorials and applying what you've learned to CSS Zen Garden. I'm coming at this stuff as a programmer, though. I have no idea how designers approach this stuff, and I feel like this is their domain.

u/GigantorSmash · 3 pointsr/crestron

not tied directly to touch panels, but i found the following books help my touch panels look less like an engineer designed them.

Design of everyday things

100 Things Every Designer Needs to Know About People

this one provided insight sticky design, and what makes some apps stand out, it a world of apps it dose hurt to see what is driving some mobile platform/ product development.

Hooked: How to Build Habit-Forming Products

infocomm published the dashboard for controls, but it is quiet dated, and as pointed out below its counter any kind of modern ui design principal.

u/govision · 3 pointsr/webdev

For really really basic teaching, I loved this one the most because it's like those miscrosoft office books that make you do stuff step by step. As for programming... No books, just use resources.

https://www.amazon.com/Teach-Yourself-VISUALLY-HTML-CSS/dp/0470285885


https://docs.google.com/document/d/1Zb9GCWPKeEJ4Dyn2TkT-O3wJ8AFc-IMxZzTugNCjr-8/edit?usp=drivesdk&ouid=116246055924160986923

u/Riimii · 3 pointsr/cscareerquestions

This book is on my list.

A dot grid notebook would be good. From Behance. From Moleskine.

Portable whiteboard.

Pantone thermo cup.

u/ahydell · 3 pointsr/nfl

I live with my parents and in a really good climate, so I have to grow outdoors. I grow 4 plants per year, I plant in April and harvest in September. Growing is NOT EASY, growing 4 plants is about a $500 investment (seeds, dirt, nutrients, pesticide, all organic) and they're very finicky and you have to be diligent with watering, nutrients, pesticides, etc. But you can get around 8 ounces out of a 5 foot tall plant. I smoke a gram a day so I smoke 12 ounces a year, but my mother also eats a little canna-brownie before bed, so she consumes some of my harvest as well. /r/microgrowery is a great reference, and I can't recommend this book: Ed Rosenthal's Marijuana Growers Handbook enough. It is a labor of love and it took Mom and I 9 days to trim 4 plants. And it's stressful because it's worth so much money to my family. I'm on disability and a fixed income and can't afford to buy it.

u/IanTheRed420 · 3 pointsr/microgrowery

http://www.amazon.com/Marijuana-Growers-Handbook-Complete-Cultivation/dp/0932551467/ref=sr_1_sc_1?s=books&ie=UTF8&qid=1334088516&sr=1-1-spell

Ed Rosenthal is the Eisnstein of Pot. That book will teach you everything about the plant from a cellular level and up.

also the book by SeeMoreBuds is less detailed but full of pictures if you prefer that instead. Still a great buy.

u/CSMastermind · 2 pointsr/AskComputerScience

Senior Level Software Engineer Reading List


Read This First


  1. Mastery: The Keys to Success and Long-Term Fulfillment

    Fundamentals


  2. Patterns of Enterprise Application Architecture
  3. Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
  4. Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML
  5. Systemantics: How Systems Work and Especially How They Fail
  6. Rework
  7. Writing Secure Code
  8. Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries

    Development Theory


  9. Growing Object-Oriented Software, Guided by Tests
  10. Object-Oriented Analysis and Design with Applications
  11. Introduction to Functional Programming
  12. Design Concepts in Programming Languages
  13. Code Reading: The Open Source Perspective
  14. Modern Operating Systems
  15. Extreme Programming Explained: Embrace Change
  16. The Elements of Computing Systems: Building a Modern Computer from First Principles
  17. Code: The Hidden Language of Computer Hardware and Software

    Philosophy of Programming


  18. Making Software: What Really Works, and Why We Believe It
  19. Beautiful Code: Leading Programmers Explain How They Think
  20. The Elements of Programming Style
  21. A Discipline of Programming
  22. The Practice of Programming
  23. Computer Systems: A Programmer's Perspective
  24. Object Thinking
  25. How to Solve It by Computer
  26. 97 Things Every Programmer Should Know: Collective Wisdom from the Experts

    Mentality


  27. Hackers and Painters: Big Ideas from the Computer Age
  28. The Intentional Stance
  29. Things That Make Us Smart: Defending Human Attributes In The Age Of The Machine
  30. The Back of the Napkin: Solving Problems and Selling Ideas with Pictures
  31. The Timeless Way of Building
  32. The Soul Of A New Machine
  33. WIZARDRY COMPILED
  34. YOUTH
  35. Understanding Comics: The Invisible Art

    Software Engineering Skill Sets


  36. Software Tools
  37. UML Distilled: A Brief Guide to the Standard Object Modeling Language
  38. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development
  39. Practical Parallel Programming
  40. Past, Present, Parallel: A Survey of Available Parallel Computer Systems
  41. Mastering Regular Expressions
  42. Compilers: Principles, Techniques, and Tools
  43. Computer Graphics: Principles and Practice in C
  44. Michael Abrash's Graphics Programming Black Book
  45. The Art of Deception: Controlling the Human Element of Security
  46. SOA in Practice: The Art of Distributed System Design
  47. Data Mining: Practical Machine Learning Tools and Techniques
  48. Data Crunching: Solve Everyday Problems Using Java, Python, and more.

    Design


  49. The Psychology Of Everyday Things
  50. About Face 3: The Essentials of Interaction Design
  51. Design for Hackers: Reverse Engineering Beauty
  52. The Non-Designer's Design Book

    History


  53. Micro-ISV: From Vision to Reality
  54. Death March
  55. Showstopper! the Breakneck Race to Create Windows NT and the Next Generation at Microsoft
  56. The PayPal Wars: Battles with eBay, the Media, the Mafia, and the Rest of Planet Earth
  57. The Business of Software: What Every Manager, Programmer, and Entrepreneur Must Know to Thrive and Survive in Good Times and Bad
  58. In the Beginning...was the Command Line

    Specialist Skills


  59. The Art of UNIX Programming
  60. Advanced Programming in the UNIX Environment
  61. Programming Windows
  62. Cocoa Programming for Mac OS X
  63. Starting Forth: An Introduction to the Forth Language and Operating System for Beginners and Professionals
  64. lex & yacc
  65. The TCP/IP Guide: A Comprehensive, Illustrated Internet Protocols Reference
  66. C Programming Language
  67. No Bugs!: Delivering Error Free Code in C and C++
  68. Modern C++ Design: Generic Programming and Design Patterns Applied
  69. Agile Principles, Patterns, and Practices in C#
  70. Pragmatic Unit Testing in C# with NUnit

    DevOps Reading List


  71. Time Management for System Administrators: Stop Working Late and Start Working Smart
  72. The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services
  73. The Practice of System and Network Administration: DevOps and other Best Practices for Enterprise IT
  74. Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale
  75. DevOps: A Software Architect's Perspective
  76. The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations
  77. Site Reliability Engineering: How Google Runs Production Systems
  78. Cloud Native Java: Designing Resilient Systems with Spring Boot, Spring Cloud, and Cloud Foundry
  79. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
  80. Migrating Large-Scale Services to the Cloud
u/_Xantium · 2 pointsr/HTML

Well, this book is a bit outdated (and I don't think it's HTML5), but I learnt the language quickly with HTML, XHTML & CSS Sixth Edition by Elizabeth Castro.

http://www.amazon.com/HTML-XHTML-CSS-Sixth-Edition/dp/0321430840

(Also, I'm not sure if you are starting HTML5 or HTML in general)

u/mysticreddit · 2 pointsr/gamedev

I still have my Black Art of 3D Game Programming around here someplace ...

I always thought he was over rated compared to Michael Abrash's Michael Abrash's Graphics Programming Black Book

u/phishin · 2 pointsr/houstonents

I will try to remember and bring this book: http://www.amazon.com/books/dp/0932551467 if anyone would like to flip through it and learn something. Most everything in this book can be found on the internet but it might ignite some interesting conversation.


Also I was over on /r/seaents and I came across this: http://nwcannabismarket.com/ <---that is a beautiful thing.

u/baby-monkey · 2 pointsr/web_design

I would go to amazon.com and order a bunch of books. Then read them. :)

Design encompasses a lot of things. You need to learn what it aesthetically pleasing. Some people are just bad at it, but you can learn it to some extent. Go to dribbble.com and other design showcases to get a sense of what looks right... and what doesn't. Learn the basics of design so you have some tools to evaluate it with. (If you don't know about kerning, you never notice badly kerned words etc.) So get the knowledge, then practice.

Then you need to have the abilities to create nice things. That involves doing tutorials and learning to use a program like photoshop and illustrator.

Another part of design is more "logical". You need to learn how people think and use websites. So that you can design with purpose (otherwise you are just making pretty pictures). You need to learn conventions of the web and information architecture.

Then you also need to get a feel for... the "feel" of sites. If you can make great looking sites that are easy to use and nicely organizes it is still not enough. If the design does not represent the company and speak to the target audience it is still a more or less useless website. You need to learn the meaning of colors and the styles of different industries. What looks feminine, what looks childish, playful, high-end, corporate... etc.

So...important topics are: information architecture, basics of design, color theory, photoshop books (to learn raw skills), illustrator books, usability books... there are also specific web design books that cover several topics briefly.

This is a great one:
http://www.amazon.com/Things-Designer-People-Voices-Matter/dp/0321767535/ref=sr_1_1?ie=UTF8&qid=1332011684&sr=8-1

Alternatively, read web design blogs. Start with Smashing Magazine.., they have a whole network. Go to "network" and then you can find a lot of other blogs.

u/-t-o-n-y- · 2 pointsr/userexperience

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.

u/MarcelleLeahy · 2 pointsr/bookbinding

Not sure what level bookbinder your partner is, but all bookbinding books by Keith Smith are stellar: Books without Paste or Glue https://www.amazon.com/dp/0963768263/ref=cm_sw_r_cp_api_W2.yzb5HWAXSB :)

u/mstoiber · 2 pointsr/web_design

Sorry, ran out of time. Here's the rest of my answer:

If you are more of an engineer and not that interested in design, but in Front-End Development, start with Bulletproof Web Design, following up with Transcending CSS.

For JavaScript, read You Don't Know JS and Eloquent Javascript. (The second edition of Eloquent is going to be released on 17th of november, if you can't wait until then, there's a first edition aswell)

A very important design book I forgot aswell: The Design of Everyday Things.

Good luck on your way to mastering Web Design!

u/chromarush · 2 pointsr/userexperience

I am self taught and design applications for human and system workflows at a Internet security company. I am biased but I don't think a degree will necessarily give you more hands on skills than just finding projects and building a portfolio to show your skills. There are many many different niche categories, every UX professional I have met have different skill sets. For example I tend in a version of lean UX which includes need finding, requirements validation, user testing, workflow analysis, system design, prototyping, analytics, and accessibility design (not in that order). I am interlocked with the engineering team so my job is FAR different than many UX professionals I know who work with marketing teams. They tend to specialize very deeply in research, prototyping, user testing, and analytics. Some UX types code and some use prototyping tools like Balsamiq, UXpin, Adobe etc. There is heavy debate on which path is more useful/safe/ relevant. Where I work I do not get time to code because my team and I feel I provide the best value to our engineering team and internal/external customers by doing the items listed above. The other UX person I will work with me on similar activities but then may be given projects to look at the best options for reusable components and code them up for testing.

TLDR:

u/interactivejunky · 2 pointsr/webdev

If you want to have a bit more of a broad understanding of design then check out 100 Things Every Designer Needs to Know About People ... it's a nice way of understanding the 'why' of design which will compliment your more practical learning.

u/AndyManCan4 · 2 pointsr/linuxquestions

It's this one I believe:
http://www.amazon.ca/Linux-For-Dummies-6th-Edition/dp/0764579371%3FSubscriptionId%3DAKIAILSHYYTFIVPWUY6Q%26tag%3Dduckduckgo-d-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0764579371
So pretty current, it was a free e-book offer from the Hacker Times, and I always like to read the latest "Linux" Literature, I haven't reviewed this one yet, but I figure it's decent. I have been impressed with "For Dummies" series, they are never the "Best" book for reference, but are always good for beginners.

Let me know what you think about it yourself.

u/shiftyeyeddog1 · 2 pointsr/UXDesign

Is there opportunity at your company to conduct user research? Is there a team devoted to it or do senior designer do research? Have you stumbled across situations where research would help you answer questions about your designs and prototypes?

Having a more advanced degree in some form of research, psychology or advanced UX/HCI would be beneficial if what you really want to do is research. Most of the user researchers I work with have masters in market research or user research and also teach classes to undergrads.

However you do not have to have a degree to learn it. There’s a few books out there that can help, such as Interviewing Users: How to Uncover Compelling Insights or Validating Product Ideas: Through Lean User Research

I also love this book that doesn’t have much to do with research but more about the behavioral science behind user interactions
100 Things Every Designer Needs to Know About People (Voices That Matter) .

u/alaterdaytd · 2 pointsr/sysadmin

http://www.amazon.com/Linux-For-Dummies-6th-Edition/dp/0764579371

The best thing you can do is to setup a VMWare or Hyper-V environment, and just start installing / configuring OS's. The best experience you can get, is real-world experience.

u/its_my_growaway · 2 pointsr/cannabiscultivation

I remembered I have one of the most popular growing books as an eBook. Here is a link to download Ed Rosenthal's Marijuana Grower's Handbook. If you feel conflicted about pirating books you can buy it from Amazon also. The other really popular growing book, Jorge Cervantes Marijuana Horticulture, can be found here.

u/Enkrod · 2 pointsr/webdev

Beeing able to code valid HTML and CSS without any visual help, just by looking at the code-level, should be your first goal. You might be able to learn a lot about it through your Job but I would not depend upon it since it does not seem to go deep enough there.

Right now, disregard Github and all that Jazz, go look for a nice Website with as little JavaScript as possible, make a Screenshot of it and do not look at the code.

Then start building it from scratch. Think about how you would part the sections and place them where they belong, this Book and the website that inspired it helped me a lot with learning good CSS. (Initially, books are your best friends anyway)

The important thing is: Focus on the coding, not the design. Webdesign is a different skillset and can either be avoided or learned seperatly. Do not get hung up on "This just looks bad" before you have the coding down. For now you are only concerned with the coding of HTML and CSS.

When you feel firm (but not perfect) with those you can move on. Now is the Time to decide how you want to apply your new earned skills. If you want to continue developing Wordpress templates I would encourage you to learn the basics of PHP before JS, if you would rather not involve CMS right now you can start by hopping into jQuery. Though there are people who will tell you it's better to learn vanilla JS before you learn jQuery. And I think that's true, but way harder and you won't see as many early, motivating success than starting with the easy-mode that is jQuery.

As soon as you have those 4 down: HTML, CSS, Basic PHP, Basic JS and/or jQuery. You are going to be able to fare way better on the template-front and are more useful to your employer. My guess would be that from then on, as you take on new responsibilities, you will learn more on the Job than you are doing right now.

u/TroubleInMyMind · 2 pointsr/trees

Great book. But a lot of those look like grow books. I see Jorge Cervante's book in that pile, one of my favorites. As well as Ed Rosenthal's growers handbook in the upper right corner

u/kajehart · 2 pointsr/HTML

Years ago, when I first started learning HTML (CSS was a baby), I bought this book and it was the best damn book I ever bought! I wish to Hell they had a series in JS and PHP! http://www.amazon.com/Teach-Yourself-VISUALLY-HTML-Tech/dp/0470285885 After reading that, I found I could really start putting things together!

u/Jimbles · 2 pointsr/bookbinding

Check out Sea Lemon's videos on YouTube. And [this book](hand bookbinding: A Manual of Instruction https://www.amazon.com/dp/048629157X/ref=cm_sw_r_cp_apa_i_vQyWCbR9YZAKD) can be a useful starting reference.

Enjoy the ride down the rabbit hole of bookbinding!

u/FinalRewind · 2 pointsr/css

I actually recommend a book. I got this on one of the Humble Bundle sales for cheap.

​

https://www.amazon.com/CSS-Definitive-Guide-Eric-Meyer/dp/0596527330

u/[deleted] · 2 pointsr/trees

Get rid of the tinfoil - You can use mylar if you want, but a good coat of flat white paint works fine.

With such limited vertical space, work on training your plants - tie them down so they grow sideways as opposed to straight up. Top your plants after the 4th/5th node to help control growth. How long you veg them depends on how much vertical space you have in flowering. Most plants will at least double their size in 12/12, plan accordingly.

What soilless medium are you using? What lighting are you going to use for flowering?

Sites like icmag.com are good resources, but there is a lot of bad information on the internet and sometimes its hard to find a trustworthy source. I suggest you pick up a good book:

http://www.amazon.com/gp/product/0932551467/ref=oss_product

http://www.amazon.com/Marijuana-Horticulture-Outdoor-Medical-Growers/dp/187882323X/ref=sr_1_1?ie=UTF8&s=books&qid=1279560818&sr=1-1-spell

Books are still the best way to learn everything you need to for a successful harvest.

u/ahamilton9 · 2 pointsr/programming

The site I used when I started learning is no longer availible. The closest I've been able to find is this place which looks promising. It's a visual guide so it shows exactly what it's explaining. If he really gets into it, this site is where I learned everything else. It's a bit more advanced, but it's clearly written.

Edit: Also, this book I gave to a relatively computer-illiterate friend who learned quite a bit from it. Another visual guide.

u/cheeseballtaco · 2 pointsr/web_design

I think that there are many ways of learning UX. What I have found that I use most often is googling something like "Modern web design UX" and I try and recreate those myself and so my brain just knows what to do. Here are some cool books I have read that I found very useful.
https://www.amazon.com/Things-Designer-People-Voices-Matter/dp/0321767535/ref=sr_1_1?s=books&ie=UTF8&qid=1509069574&sr=1-1&keywords=100+Things+Every+Designer+Needs+to+Know+About+People%E2%80%8A%E2%80%94%E2%80%8A+Susan+Weinschenk

and

https://www.amazon.com/About-Face-Essentials-Interaction-Design/dp/1118766571/ref=pd_lpo_sbs_14_img_0?_encoding=UTF8&psc=1&refRID=T2H4X09K5XV9Y2HPT56N

good luck friend

u/rugtoad · 2 pointsr/funny

Absolutely.

There are a number of different sites on the web, two of my faves are useit.com and webpagesthatsuck.com

The second one will keep you busy for a bit, and will give you a lot of starting points. They have a few checklists that you can kind of go off of...bearing in mind that there are very few "absolutes" in web design...so if you put together a page that, by a definition on that page, sucks...it may not actually "suck" by all meaningful definitions. In the end, content is what wins over everything. You can have a miserable design, so long as it isn't painful to look at, so long as you have content that is captivating and keeps people coming back.


Anyhow, I'd look through those two and get your research-hat on. From those, you can branch out very quickly across the search engines with all of the lingo and concepts in tow.

Additionally, CSS Zen Garden is a great place to see some of the more "artistic" design concepts in action.

The site itself doesn't necessarily give you a lot of direction, but they have a book that I've found pretty helpful with a lot of those concepts (although it's 6 years old, most of the info is still relevant). Additionally, the zen garden has a few resources linked that can again give you a lot of great places to start.

I always tell people who aren't necessarily able to afford a designer but still need something that a few CMS systems out there can also provide you with the tools you need to get something that looks professional enough and can get you started quickly. Joomla and Wordpress are two that have a bevy of different templates that are free, and readily manipulated to give a custom feel. That's usually the direction most people who have a bit of experience with coding but don't know much about design go.

Hope that helps!

u/crashrider · 2 pointsr/battlefield_4

lol, little late here. Already found it leads to a Unicode 5.0 book.

http://www.amazon.com/gp/offer-listing/0321480910/

u/photoGrant · 2 pointsr/photography

Embedding is useless. Most browsers ignore embedded profiles. Better to send it out untagged.

For more info: http://www.amazon.com/gp/product/0321267222/ref=oh_aui_search_detailpage?ie=UTF8&psc=1

u/irriadin · 1 pointr/infj

Sorry, three weeks later and here I am!

It's hard for me to give advice in a way, because my path into design was quite unorthodox. I started as a computer science major in college, but quickly shifted into a more broad "Information Sciences and Technology" which included human-computer interaction but also things more networking related. It was a great "catch-all" for various technology-related fields. I ended up enjoying the HCI part the most by far.

My first "real" job was working for an agency as one of their developers. I can distinctly remember hearing how the creative director had started as a coder and moved entirely into design and for a while that notion was appealing to me. I taught myself design on the side, devouring many books and carefully examining the site designs created by our designers.

A few years later, I was working for a college as their web manager and saw a window of opportunity; they were beginning the process for a website redesign. Almost as a lark, I pushed out what I thought the new website should look like and presented it to the other members of the web committee. They all liked my design and decided to work in-house with me as the designer and principle developer.

So my advice for you is perhaps a little generic, but I think still helpful: never stop learning. Keep reading all you can about UX, UI design, HCI, and the industries that interest you for product design. If you see an opportunity to grow professionally, whether that is a promising job offer or some project that has just coalesced, be bold and try your hand at it. Don't talk yourself out of a chance to grow before even trying; it's an easy pitfall.

For breaking in: read all that you can, for example this book is an excellent resource and quick read. Have an opinion on everything; for the things that you don't know, be curious and thoughtful. Recognize what makes for a bad user experience and what makes for a good one. Be empathetic.

Hope that helps. Good luck to you!

u/StitchedCloth · 1 pointr/FanFiction

Character Sympathy by Jordan McCollum


The Busy Writer's Tips on Writing Romance by Marg McAlister

5 Tips for Getting Unstuck in Our Story by Jami Gold

This isn't a book but this article has helped me to overcome writer's block in the past

u/curiosity36 · 1 pointr/microgrowery

Go with the classic. Ed Rosenthal's Marijuana Grower's Handbook. It'll set you up right with all the knowledge, solid foundations, and the right attitude.

http://www.amazon.com/Marijuana-Growers-Handbook-Complete-Cultivation/dp/0932551467

u/theunfilteredtruth · 1 pointr/truegaming

You are correct that it isn't really 3d, it is lots of 2d shapes rendered to look like 3d.

The DOOM Engine did something unique though which made it so much faster than the other games. In other games, the rendering process would be like you said; start from things farthest away and rendering until you get close to the player. Abrash and Caramack implemented Binary Space Partition (BSP) tree creation that was used to quickly figure out which part of the maps did not even have to be considered to render.

This is a great link showing how the BSP was referenced all the time during gameplay and how the calculations worked.

http://fabiensanglard.net/doomIphone/doomClassicRenderer.php

I think you also might be interested in buying my fav book, Michael Abrash's Graphics Programming Black Book. It has a lot of discussion on 3d engines including how the DOOM/QUAKE engines were built and their weaknesses but also includes anecdotes during their development. Quake still used BSPs, but built a whole new process (QVIS) where the compiling calculated exactly what surfaces a player could see from any position in the map and know which surfaces to load because they might see it soon (like rounding a corner).

https://www.amazon.com/Michael-Abrashs-Graphics-Programming-Special/dp/1576101746

u/reichbc · 1 pointr/IWantToLearn

Adobe InDesign CS6 Classroom-in-a-Book

This is how I got started. Available in paperback and e-book. SUPER easy to follow step by step guides. It's a very nice way to give yourself a swift crash course.

u/iamanetizen · 1 pointr/programming

I completely understand how you feel. I was in the same shoes. I picked up the following two books very recently & finished them cover to cover. I would strongly recommend them to you. Both books are very easy read & should not be a problem to finish them in weeks.

  1. Learning web design - Jennifer Niederst Robbins - This is a beginners book on web design.
    2 Bulletproof web design - Dan Cederholm - This is bit advanced & shows best practices in CSS. Again a very good read.
    Finally, my own blog article on HTML & CSS authoring that I wrote a few days ago if you care to read.
u/toxicvarn90 · 1 pointr/programming

If I learned one thing from designing this site is that all you've gotta know about CSS is that you are changing the attributes for certain components. If you got the simple syntax down, all you've gotta do is look at cheat sheets or have a WYSIWYG do the customizing for you.

What gets tough about CSS is layout, making it work for all browsers, making graphics (I know little about photoshop and just follow tutorials), and getting what you want with CSS' limitations (especially for a site you didn't HTML for). I haven't even learned advance selection!

I'd recommend this book, which I have yet to get back from the library.

BTW is ASP.net/C# any good and worth learning?

u/jabonko · 1 pointr/bookbinding

When you say hole placement - are you talking about the holes in the sections (textblock)? The cover has slits rather than holes: I'm basing it off the design in Keith Smith's book Books without paste or glue.

> with practice you'll find a way that works for you.

I like hearing that. :)

u/lookatthesource · 1 pointr/Marijuana

A bale of cocogro or cocotek, some CannaCoco A&B or BioVega+BioFlores for organic , some Garden Lime from Lowes, a tent, an led, a light timer, a carbon filter and fan, and a guide book.


Ask Ed's coco guide works well for basics


Micks Coco guide is also good using just MaxiBloom

u/abhisharma2 · 1 pointr/webdev

I think getting a baseline of UX fundamentals is much needed, otherwise you'll be copying other UI patterns that won't necessarily work for your site. I would suggest "100 Things Every Designer Needs To Know About People" by Dr. Susan Weinschenk. And after that, learn how to sketch out layout and UI patterns by hand. It's shocking how much you'll start to question your layout just by that 15 minute exercise instead of diving right into a Bootstrap theme.

http://www.amazon.com/Things-Designer-People-Voices-Matter/dp/0321767535

u/robsnell · 1 pointr/programming

I love Susan Weinschenk!

This list quotes from her book: http://www.amazon.com/dp/0321767535/ref=rdr_ext_tmb

See page 193.

/edited.

u/PriscaDoulos · 1 pointr/gaming

I was more surprised by Michael Abrash, the guy is a genius when it comes to assembly and was essential to the development of Quake, even AutoCAD's line drawing algorithm from when there was no hardware acceleration is his creation. That book is worth reading even with the assembly part being outdated, merely because of the historical side and the creativity he shows to optimize solving problems.

u/dutchpassion · 1 pointr/trees
u/rajittheqeek · 1 pointr/css

I think it's good to balance practice and theory so I'd recommend making room for reading up/studying.

I used Cascading Style Sheets, The Definitive Guide, but it's pretty old now.

u/shilabula · 1 pointr/eldertrees

There are some good books to get going - this is one of the easiest and best written:

Marijuana Grower's Handbook: Your Complete Guide for Medical and Personal Marijuana Cultivation

u/TashaMoon · 1 pointr/eroticauthors

Well... it's hard because I have two different approaches to novels. The one I have for my non-romance plot stuff and the new one I'm developing for romance. All that terminology "pinch points" "inciting incidents" makes me want to puke. I don't bother with that. I'm sure when people told stories hundreds of years ago around the campfire they didn't worry about pinch points.

I keep a few things in mind (and this will be different for romance sort of)

  1. What does my character want most?
  2. What does she need to do to get it?
  3. What is the worst thing (or things) that can stop them from getting it?

    If you can make a good story... you don't need to worry about those 'pinch points' it will just sort of happen. If that makes sense. I guess what I'm saying is when people tell stories they didn't sit down and think "hmm what is my pinch point?" Instead, they came up with their characters, and a story. Be a storyteller. Not a story analyzer (is that a thing?) Don't let yourself get wrapped in analyzing or terminology that your reader doesn't know or care about anyway. Tell a story with good characters and you'll win.

    Now with romance, I'm still learning... it's a harder beast imo to plot/plan. (If you have KU these might be of some help.) I've read this:
    http://www.amazon.com/Busy-Writers-Tips-Writing-Romance-ebook/dp/B009HUQ8KK/ref=sr_1_25?s=digital-text&ie=UTF8&qid=1449616072&sr=1-25&keywords=writing+romance

    And
    http://www.amazon.com/KEEP-YOUR-PANTS-OUTLINE-INTUITIVE-ebook/dp/B018688KPY/ref=sr_1_56?s=digital-text&ie=UTF8&qid=1449616122&sr=1-56&keywords=writing+romance

    And there is some helpful info in there... might need to dig a little but it helped me figure out my 'plan' for plotting romances without worrying about what pinch point really means.

    To sum up, don't get bogged down, just tell a story about the characters. Get them together, love love love, kiss kiss kiss, pull them apart and make them find their way together again. Swoon. After all, romance is more about the characters than anything else anyway.

    This is what works for me but some people may disagree. I'll let you know how it works for me when I'm taking a bath in all my money. :)
u/calamityjay · 1 pointr/Printing

You should really calibrate to the stock and create an output profile for each stock you use.

This page should be a good resource to delve into the print world:
http://colorremedies.com/realworldcolor/downloads.html
Granger rainbow and rgb explorer are in this page somewhere to download for free.

Also, read this book: Real World Color Management (2nd Edition) https://www.amazon.com/dp/0321267222/ref=cm_sw_r_cp_apa_BweXzbSD9Y08P

Most of the time coated swop will suffice. 😉

u/an_ancient_cyclops00 · 1 pointr/truegaming

Also read up on Abrash's book.

http://www.amazon.com/books/dp/1576101746

The last couple chapters goes into when Abrash was with iD and was there with Carmack when he was coming up with the following: " Optimized solutions to 3-D graphics problems from texture mapping, hidden surface removal, and Binary Space Partitioning (BSP) trees are explained."

u/shitballsandgravy · 1 pointr/web_design

This is the best CSS book I've ever read. It's more or less what made CSS click for me after learning from places like w3schools. How it teaches by example was perfect for me. The Zen of CSS Design: Visual Enlightenment for the Web

u/Capolan · 1 pointr/AskReddit

you could start with dreamweaver, but its not free and you'll have to learn it - however knowledge of it pays off. But there are alternatives...

beginner HTML - check out kompozer - http://kompozer.net/ this will let you get away with not learning anything...

more advanced? - lot of my developers use HTML-KIT http://www.htmlkit.com/

In the agencies I've been in - no one uses Dreamweaver, they're all in things like HTML-kit (which is really popular it seems) and some were using plugins for ECLIPSE.

CSS - without question. start here: http://www.csszengarden.com/
Read this book if you can: http://www.amazon.com/Transcending-CSS-Fine-Art-Design/dp/0321410971/ref=sr_1_2?ie=UTF8&s=books&qid=1255578225&sr=8-2

avoid tables at all costs unless you have data that actually needs to be in table form..but don't style with them.

Read this book if you can: http://www.amazon.com/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?ie=UTF8&s=books&qid=1255578275&sr=1-1

as far as flash goes, its a fantastic thing to know. are you into code? if so learn AS3 - its where all flash is going. If you want easier flash to learn, the "timeline based" standard flash would suit you well.

Also - check out javascript animation - things like JQUERY make stuff possible that looks like flash, but isn't. very cool.

and if you don't want to do any of this - just go get a template somewhere ( http://www.templatemonster.com/ ) and fill it in. get some photos from istock and poof - Mcwebsite. slap some google analytics code into the site and you now have tracking for your Mcwebsite.





My experience? - I produced quite a few large company websites (+$80,000.00 sites), and have worked with and hired designers and developers many times. I personally don't do any of the things they do, but I know what tools they choose to use in professional situations.

u/emerca20 · 1 pointr/colorists

For starters, I think this book has helped me a lot:
Color Correction Handbook: Professional Techniques for Video and Cinema (2nd Edition) (Digital Video & Audio Editing Courses) https://www.amazon.com/dp/0321929667/ref=cm_sw_r_cp_apa_i_RYrXCbSPFBN3C

... And I found this book super helpful as well, it's less about grading and look development and more about the technical bits: (full disclaimer, I haven't finished it, it was at my school's library so I was reading it in bursts)

Real World Color Management (2nd Edition) https://www.amazon.com/dp/0321267222/ref=cm_sw_r_cp_apa_i_u0rXCbKEE8JQE

u/Madsy9 · 1 pointr/opengl

You didn't post a question, so it's difficult to know what exactly you want. If you just need to implement space partitioning with a BSP tree, read the good old BSP FAQ

If you need more general graphics background, check out:

  • Websites like Flipcode and GameDev.net

  • Buy some books. GraphicsGems and Michael Abrash's Graphics Programming Black Book are maybe old, and the code examples are certainly outdated (They are from the old MS-DOS mode 13h VGA days), but they are excellent in teaching you the fundamentals of computer graphics theory that never gets old. Like how polygon rasterizers work, space partitioning, polygon clipping, etc. When you want to learn more about more advanced effects, look into the Real-Time Rendering series. For a slightly more updated book on the same topic, check out 3D Math Primer for Graphics and Game Development, but I think it's a bit thin for the price (I have the 1st edition myself).

  • Forums with people who actually specializes in computer graphics, like Ompf2 and DevMaster

    If you have more questions, please be more specific. I might help you with more resources.
u/pointer2void · 1 pointr/programming
u/flehrad · 1 pointr/technicalwriting

Auto spam filter caught this post because of the shortcut link.
If you're suspicious of the shortened URL, the link refers to : https://www.amazon.com/Developing-Quality-Technical-Information-Handbook/dp/0133118975

u/treefarmercharlie · 1 pointr/microgrowery

I would highly recommend getting this book. There are a lot of good websites, too, but I've personally learned more from that book than from any of the websites.

u/blktiger · 1 pointr/programming

The Zen of CSS is a great book.

u/doctahaze · 1 pointr/microgrowery

They teach Ed Rosenthal apparently at Oaksterdam University in Cali.

https://www.amazon.com/gp/aw/d/0932551467/ref=dbs_a_w_dp_0932551467

I found all the popular grow books on Library Genesis too.

u/LuluDarkWing · 1 pointr/graphic_design

I recommend this book: The Zen of CSS Design: Visual Enlightenment for the Web

And checking out the website for it: css Zen Garden

This is a good site too, that I find a lot of my searches for how to do a certain something lead me there: http://css-tricks.com/

u/logicalriot · 0 pointsr/web_design

This book really helped me out when I first got started. David Shea is a real talent. CSS Zen Garden