I'm not in charge of the Vault as part of the product but this is how we use it:

We use Vault as an on-premise service deployed in K8s. It is using PVs (persistent volumes) in order to have persistency between restart/shut downs etc. The vault is initialized by a custom made script which puts some default values for all the passwords which come from a config file, we refer to this process as a Day 0 operation. Afterwards the customers/system administrators are expected to update and change service passwords on their own which is known as Day 1 operation.

Just install a local mongodb and use that instead of the remote one.

Went all the way from QA to Development Team Lead in charge of a multi functional team (fe, be, devops, dba) in 5 years. What a long strange trip it's been

Not sure if you use Teams/Outlook but if you are I recommend turning on Focus mode to keep yourself distracted from other people and they'll also get an notice that you won't be available. Start by cutting off some noise from your day-to-day, most of the time people will eventually solve it without you, it's part of their job aswell after all.

The most you learn is by doing mistakes, you can't do mistakes in learning/side projects or atleast they are not so impactfull as there's no real user base. Not to mention that whenever you're dealing with real users you start seeing outside the happy flow path. I believe the statement that you learn while working is true for software programming. I just think you're looking at it the wrong way, it's not the number of frameworks or languages that you master that is important but the power to adapt and overcome all sort of challanges. The IT recruiters / managers are dilusional in their search for the candidate that has 10 years experience with React, but if that is all he knows he s a much less valuable team member to me than someone that also knows a bit of Backend, a bit of database querying, a bit of working in a Kubernetes env with CI/CD pipelines. You don't need to master all but you need to understand a bit about everything.

Custom build pipeline, custom versioning system. Component version is kept in two places, one of them gets updated one of them doesn't. DevOps team: "yeah we know it happens, its the developer jobs to make sure it was updated in both places".

Try teaching some tech illeterates basic concepts like for, if, while instructions. In our mind it is an easy job but its not something that everyone can do. I'm amazed by some of the devs in my company, they are supposed to be smart people but they can't fucking read a log message and google the error.. So yes, maybe in the next 10 years you'll get some purge but that's mostly aimed at the very bad developers. If you do your job good and know your shit there's very few reasons to fire you.

@hippolyte europe is weird given you have both 1st world countries and 3rd world countries, so would be a bit better if you specify the zone (west, east, north). I get 36k/year in eastern europe (romania) on a team lead position with 5 years of experience (not as a team lead but overall).

Define non web programming. You can pretty much do everything in any given language its just a matter of picking the right tool for the job. Sure you can pin nails with a screwdriver but everyone would rather use a hammer instead...

That being said you'll most likely settle for a language when you find your real interest in programming/area of expertise.

Taken from a rant seen here.

Just go out there and apply on jobs that you have atleast some of the "required" stuff they ask for. You'll see that in most cases they'll settle for way less as long as you seem experienced enough to pick up new skills while learning. There are just way too many stacks and languages and frameworks and so on that it is frankly impossible to be proeficient in all of them.

Do you work in sprints? You could implement a develop branch per sprint, all PRs go to the develop branch after dev review. When QA gets to finally test it you'll merge the develop branch into master after they mark it as passed.

And if QA is more than one sprint behind dev you could branch the next develop branch on the previous one... But it might create a mess when a dev needs to integrate a fix to an older develop branch...

But anyway it's a starting point..way better than everyone rebasing all day everyday 🤡

I'm a middle level with 3-4 yrs of experience which recently got promoted to TL just cause the old one left and I get spammed with TL offers that require 6+ years of exp as programmer and 3+ years as lead. The recruiters are bots

Just switch to JS and make everything browser based pogchamp

I don't have a problem with people asking dumb questions as long as they are relevant or they've searched it on google first and just want some clarification.

@spacehash check my updated comment, add some more info regarding serving the react app

Why not use the oficial react testing library:
https://reactjs.org/docs/...

Also I'm sure there are plenty of tutorials on how to serve a react app using node/express lol, but tldr you just take the react build and serve it as static files, I'm sure you'll easily find it on the web.

Also if you only need some easy to setup test POC you can use Cypress, it s a JS automation testing library, easy to setup and no hassle with Selenium (ugh).

will change the world

Tickets/stories should not be changed after they've been commited to the sprint (if you work agile/scrum) but instead a different ticket with a feature change should be raised instead. It's up to the developer/tl/scrum master to push back on changes that are added after the work has started otherwise what's the point of working with tickets, we could just code and use chats to request features added.

@Crost thanks for the advice but yeah, I've already notified both my manager and the product owner that we will most likely won't be able to deliver by the due date. In a spin off action however I was planning to have a 1:1 with the employee and tell him that I'm not quite satisfied with his commitment and he actually announced me that he's going to resign before we hit it off. I'm pretty sure that he was already working for a different project/company as I've seen him with the "in a call" status on Teams several times in the last week and I'm pretty sure they weren't for our company.

Typescript is evil, it takes me 30 minutes to write the code and then 2 hours to fix all the ts compilation errors :/

I agree the helm compiler and helm errors output are just ugh, figuring out whats wrong with the yamls feels impossible sometimes even. I had to upgrade grafana and prometheus-operator helm charts from v2 to v3, it took me like a whole week to bring our current setup up to date with the new charts.

Basically you don't shit where you eat, or rather you don't fuck where you eat. I've had two dev co-workers that hooked up, it was all fun and games until they broke up a couple of months later and it kinda made a mess, we were supposed to go into teambuilding right around that period, one of them didn't want to come anymore and there were kinda awkward situation in the office cause everyone knew about it but nobody talked about it. So yeah, it's not the most pleasant thing tbh. And I think it gets even worse if one of the party involved is part of management.

Tbh that's not that bad as long as they don't overdo it. As long as they only remove explicit porn images/gifs it will be alright. Plus i'm pretty damn bored of being follow spammed by porn blogs