salsakran

It's a natural state which most django codebases tend towards. There's a natural Views use ModelForms use Models data flow which leads to bloat somewhere in that chain as you add code. Fat models are easiest to test and the natural place to put most things, but eventually massive models get unwieldly and you start putting things into helpers. The core thing the author seems to have conflate util functions that have access to a request and helpers that have no connection to the request/response cycle.

Cognitive dissonance much?

All of these look at returns that predate the "new angel age" of the last couple of years. Every hot bubble looks great using metrics collected before world+dog pile in.

You're better off going to the next investor cold (or just do the leg work and get to them from a different direction) than via an introduction that reads "here's this deal I passed on".

It's a stable, well understood DB vs an immature, not well understood DB AND 1KLOC to deal with not being consistent.

To be clear, I'm not saying any given DB is the OneTrueWay, just that people seem to be a bit cavalier in regards to some of this crap and chasing the newest shiny thing while rediscovering why some of the braindamage in those 1MLOC was put there in the first place.

This is backwards. Multi-DC capability is a feature. Eventual Consistency is an explicit tradeoff in a desired characteristic (Consistency) to allow other features.

I'm not exactly a SQL fanboy, but maybe ACID is kinda useful in situations like this and having to write your own application land 1000 liners for stuff that got solved in SQL land decades ago isn't the best use of time?

If a PaaS can't beat the internal price (including time, hiring ops people,etc), they're fighting a losing battle.

People drastically underestimate the effort required to make a PaaS platform and drastically overestimate people's willingness to pay. It's a dogfight of a market with brutal economics.

The idea that people will casually do this is ... hilarious.

Scaling a static Q/A site with a few widgets that require user info/counters should be table stakes.

If you aren't able to do such basic things correctly on the spot, I simply can't trust you to check in complex/highly concurrent/etc code that works. As an IC developer I don't want to deal with your code or clean up your mistakes. As a manager, I can't trust you to write code unsupervised.

This quote in particular would be a massive red flag and probably the end of an interview: "it is more appropriate that I understand how it should be used, it's pro's and con's and all it's supporting functions". In most companies, what's being sought is not someone who can just use the tools as appropriate. It's someone who can develop new tools and solve problems for which there isn't a pre-canned answer available. If you don't know how to solve the problems for which trivial answers exist, how can anyone expect you to be able to reason through truly novel and difficult problems.

The sort of attitude you're espousing is perfectly fine for large ERP/custom corporate app/corporate website/etc programming work. It's just not what people in the valley are doing.

This should be the sort of thing anyone looking for a programming job should be able to do as the programming equivalent of muscle memory.

I believe Heroku used EC2 under the hood before the Salesforce acquisition.

Whether postgres (vs MySQL), the polish and better ui/workflow of heroku is worth the premium over RDS depends on you.

They've had BerkeleyDB since 2006. The real issue is not technology so much as economics. The heart of the matter is that no startup is going to shell out what Oracle wants for licensing/support contracts.

do you mean taking historical snapshots and saving them?

I imagine if he had seen something like Play!, he'd have a very different opinion.

Keep training jiu jitsu, maintain social relationships, chase girls (or boys or whatever) and make sure you allocate time to keeping yourself healthy - physically, mentally and emotionally. For most people that means a social network (not the facebook kind) to keep you grounded.

Otherwise, pick a hobby, preferably one that is social but where you won't be tempted to spend escalating time on it. Sports league, dance, improv, whatever.