OhHeyItsE
Joined 13 years ago
Joined 13 years ago
For years AWS was the cloud, and the only viable option.
At the same time that traditionally non-technical (or at least not tech-first) companies are coming around to the idea of moving to the cloud, there are alternatives for the first time ever.
Amazon is now a major player in ecommerce, perishable/grocery and digital media content (both delivery and production). Companies in those verticals are hesitant to move to AWS, some are already outright refusing. This is where the opportunity for competitors lies.
Edit: was mentioned, about 13 hours before I did https://news.ycombinator.com/item?id=19149933
Freudian slip? :)
The caffeine part is particularly bad advice, as a stimulant is the last thing you want to ingest when you are already highly agitated.
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...
[...right?]
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.
http://www.nj.com/news/index.ssf/2016/03/the_story_behind_br...
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.
Pretty sure the candidate is supposed to ask the interviewer that one...