Feeling you. If big goals are your view I wouldn't be dissuaded from that too much. Find the right job. I have a friend who likes to describe himself as 'a builder' when asked what he does (He's a dev). It's worth remembering that this job is to a large degree characterised by building things in a way that many jobs aren't (doctor, lawyer, etc..).

If you notice there's a lot of maintenance/feature churn it only feels wrong because you know it's in the dna of the job to be more so go and find the early stage projects where it is.

It's also worth remembering that time spent churning round fresh ways to do similar things is why your site doesn't look like one of those corporate embarrassments that has supposedly been continuously developed but doesn't look to have changed in 15 years.

@guru Yup, push from the server is exactly what's nice about web sockets.

Yeah I'm a recovering 'that guy'. Sometimes it comes out that way coz I'm too tired to figure out how to make it not like that.

Other times I'm too alert to remember that correct and concise use of a wide standard library vocabulary won't be so much fun when I go back on a tired day and can't remember what 'slice' does and what prick wrote this.

Because if it's now that you're seriously on the edge of bailing that there is the self-sabotage monster. The task is not the course anymore it's being 'Zen' (whatever that means), handling boredom, bullshit and more so as to win.

@willol speaks truth. If well setup, the database is the guru on how to efficiently get what you want and SQL is its native language. You can talk to it with just an ORM like in laravel. It'll work but it's like trying to rephrase Shakespeare into Donald Trumpisms. You'll just need a lot more of them to get the whole meaning across.

But that analogy goes both ways. Never go for Shakespeare when a short, blunt Trumpism can say the same.

I get your pain although recursion can be the prettiest way to solve something. Unfortunately, I find the really pretty examples are the ones most likely to blow your stack.

e.g. Tail recursion is the only kind where in some languages you categorically don't need to worry about this problem because the optimizer will rewrite so that it's not actually recursion. Of course, these are the ones you could rewrite yourself to not recursion so you don't blow your own personal internal callstack.

The nice uses that save many lines of code are like where each call of the function spawns another 4 of itself going off in different directions. Cute but that callstack is in for pain.

I'll bet you love haml templates

So let me get this straight. Someone is going to pay you significant money to learn another highly marketable skill? Something that right now there are thousands of people paying even more significant money in bootcamp to learn? Having trouble bringing up the sympathy here.

@KnightsOfCode yeah I'd vote for money high + time low = many unused raspberry pis.

There are lots of things that are so easy once you know how that it's easy to forget what it was like before knowing how. Remember that the permutations of each of these forks in the road are multiplicative not additive. 5 sets of crossroads could make 1000 possible wrong destinations.

God, back to work you slackers! There's ntiles to be solved.

On that note I've not used ntile either but it'd be a pretty tricky problem for a DB to implement on live data so I'm not surprised if it screws up. Are you using nolock or read uncommitted anywhere in that query? That can cause double reads but sometimes so can standard read committed.

AWS IS FINE. The status board would not betray us.

@Greggergalactic @tommy Yeah I'd get behind this. For years I thought listening to certain kinds of music made me code faster and better. Eventually I realised it probably was distracting and slowing me down but at least it kept me in a good mood so I didn't hit that ditch you're talking about. Doesn't always work...