174 karma · joined January 8, 2016
*just noticed I was down voted, likely by MichaelApproved because he has 7500 Karma and I only have 156.
I'm starting to really hate contributing to HackerNews discussions because it's fully of a bunch of bullies who pound on your karma if you don't agree with their viewpoints. Bring on the downvotes, I know HN hates any mention of it's imperfections as well. At least my conscious is clear.
As opposed to something like go, which compiles in seconds typically. Naturally, different folks will have different experiences depending on how it's used. For myself, the long compile time was a turn off.
Other than that, it awesome how it works with so many data storage providers. If it helps anyone, the last time I looked at pricing (a couple months ago) IBM had the cheapest per GB cloud storage of all the providers. I already have 1TB of Google Cloud for $2/mo, so I'm using that to keep my life simple, however, it's slow as far as data stores go.
how will the API work for developers? Personally I think the attention Slack put into their API is the reason it is so popular and will continue to own the space until there is a competitor with their api/bot building abilities.
That aside, their monetary policy has also been a train wreck from the 70's, and compounded with more bad decisions in the early 2000's. https://mises.org/wire/venezuelas-economic-collapse-was-enab...
Until they fix core issues in their central government/bank, they will continue to struggle in a global economy.
I also baked a 25+service AI platform onto 4 virtual machines, running kubernetes, for deployment in an air-gapped system without a knowladgable operator. It was an excellent choice for that project because of the auto-healing capabilities.
I have also run it at a small startup where we had a combination of static nginx sites, ruby on rails sites, elixer sights, node.js app, and even a c++ app. (it was at a crypto company if you are wondering why so many disparate languages). Having a single deploy pipeline for 5+ different languages and architectures was awesome. I would have killed myself if I needed to support all of those in their native environments at the same time.
There are lots of good use cases for k8s, and honestly it's not that hard if you already have system admin skills because you understand the problems it solves and how it works. Most of the folks I have seen struggle with it are developers (and likewise, I struggle with OOP sometimes - i don't mean to diminish developers skills).
So.....basically nothing has changed and the headline is extremely misleading.
Edit: so apparently this applies to the "subject" tests. I never took those and didn't know they were a thing, now I do.
The question was "why higher less senior people?" My answer, and perhaps I wasn't clear, was that for your first 1-5 devs, you should definitely higher senior...but once you break past that then your senior devs - you know the ones who launched all that boring technology - then want Jr devs to mold into doing things the right way from the start.