2,511 karma · joined July 7, 2018
The only way to have a decent job in Spain is by working for a foreign company (as a remote worker or FTE if they have a spanish office) from which you can get a decent salary and work conditions or creating your own company if you’re successful. Otherwise, working for spanish companies in Spain is most of the times a death sentence and may as well make you hate your job forever.
Consider also dust mites allergy and do extensive cleaning where you sleep and see if that helps.
[1] https://www.hostingmanual.net/3-seconds-how-website-speed-im...
>Perhaps in few areas there are some support but it's not what Nomad intends to do anyway
Look, I think we can agree that K8s have many features that Nomad don't and that's just how it is (not good or bad, just different). This comes with added complexity. If you wanted to have all these features in Nomad it'd cost you a lot to the point of being impractical. "I don't need all of those" then don't use K8s - but then don't complain when you bring a vast machine that does 1000 things to do 100 and complain it's too complex.
Everything else - I literally said "K8s is enterprise stuff". Now if we go to specifics then it depends of what the company does, maybe they'd do just fine with Nomad or a managed solution like ECS.
>If you want Kubernetes it's probably a better idea to use a hosted Kubernetes solution like Google's offering.
Well I agree? All of the big companies I've been in used EKS and before EKS was decent there was some maintenance overhead. It'd still be less than the maintenance overhead to maintain the full list of features that K8s provides with Nomad, as Nomad doesn't provide any of those and you'd need to seek solutions outside of the product and try to fit them in.
The same way you'd not buy a car if you're going to drive yourself quarter of a mile once a week, you'd not use such a complex solution to run a few dozen containers.
Some are mentioned in the post but I can think of secret management, load balancing, config management, routing, orchestration beyond workloads (e.g. storage), rollbacks/rollouts and many more. Perhaps in few areas there are some support but it's not what Nomad intends to do anyway. I also like these points from another comment: https://news.ycombinator.com/item?id=26142658
In order to supply those needs in Nomad you'll need to spend time finding out how to integrate different solutions, keep them up-to-date, etc. At that point, K8s may be a better answer. If you don't need any of those, use Nomad or anything else that's simpler (e.g. ECS if you're in AWS, K3s if that's simple enough for your home server, etc).
K8s is enterprise stuff and should be seen as such. It's complex because the problems that are being attempted to solve are complex and varied. That doesn't discount that Nomad is a great piece of software though.
As a counterpoint, in my experience of a bunch of years with Scaleway they have always worked quite well. I left them due to the price getting out of hand.
This is something I want to highlight. I know we’re not all product managers but as people working in tech we should be able to take different perspectives and understand that what matters to us doesn’t matter at all for the 99% of the people outside our tech world.
Perception does matter a lot, and that’s why I used the 1% figure. It means one percent of WhatsApp users are investigating a competitor (not even deleting their account in WhatsApp, but I guess few did) and here people seem to see it as a clear tipping point to which I disagree - raw numbers don’t mean much if you have nothing to compare with.
To put things into perspective, let’s assume that 25M users (as stated in the article) actually moved to Telegram - which I use and like by the way. Let’s assume they fully moved and stopped using WhatsApp (very unlikely). That means less than 1.25% users moved to another platform - and this means assuming many things that aren’t probably real.
It reminds me a bit of the articles about DuckDuckGo vs Google where many people think big changes in usage are happening while ignoring that the average Joe will keep using whatever it’s using unless there’s way too much trouble to continue using it.
[1] https://unric.org/en/finland-first-in-europe-to-use-dogs-to-...
The formula worked and keeps working very well.
Why? The answer is simple: women have plenty of options and also absolute power over those choices so no need to do much - it's a natural, rational and logical choice. Hence the dynamics aren't going to change no matter what tech you apply to the "problem". If you forced somehow to write a more thoughtful initial message, they'd just go to some other app (or the majority anyway).
How I see it is if Bumble grows as much as Tinder, it'd suffer from the same problems. Except that women will receive less initial gross messages (if that's an actual wide issue, I have no idea). Men are left in the same situation, which is how it should be I guess.
You can’t just convince the majority of the users with privacy arguments or even hypothetical extra features from Signal. Only if WhatsApp would introduce something really annoying (huge ads, fees, constant technical issues) people would start to move. But even Telegram which is so much better IMHO (albeit privacy by default isn’t better) will hardly be #1 ever if nothing of the above happens.
When I learned what I said: it takes little time to set it up and you reap the benefits. If you don’t know how to use it then it’ll take some time to learn, in such case I see value going with whatever you know.
>We've been shipping MVPs long before those were a thing.
That reasoning can be used with almost any technology and doesn’t tell anything.
>./deploy.sh runs the commands you used to run manually.
You went from “manually copying” to having a script with reproducible steps. You’re closer to CD than what you were thinking.
I think the rest of the comment doesn't need to be addressed.
>Kubernetes, and Docker and CI? Cool tech, I suppose, but time wasters. Your release process should be scp-ing and extracting a zip file on the prod machine, or git checkout the files.
Ok, let's accept that K8s is overkill most of the times. But containerization and CI/CD? If you've some experience with it you know it's something that takes little time and money to set up (e.g. GitLab CI) and you get tons of benefits - you don't need to get super fancy either.
To me it sounds like the time waster would be doing what you describe, specially because it's so easy to mess it up after you do it a bunch of times on a single day. I used to do that when I started with PHP several years ago (replace scp-ing with FTP and git with cvs or svn) but IMHO it's not worth it once you deploy your product live.
Also I IMHO doubt that Fauci didn’t know about mask effectiveness - sure, maybe he didn’t know the very specifics but it was kind of obvious back then it wasn’t going to harm and one could infer that it’d probably help somewhat (nowadays it’s clear). IMHO all authorities just agreed to transmit a similar message around the world so they could in the meantime arrange more mask orders and sort out the distribution as production speeded up while avoiding massive riots and/or poor masks made at home that could’ve been worse than nothing.
Again I don’t defend these actions, I’m just trying to reason why they decided to go that way and not the most instintive one “let’s be fully transparent” (at least for HN anyway).
Politics is IMHO all or a majority about deception unfortunately and once you accept this these actions just make more sense and you stop playing their silly game. I decided to move to a smaller and more healthy democracy because I knew degeneration of politics back in my (somewhat big) country was only going to get much worse and in some cases that can mean literal death to me and I could do nothing to change it. Well, all this is way too off-topic so let’s leave it for another time as it’s an interesting one :)
And I agree with your last point of course.