gameguy43

:(

Ok, time to rethink the email opt-ins.

Really helpful to hear. We were worried about it but thought "once you get into reading the piece you'll probably just forget it's there, right?"

We're really focused on trying to "twist the knobs" only up to the point right /before/ it starts getting annoying.

Thanks for the note. Definitely a great point. Not sure yet how we tier out our product, but tiered pricing is definitely the state of the art.

We've been working on some /tech/ to enable tiered pricing in the meantime. The Site's all custom, and so far there's no notion of a "product" yet...just "paid" and "unpaid."

Share your question re: where's Kaplan on this stuff!

Original Author here. Happy to answer questions about this piece or coding interviews in general!

And eager to receive any feedback.

Thanks for the post!

Something on data structures and algorithms.

I like /coding interview/ resources for this, because they skip the proofs and get to the point faster.

Cracking the coding interview is good So is interviewcake.com (disclosure: I made it)

Read the first 3 points, saw they had nothing to do with the headline, and bounced.

Super interesting comparing this to the one we have on Interview Cake: https://www.interviewcake.com/article/big-o-notation-time-an...

I like how Rob Bell's piece has headings with the most common time costs--sorta makes it easier to see at a glance what you're going to get, and I imagine gives folks a quick sense of, "Right, I've seen that! Been /wondering/ what that means."

Aline Lerner! Former engineer. No bullshit. http://blog.alinelerner.com/

Surprised nobody has mentioned this yet: be careful about that non-promise of a "possibility of getting a bit more into actual software development later."

It's very easy for a company to make vague non-promises like this. Consider how you would feel if it took 1 year or 2 years or infinite years for that "getting a bit more into actual software development" thing to happen. Would you quit after a year of waiting? Would you feel like you had wasted your time?

Something to consider.

"buy a t-shirt!"

"I buy a t-shirt >>"

This is my new favorite web copy trope.

Don't copy that floppy!

This. I added https to my site to get users to stop worrying, but AFAIK you don't need it with Stripe.

Oh maaaaan the old graylog2 site had probably my /favorite/ branding in all of software. The heading was "Manage your logs in the dark and have lasers going and make it look like you're from space."

https://web.archive.org/web/20130302051347/http://graylog2.o...

Sad to see it's gone all "professional" now :(

The web service had some hilarious bits too. Does it still say "enraging gorillas... | mounting party hats" etc when you log in?

Thanks!

(I'mma wait on pushing the fix until traffic dies down a bit.)

When I saw your username I was really hoping your comment was going to be about how back in your day you'd "subscribe to podcasts" by adding an rsync to your crontab (and hopefully something something FTP).

Almost.

Yeah, this is what I meant by my confusing question above.

"Apple Pay doesn’t replace In-App Purchases. You should use Apple Pay when charging for physical goods (such as groceries, clothing, and appliances) or for services (such as club memberships, hotel reservations, and tickets for events). You should continue to use In-App Purchases to charge for virtual goods such as premium content in your app."

Anyone understand why this is? Is there a reason I shouldn't let my users use Apple Pay to buy the freemium digital content on my website?

I don't quite understand what capitalized In-App Purchases means...oh, maybe Apple Pay is only possible from an app, not from a mobile web browser? Is that true? (But like, why?)

Great work. Reminds me of Choc, an implementation of Bret Victor's Learnable Programming: http://www.fullstack.io/choc/

I'm really interested in solutions for visually explaining what an algorithm does. Anyone have any other resources they like?

Agreed. I'm working on an "advanced" follow-up that digs into log n and a couple other things!

Agreed. I'm trying to strike a balance here between painting the full picture and being approachable for people who are scared of math. These notes are super helpful though--we can probably nod briefly to this complexity without getting /too/ stuck in the weeds. Really appreciate the thoughts!

Ah, gotcha. I'll patch that up. Thanks!

Hm, sounds like a bug. Which example are you referring to?

There are echoes of some zen/meditation ideas in here. I'm just starting to get into that kind of stuff. Curious to hear if Paul meditates, and what resources he (and other HNers) recommend for getting into it.

Love this. I wish more recruiters were this data-driven.

Not Sam's (and pg's) usual style of super-pithy and easy-to-read writing. Did this get rushed out the door?

I like skeuocard's experience a lot. But it's not responsive, so it was a no-go for me. Ended up rolling my own.

One great optimization skeuocard has is it only asks for the cc# at first, then the other fields appear as you type it in. So the form is less daunting at first.

I think there's some truth to this. Companies should weigh past work more heavily, and let candidates do real work with the team as part of the interview process, IMO.

That being said, I think these whiteboard problems can be useful when you think of them as "trying out what it feels like to brainstorm with the candidate about how to solve a problem." That's how I think of them. There are plenty of people I just can't get on the same page with when trying to whiteboard together (different communication styles/speeds/whatever), and it's helpful to know that ahead of time.

Hey there,

The problems are definitely a bit more advanced. I do try to make sure that any "vocab words" (data structures, algorithm types) can be clicked on for a deeper explanation. But if you haven't seen big-o before, for example, you'll be in the dark on a few things right now. I have some more "bottom-up" curriculum that I've developed from teaching at boot camps around San Francisco, and I'm still working on figuring out the best way to present it on the site.

For Big-o specifically (the thing that looks like "O(n)"), I really like these resources: http://stackoverflow.com/questions/487258/plain-english-expl... http://www.perlmonks.org/?node_id=227909 http://www.daveperrett.com/articles/2010/12/07/comp-sci-101-...

Best of luck!

Man, can I get your help writing sales copy? :P

Hey there! Yep, bootstrap and angularjs in the front, Django in the back. Cloudfront CDN to handle the static assets (I've /really/ fallen in love with their product--so easy to set up). And of course, Stripe for payments.