What are your favorite colors to contrast with each other?

Black and Pink Wallpaper for bedroom

Oh man, you read my mind.

Color combos are important and influence mood.

Here are my faves:,BLUE AND BROWN:,blue, brown and gold wallpaper:,SEA COLORS- gray combined with light blues mostly or the ever popular BLUE AND GREEN:,Ok, what else!?,BLACK AND WHITE IS CLASSIC.

Sophisticated if done right.

I adore b&w french tile, though very hard to find now:,Black and green dresses for when youre feeling powerful lol:,Red and pink!!! Energizing as all get out!:,Confession: My bedroom is pink and red.

Good fengshui as well.

Google!

Black and pink background plain

I hate cheesy stock art.

Like, really hate it.

And having designed 7 - 10 book covers (across various editions), plus having picked images for blog posts and articles, Ive seen a lot of stock art.

,Ask designers to create a book cover for an interview book and theyll put images like briefcases, men in suits and ties, or maybe even some cheesy question marks.

,If you tell them its about programming, theyll make the book cover black and green and throw in some matrix-style binary code.

Or put a big picture of a brain.

Or a puzzle.

Or a computer or iPhone.

,Essentially, any image that makes immediate logical sense makes me want to vomit a little.

So cross those out.

,What youre left with is getting something that has the right feel, where that could be any number of things.

,With all that said, here are the stories behind the covers for Cracking the Coding Interview 5th edition, Cracking the PM Interview, Cracking the Tech Career, and Cracking the Coding Interview 6th edition.

,These are in chronological order, because each led to the next.

,,Cracking the Coding Interview, 5th editionI wanted an image that gave it a textbook-y / science-y feel.

CtCI was just starting to establish itself as the programming interview book, but it did not have that track record.

,Some history is useful here.

The thing that eventually became Cracking the Coding Interview was not, at first, what one would really call a book.

It was a little 20 page PDF, released almost on a whim.

It was actually called something else.

It didnt even have solutions.

,That little whim was surprisingly well received, so I kept working on it.

There were a bunch of incremental updates, but three of those involved more major changes.

I retroactively called those editions.

Thats why the first physical edition on Amazon was the 4th edition.

,It made sense at the time, but if I could do it all over again, I would have reset the numbering on its first paperback edition.

The 4th should have been called the 1st (arguably more like a beta) and the 5th should have been called the 2nd.

Oh well.

Hindsight is 20/20!,All this is to say that when I was releasing the 5th edition, it had come after a whole series of alpha / beta releases.

I wanted a cover that separated it from this history.

I wanted something that suggested legitimacy.

,It came down to two designs.

I liked both about equally, but decided on the first one since I figured there was a higher chance of eventually despising the stock-art-y-ness of the second one.

Something that I would continue to tolerate was high priority.

,,Cracking the PM InterviewThe next book I released was Cracking the PM Interview.

,Now that I had what could arguably be called a series, I wanted a cover that could represent this.

The problem was that there werent design elements from Cracking the Coding Interview, 5th edition that would work for Cracking the PM Interview.

,So I took the opposite approach.

I created a fresh design for Cracking the PM Interview, knowing that Id reuse some elements for Cracking the Coding Interview, 6th edition -- then a distant thought.

,I like the single-image-on-solid background, so I stuck with that.

,I wanted something bold and unique.

Thats why its bright orange.

How many orange book covers do you see?,I figured that itd be nice if theres some justification behind the image, but that wasnt super high priority.

As I said, I tend to hate the images that immediately make sense, since Ive seen them too many times.

,My co-author Jackie Bavaro suggested playing with some interview questions or other PM-y phrases (wearing lots of hats, alarm clock for the blind, etc).

,That eventually led to this cover:,Here were some of the other options.

These are in rough draft (very unpolished) form, since we didnt go with them:,,Cracking the Tech CareerThis was actually a new edition of The Google Resume, not a brand new book.

I would have been just fine with taking the same image from The Google Resume, but it wasnt up to me.

While Cracking the Coding Interview and Cracking the PM Interview are published independently by me, The Google Resume/Cracking the Tech Career are published via Wiley.

So now we have to -- eek! -- compromise.

,The work should have been easy.

Take the style from the Cracking the PM Interview, pick a new color and image, and were done.

,The background color was immediately decided to be either green or blue.

What else would you use? Orange was already in use, and red would be too similar.

Purple and pink would be too girly.

White and black are too plain.

,Wiley wanted an image that made sense and offered a bunch of options, almost all of which looked like cheesy stock art to me.

After much discussion, we compromised on this:,,Cracking the Coding Interview, 6th EditionThe style was already locked in.

The background color probably had to be green, since Cracking the Tech Career took blue.

Just needed an image!,I posted a contest on 99designs.

com and described, very clearly, the rules: new image, new background color, change nothing else.

The image doesnt need to really make sense.

And, for the love of all that is good, no men in suits, no puzzle pieces, no briefcases, no eggs cracking, and no question marks.

,A ton of bad options and a small handful of good ones rolled in.

There were also a shocking number which failed to follow the instructions.

,The one on the left wasnt bad -- a bit mathy, but Im not so sure about the flower.

The second one is too similar to the Visual Studio logo.

The third one is too stock-arty.

The fourth one was sort of random, but thats fine.

The fifth one was too cheesy.

,Many more came in.

Some were comically bad.

,Then this came in.

My first reaction was, Huh? You just tweaked the image from my PM book.

Cant you at least come up with something on your own?,Then it clicked.

It makes a ton of sense.

The PM is designing the outside stuff of the clock, while the coder is doing the inner part -- the gears.

,Love it.

,A few iterations later, and here we are: