Recent submissions

Comment · 7 years ago
> 9. How do you maintain a work-life balance?

Pretty sure the candidate is supposed to ask the interviewer that one...

Comment · 7 years ago
Hypothetical: individual pricing based on how likely you are to pay more for an item, or how badly they think you need it. Sharing of data across domains could place you in a "bubble" where you see the same price no matter where you look.
Comment · 7 years ago
Comment · 8 years ago
> the ICO should have given them pause

Freudian slip? :)

Comment · 8 years ago
Agree 100% in principle, but just want to PSA that 1-2mg of Xanax is a fairly hefty dose.
Comment · 8 years ago
Urban legend. Not true at all. Nothing can kill a trip except time. Not even Xanax - it will just help you relax and kill the panic and anxiety.

The caffeine part is particularly bad advice, as a stimulant is the last thing you want to ingest when you are already highly agitated.

Comment · 8 years ago
I always wonder where the myth that older developers are "slower" comes from.

Dunno about you folks, but I get better and faster every year. And, for me, that productivity metric is probably approaching parabolic.

You learn enough languages, frameworks, tools - all the fundamentals start to merge together. You can pick the next one up faster than you did the one you just put down. You understand how to design software; how to organize code. Exactly when to reuse, refactor, or copy/paste.

You have a better understanding of how the market works and the competitive strategies around product development will manifest - not only within your own product and industry, but when analyzing and choosing vendors as well (you really want to leave it up to a 25 year-old to choose AWS vs GCP?).

Sure, I've got a ton of better things to spend my nights and weekends on than writing code for free. I can also spot a doomed project from a mile a way and have no qualms about delivering a very curt "yeah no thanks" to that project manager who waddles over with some deluded hero fantasy where they carry the flag on my back for something that's probably never going to see the light of day anyway.

Maybe that's it? That's probably it...

Comment · 8 years ago
This is good for Bitcoin.

[...right?]

Comment · 8 years ago
> Put aside what devs at your company may already be comfortable with

At your peril. Sorry, but it's true.

Any time there is something even slightly amiss it's going to be "Uh oh - looks like Mongo is giving us trouble again."

No matter what the real problem is a slam-dunk scapegoat. And your name is going to be forever attached to it.

Also consider how you're going to deploy & maintain the stack itself. Do you have an ops team that's familiar with deploying war files into a servlet container? Well now on the critical path to this thing going live is them learning how to maintain a new app server, language and deployment process?

That said, at the end of the day - all the tools, frameworks, and languages you mentioned are just fine, with some slight nuance:

DB: MySQL is fine, Postgres has some nice additional features if you need them: GIS, great scripting support, etc

API/App: Stick with the big ones (Elixir? C'mon...). Slight edge to Node because JSON de/serialization is automagic. Slight ding to PHP because... PHP.

Frontend: Who cares? It's going to be outdated in 6 weeks anyway.

Caching: Which ever one you don't have to maintain or think about. Did you choose AWS? Great. Elasticache supports Redis and Memcached.

PaaS: Whichever one supports all the features that you need.

Comment · 8 years ago
Comment · 9 years ago
A long-time dream of mine. Am envious. Wish I had the confidence to do it. Wish I knew how to get "Client #1"
Comment · 9 years ago
It's a good idea, but if your product is a website, cookies and authentication in general are going to be a real challenge. Obviously you won't be able to share cookies between the site and the api. But you have the additional challenge of having your api domain treated as 3rd party and are thus subject to all the security measures and sandboxing that come with that.

And what if your product is just an api for use by developers? Now the api is part of your brand.

It's just a bad situation all around.

Comment · 9 years ago
I've found that companies that are serious about this will offer some form of compensation (gift card, etc)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton