And now 50% time software engineers are writing infrastructure. Don’t know what is solution but cloud-native landscape has increased cognitive overload.
The point is obviously to pay less people to do more work. What I don't get is when developers themselves are in favor of it like I constantly see with this devops stuff. There's no way they have any kind of life outside of their job. There's no way they have a wife or children, otherwise I simply don't believe for a second they would be in favor of "developers own all the things yay!".
> What I don't get is when developers themselves are in favor of it
If you're comfortable with AWS and have built things as a software developer, it becomes clear very quickly. These things are intrinsically linked, and pretending they aren't is just kicking the can down the road until you have to solve some non-trivial problem.
There have been huge innovations and value-adds over the last 10+ years in cloud and serverless, yet everywhere I've worked that silos "DevOps" from devs has already baked in the culture that devs can just avoid knowing anything about AWS, that DevOps will be the gatekeepers, and that devs can just work within the "lowest common denominator" box of tooling that those gatekeepers think is appropriate. Meanwhile, infra costs are skyrocketing but it's all good because we're mostly "cloud agnostic."
I don't want to just be closing Jira tickets. I want to actually solve business problems well. And to do that, I don't want to be constrained to someone else's "box," throwing code over the wall to them, and hoping for the best.
I get paid pretty well fixing bugs and writing code, that stuff you call "just closing Jira tickets" and "throwing code over the wall". It's also enough to fry my brain and leave me exhausted. But it's obviously worth next to nothing in your view. So yeah, I don't care. I can't figure out if you're going to have to find people a lot smarter than me to do what you're looking for, or people a lot dumber than me.
> It's also enough to fry my brain and leave me exhausted. But it's obviously worth next to nothing in your view.
It's fine up until you have to solve hard problems. Once you need autoscaling or more of a datastore than you can get from vertically scaling a relational database, your brain will be REALLY fried trying to solve those things without touching anything at the Kubernetes or AWS layer.
Or it won't really be fried, because it won't really get solved. That's the pattern I've seen more often: just keep scaling up the CPU and RAM for individual containers / instances because devs can't solve it without DevOps, and DevOps can't solve it without devs. Cloud costs keep going up, and the problem's not really solved, but at least nobody had to understand more than they wanted to.
Not starting with a big name tech corp or a high-growth VC-funded company. Big brand on CV makes big difference when recruiters are doing initial screening. A CS/MBA degree from top university helps. Do whatever you can to work with a big tech brand early in career, otherwise later you will regret.
I’ve often wondered if I should be working for a high-growth VC funded company. Does it really make much difference when I still have to go through the same leetcode and interview when switching jobs? I still get left out if I fail the leetcode from the start. Not to mention, these high-growth companies are usually more demanding and long hours are expected. Is it worth it?
For senior roles CV/brand still weights. You need to be in initial shortlist then only leetcode and interview will be any help. I now work at a big brand high growth company and get pitched 2-3 new opportunities every week, although I have been in the current role less than 9 months. Previously I have to apply and rarely a recruiter approached me.
I will be happy to speak. My team specialise in identity and SSO implementations. In fact we also have our own identity product Axioms (https://axioms.io/).
Congratulations on launch and good luck in a very crowded market. We are building something similar with focus on SaaS companies (https://axioms.io/). I really like your multi-tenancy approach - interesting take could be very useful for B2B SaaS companies. We achieve similar outcome using organizations.
I never understood why media companies continue to reinvent the wheel. What’s commercial benefits if at all any? I guess, good for everyone’s CV. Build better media products, but no let’s build another publishing system.
That's the brilliant thing about the BBC. None, and it does not matter.
It's a publicly funded organization. They cannot make money by law (excluding BBC World).
Any organisation as large as the BBC design their online media around making users buy more products. UX, a/b testing, research, all about making you buy something even if you didn't want to buy it. If the website isn't trying to sell you something, it's trying to collect your information to sell or provide others opportunities to sell to you.
For the BBC you have none of that. That means everyone working at the BBC is working on providing the best user experience and content where you freely choose to visit because of the quality and content. Even if you don't like the content, critique the site, disagree or find faults with it, that doesn't change the fact the people creating it believe it's the best experience for a user. I've yet to work anywhere with all development being driven by UX and the UX member being one of the most respected people on the team. Their metric for success is visitors happiness, not profit from sales.
They are also on tighter budgets, a political target, and legally can't compete with other commercial organisations. That means they can't always do things as well as they can do as some company will complain they are stealing their customers. That's why IPlayer has stagnated as an example.
While their current lambda rendering wouldn't be something I'd personally do or recommend, it's also likely not CV building. The BBC is a billion pound, large, corporate organisation. Change is hard, deviating from the norm is hard, sometimes the process can make it hard to get things done. So ending up where they are now was probably a gradual process of trialing things over the years, capabilities of staff skills, and so on.
The BBC has many faults but the lack of "What's commercial benefit" makes for doing fantastic work. It was the only meaningful work I've done in my career so far.
I don't thing there is a mature, flexible CMS out there for publishers. AEM is more appropriate for marketing and old school web pages. Doesn't work for long lived content, journalism or publishing to diverse platforms and formats (AMP, native)
I am unable to suggest anything as I am out of touch these days. 5 years back every media CIO/CTO wanted to have Adobe AEM paired with Wordpress. Then they realised Adobe AEM is way too costly so decided to build authoring experience in-house but still using Wordpress and like for rendering and delivery. Recent trend use JAMStack/SSR for rendering. Don’t get me wrong it’s all great but doesn’t solve real problem media businesses face these days.
Hi HN,
We have created a cross-platform interactive JWT Debugger App with JWT token validation support using JWKS Endpoint and PEM/Secret Keys. Use the web version as a progressive web app or install desktop apps for Mac, Window, and Linux.
Love to hear your feedback. App itself is open-source and if you find any issues or like to add a feature just open a Github request (https://github.com/axioms-io/axioms-jwt-debugger). We will love to help.
The app is built on top Quasar Framework which is why it is cross-platform. It took about a day to pull this off. So current codebase is probably not completely clean yet but the app itself is fully functional.
