> Congrats, you can almost high-five yourself for reading tech bro hot takes on a beta iOS version like it’s a personality. Your setup screams “I refresh Y Combinator in a bathroom stall,” and your Safari browser agrees.
Yup, pretty accurate! Funny it also thinks my 15 Pro is an old iPhone since I’m using lower resolution.
In Scala it worked great using AnyVal wrappers around primitive types. It’s something I miss in typescript, where type aliases are more for documentation purposes on id types but don’t add much type safety. I think they trick is the type needs value semantics, which records should help with.
I’ve seen it happen, including other employees telling me I should make sure to zip up my code before I left (which I would never do). It’s only been at the earlier companies I worked for with many devs of questionable skill level. I’m not sure what’s behind the mentality, I assumed the act of writing decent code was challenging to them or it was perhaps something they were proud of, but maybe it’s also some misplaced sense of ownership. At one company I’ve experienced a dev asking back printouts of a design for a CRM at the end of a presentation, I assumed it was “borrowed” from their last job (thankfully we went a different direction). But regardless it definitely is a thing.
> I’ve rewritten quite a bit of the same logic at most places I’ve worked over the years.
Same here. I’ve learned to enjoy it, like perfecting a craft.
As others pointed out, some form of deterrent is just as important as vengeance for the victims. Just my opinion but it feels like tech is getting a bit too full of people who think they can do all sorts of terrible things because they are actually saving humanity in the distant future via AI or blockchain or whatever. My understanding is SBF fell into this line of thinking and I don’t think we should reward this kind of antisocial behavior with get out of jail free cards.
As someone that worked at Elastic for 4.5 years on the Elastic Cloud team and really loved it there for the majority of that time, I saddens me to admit it but this is spot on. Despite all their best efforts, everyone I've ever spoken to just wants to run the "ELK stack" and doesn't care about their confusing solutions strategy.
One thing about Elastic is that their roots are in on-prem / self-managed software and selling support to enterprise customers. This led to our cloud strategy being based around ECE (Elastic Cloud Enterprise), with the idea we would eventually fully unify this on-prem version of our Cloud product with our actual SaaS, and just run ECE "at scale". During that time we got stuck in the slower Elasticsearch "quarterly minor + monthly patch" release cycle (SaaS did have a shorter one but it was also troubled) and spent countless engineering effort troubleshooting enterprise customer's own infrastructure (imagine stuff like "ohhh, I see, you V-Motioned a server hosting ZooKeeper containers, and you're running on spinning disks" after 2 weeks+ of back and forth). We couldn't easily add table-stakes features to our SaaS because we needed it to run on-prem too, even though ECE is very limited in the types of supporting infrastructure we could add (basically just ZooKeeper and Elasticsearch). I think they are trying to move past this strategy and onto a SaaS-only K8s based approach but I fear too much time was squandered. I hope I'm proven wrong.
Thanks for the info - it just sounds like a completely bizarre approach. Like, why even make it the same (SaaS and OSS versions)? If you're going to do SaaS ELK then why not just do that and add whatever features you need to be better than DataDog or w/e? Make the SaaS ELK better than a version anyone could even imagine self managing.
It's especially weird to me because if I was a casual user then I wouldn't even know Elastic had anything to do with Elasticsearch. You certainly wouldn't know it from their webpage. I literally see this at the top:
"Accelerate results that matter, across any cloud. Easily deploy anywhere, and extend the value of Elastic with cloud-native features."
What does this even mean? How is the marketing department not 100% of these layoffs, lol?! why is a so-called SaaS company talking to me about deploying to any cloud and what even is "Elastic" and just what problem is it solving?
This is so bad it's hilarious.
You have to scroll for awhile to even see the word "Elasticsearch" and I don't see anything about ELK anywhere.
What pathetic execution. You were smart to leave that place!
Thanks for the input. Had similar experience with solution based on top of on-prem flavour (gravity - name came from pulling stuff from cloud back into traditional data centre) of k8s. Countless effort and resources have been wasted on troubleshooting customers' infrastructure rather than focusing on the real goal, get apps/APIs up and running quickly to generate value and realise goals for the business. The solution ultimately become a burden to both engineering and customers... Long sad / bad story.
Fortunately, decision makes heard the voice from the field and customers, eventually offloaded the container orchestration layer (and underlying infrastructure) to managed k8s service provider, the solution is delivered as helm charts to be installed on customers' own managed k8s (EKS, AKS, GKE and OpenShift - oh, the Red Hat OpenShi(f)t is just another rabbit hole...). But again, lack of knowledge and hands-on skill operating / running k8s (not yet a commodity although it is hyped to be...) makes the journey quite turbulent from a business PoV (technically it's easy, built the skills in house, hire the right talents).
I made a web game that's a mix of the board game Stratego and the classic rock/paper/scissor game. Its single player only, and the computer player's logic can use a lot of work but I haven't spent much time on it in a while. Basically you move your pieces to try to catch the other player's flag.
Elasticsearch has a general purpose authorization system as well, based on the concept of "application privileges": https://www.elastic.co/guide/en/elasticsearch/reference/curr.... It's an interesting concept I never really considered at previous jobs, to piggy-back the authorization system of some infrastructure already in your stack. On one hand I can see some team members finding it to be a bit of a "smell" since it's pretty far from the original intended use case for something like Kafka or ES, but on the other hand it can free you up from having to build this type of thing yourself from scratch or libraries.
I've heard it used often in the past (like 10 - 15 years ago) by some of my Ron Paul loving anti-Fed libertarian friends that were always talking about how we need to move back to the gold standard. I think Bitcoin certainly exposed the term to even more folks with different backgrounds outside of those who study or work in economists and finance.
Yup, pretty accurate! Funny it also thinks my 15 Pro is an old iPhone since I’m using lower resolution.