askyourmother

There are some very shaky bits in the JS dev arena. Just a little earlier, we read about how a developer unpublished his libraries from NPM, the fallout from this affected numerous high profile projects like node.js, which were relying on a left pad "library" that basically was a small string padding function.

Further affirmation we made the right choice to use PostgreSQL for our DB, which was a tough fight because internal company politics usually require the use of Oracle or MySQL, due to previously agreed licences.

PostgreSQL remains one of those great products that you can argue for and win based on the quality, documentation and performance of the product.

I browse mostly on mobile these days, with JS turned off. Sites load quickly, the small amount of actual content can be quickly consumed, and my monthly data allowance remains in trim.

Before this humungous amounts of JS and adverts blocked the screen, slowed loading times, tried to infect the phone, steal browser history data, and sucked down my data allowance greedily.

I have learnt over the years from personal experience, and watching the outcomes of others, never, ever, accept a deal with an employer where they structure pay or rewards for future payout. Always, always get the payoff or bonus upfront.

They may want to discuss potential claw back contractual clauses, but again, once you starting your own, they will back down.

The biggest eye opener is that you never really "know" an employer till things go wrong and communication goes legal.

The childrens book "Maisy makes gingerbread", it might help the aspiring manager understand that often there is a simple, well understood series of steps to follow, and if we do follow them, we deliver something of value.

If we choose to bog down the process, add unnecessary steps, or shortcut some steps, the end result is perhaps less rewarding.

I agree with you 200% here, but the HN crowd don't seem to be able to even conceive that once cash is gone, it only takes a glitch, a bug (in software? Surely not!), or a malicious action by bank or state, and then you are left in a rather desperate state.

Today the bank can, and had recently, make mistakes, but o can still buy food on the way home thanks to cash.

Life can go on, even when "computer says no".

A lot of js devs came straight to js without any previous language experience. Hence we are seeing lots of ideas and frameworks thrown out there. The worst example is the proliferation of single function libraries, yes, create a js lib for a single function.

It will settle down. Mostly as the devs grow a bit older and wiser, and as the end users start to rebel a bit harder - already non-tech people are publically lamenting js-heavy sites, wondering why so slow to load and run.

Lean js is happy js.

Two recent startups I worked with in London are using C++14 as a main part of their architecture, in addition to Python, JS and Erlang. Its 2016 and performance is back in vogue.

For years we have been told, Developers are expensive, embrace frameworks, ignore the bloat, just ship quick, even if it needs a billion servers to run.

Both firms are building amazing products on very conservative hardware requirements, so they can scale if required, but they actually know and understand their full stack, and it shows.

One had started with too much Python and Go, before realising the error, the other took a detour into JVM country, before getting back onto the main roads with C++.