>Nearly a decade later, new problems arose when Kubernetes (the operating system of the cloud) brought open-source collaboration to a new level.
I'd love to get more context to that statement to understand it better because as it is, it sounds as such an arbitrary statement that undermines the credibility of all the content below.
Kubernetes didn't brought open-source collaboration to a new level. No matter how relevant Kubernetes is today, it's just a drop in the huge ocean of OSS. Maybe level in this context refers to 'gitops' which many of us where doing years before the term was coined and without K8s involved. Or perhaps the author refers to the fact that most gitops K8s frameworks will work via polling which is a fundamental scalability flaw.
Ecosystem-fatigue maybe? I don't know if there is an existing term for this but it's got more and more common and it's going to get a hell lot of more.
As a junior engineer (20+ years ago, for me), anything new is enjoyable. Damn we even enjoyed .NET, J2EE, Perl.. whatever crap. You name it. But today there are so many frameworks, paradigms, tools, services... and sad thing is in many cases the differences are nuance-grade which for senior engineers might become incredibly exhausting, at least in my opinion. "Why would I want to spend 6 months learning Vue if I can do this in React in 6 weeks?", "Why should I learn Rust if I just can do this in C++?"...
I think there are big differences in how industry evolved in the early twenties to today. I think today's evolution can feel rather disappointing.
Note: Spain is preferred for the engineering positions but open to any location for exceptional candidates. US and Spain are ok for the Product Manager position.
At VMware, we are hiring multiple positions to work on several products associated with the Bitnami brand. These products are mostly corporate oriented but have a profound impact in the content that gets generated for the Open Source catalog used by millions of developers in the world.
If you ever wanted to work with Open Source, this is one of the most exciting opportunities out there. Bitnami is one of the top Open Source publishers in the world. Some of our containers have been downloaded more than 1.5 billion times and usage is growing exponentially every month.
For coping with this task we have started an initiative to renew our internal supply chain, increasing its ability to scale and meet the incredible demand that we are having both from corporate customers and the ISV publishers.
Our stack is modern Java based. That is Java 16 (moving now to 17) + Spring Boot + Microservices. We run in AWS and Kubernetes and we practice Continuous Delivery. Our core is built around the principles of DDD with a centralised event bus that all micro services use to choreograph themselves. We believe in sound engineering practices and evolutionary architectures. Everyone in the team has a saying and there is no ivory tower leaders that impose thoughts.
We have several positions open. All of them are full-remote and aiming to hire senior high level pre-staff positions that would be able to move to Staff level in two/three years. The salary depends on the country and the level so it is hard to put a specific band there but it is along the lines of what you would expect from a top tech company: Country above-average base salary + stock + options + health insurance + stock purchase plans + wellbeing + food tickets + generous holidays.
I'm linking here some public openings that we have but if you have any more questions or want to ping me directly for help with the application don't hesitate reaching out to me at [email protected]
I'm not sure if this is just my personal feeling but I would say that stealing intellectual property was sort of common at that time. Open source was not widely known, knowledge was scarce, communities were just ramping up and really anyone with lack of principles could pretty much steal anything and get away with it.
It happened to me a few times with online content I wrote. Essentially tutorials, articles, etc. around Open Source. Once my own company sent me a newsletter which contained one of my articles signed by another employee from a different place. It felt pretty weird.
Now I miss my 90s cheap MTB. I remember me as a teenager buying and setting up the bar ends. It felt so cool. For a kid it was like the ultimate performance improvement.
But well, right, they were so 90s. That wouldn't really fit at all with the current super posh MTBs out there.
Or maybe it is just not obvious that the background waves are a visualization. I just was reading this thread after going to the website and thought "I didn't see any visualization either". Then went back to the website and noticed the background.
This post and the Leetcode post both today in HN are in the totally different extremes at hiring. Try to get to dissect the person's psyche or try to find the best algorithm-maker? Totally different ways of hiring. Is the right formula in between?
This article seems to take it on Redis as it unproperly supports this use case, but Redis does not seem to be a right choice for a cheap vertically scalable k-v store. I didn't know SSSD but really you could have chosen amongst many other k-v stores or even memcache with disk support.
I guess the point is that someone chose Redis and soon realized that RAM was not going to be the cheapest store for 500Gb of data. But that is not Redis' fault.
I think you should throw away everything and start from scratch sailing on an already solid platform. Whether that is a plugin for Office 365, a paid app for Smartsheet or Airtable or any other *already successful* platform.
From your submission, I think what you are failing to understand is that you are asking people/companies to move their excel app/reporting to random-joe-bloggs' platform. It's not about the marketing. Even with the best marketing in the world, as a buyer I would ask myself "where this is going to be in one year?", and well...
Pick a solid platform. Hundreds of thousands of buyers are already there, the technology is already there, and you are not asking them to rebase their business. You only need to pipe the solution to the problem. If there is such problem then marketing will be way easier with a solid ground.
I found that reading and the project itself fascinating but not sure about how solid the project/analysis is.