@antigermanist You're mentally challenged if you think simply applying for jobs via job boards and the like is going to get you anything meaningful (especially without tailoring your CV to specific jobs or companies).

It's a well-known fact that reaching out to recruiters and hiring managers or getting referred (by someone working at the company of your choice) are far more effective ways to get jobs.

And the fact that you're projecting like a whiney kid who can't see how low effort his job-seeking attempts are; speak volumes about you.

Congratulations @Root.

Apply for that position and hope to get it and fuck off from your current workplace.

People panic about AI because they are idiots who think it's some central entity (that is better than humans in very specific tasks) and that it's smarter than a toddler in everything.

Thankfully, it's not every non-technical person or everyone who haven't studied AI that acts like this, but there are loads of them.

@We3D I've seen far more people complain about vegans than vegans whining, and I know a bunch of vegans (one of which would get uppity about meat and such, but the rest are chill).

And I agree with the other two. Religious people are much worse than vegans.
I lost count of many times I've seen in person or on social media, religious people failing in even following own rules (like being kind), discrediting people's achievements in the name of their sky daddy, shoving their "God" in people's throat regardless of the topic.

@Kernel I guess due to them going a similar route to MS w.r.t. to collecting data from people's work and breaching privacy. I don't use any Adobe product but saw a post on FB about their announcement and people saying it would go against client project NDAs and such.

@PAKA And? Hardly anyone use Terraform without using HCL which is pretty much 99% of what you touch when doing Terraform stuff.
And you don't need to have Ansible set up or any YAML configs to use Terraform.

@Demolishun I don't know about that but that doesn't surprise me.

There's a lot more to DevOps then YAML files... Like Terraform, knowing your way round AWS/DO/GCP/Firebase/... infrastructure, configurations and such.

And I say this as someone who hasn't gone deep into it as an SWE and who worked people who work in DevOps.

@Demolishun Probably because of greed over morals and ethics. The C-suite might be engaging in tax fraud if they're like companies I've seen.

@lungdart It does work when done right.
The company I work at since 4y ago, is mostly Agile with either Scrum and Kanban, and the meeting rate has been fine for the most part but it gets out of hand when there scrums of scrums (basically additional meetings that groups different teams).

You asking "why 95% of devs are bad" when you didn't even interview that many and have this questionable interview process says a lot more about you/your company then the people who applied for the role.

You should review your interview process and for a role like this, the salary (assuming it's in the US) doesn't seem that unreasonable (especially for interviees who make close to that much to demand this to jump the ship).

Write 21 then state why (when asked).

If you _have_ to ship all or none of the endpoints then you either have an architectural problem (like @hjk101 said) or your deployment strategy is lacking in something (like a feature flag for the prod, UAT and dev environments for example).

Don't forget that your (future) team mates and future you will dislike you if you write code that isn't clear (variable names is part of that).

And naming conventions are there for a reason, to ensure consistency and enhance readability and structure.

If you went through a single code base where files, of the same type, have like e+ coding conventions and styles each; you'll have a harder time reading and understanding it.

@Lensflare Only in Germany, I've yet to see that being mandated anywhere else.

Dev, test/UAT and prod should totally be in separate VPCs (or even separate EKS/ECS clusters depending on the architecture of the solution or the enterprise).

As for the secrets, it depends on whether the team has DevOps staff (the better option IMO) or if the (Sec)DevOps staff are in a centralised team.

@ScriptCoded That sounds pretty early then! I mean, most people I know work 9am-5pm, and at my office, less than a handful of us come at 7:40-8:30am ish, while everyone else shows up at around 9am (with the odd goofballs that show up at 11, 12 or 1pm; which may be the same kind of people you're ranting about), but the company is spread across 3 continents and there's flexible hours.

Sad reality? Lol really? It's like you stole the post from that Progammer FB page that often posts stuff with baseless claims and nothing to back it up.

@ScriptCoded Did you get there at 10am?
And is everyone in your office working with only people in the same timezone?

@TeachMeCode If you think you have to learn every new framework that comes every year to stay relevant, you've not paid attention to what the market or certain industries demand and the State of JS/CSS/... surveys.
Since Deno and now Bun came out, the amount of jobs that were on Node.js barely changed in the areas I've seen, and that holds true for FE with React, Vue, Svelte (Angular and Ember being the notable ones that declined in various job sectors).

I don't know if you're new to the field or working in a startup that craves shiney new things without looking at the long term (like community adoption, ecosystem, job availabilities, etc) but that route will not help you (unless you truly want to be decent at dozens of frameworks and not experienced enough in a few).

It entirely depends on what you want to do when you get a job.

Do you want to do frontend dev? Then yes.

Otherwise, most likely not.

@tosensei Genuine question:
Do you genuinely think deploying the software to the client's premises is better (in all cases)?

@jestdotty Yeah, plus the company has that weird promotion cycle that follows quarters so I may need to wait until January to see if I get another salary increase and a more appropriate title 🙃.

@jestdotty Exactly. Especially when several other people had theirs updated after some promotions and either started at the same level I did or were at the same level I was when they joined the team.

It's weird how some higher-ups refer to me with the title I should have (Senior SWE) but on the system, the title is still the same as Grads SWEs.

@electrineer Damn! That sucks even more (especially if you get more responsibilities).

Lol!

I felt the same way when I was helping a junior with some CSS stuff and caught myself nearly writing SCSS code in the CSS file 🤣.

Hopefully one day SCSS will be redundant.

@ostream So you don't know the difference between shitting on a tool vs shitting on and insulting people who use said/another tool.

And as far as I'm concerned, React, Vue and Angular have their use; some projects are better written in one vs the others (especially depending on someone or their team's knowledge/experience in said tools and all the stuff that goes into picking the right tool for the job).

@ostream I don't know what you smoked or snorted but you seriously need to stop throwing your anger about tools you dislike alongside ad homs to strangers who didn't say anything aggregating to you.

I find it interesting that you even mentioned me in a comment that had nothing to do with what I said.
It's almost like you're trying to out-compete that Andrea Jung guy (or whatever the right spelling was) from a now-defunct social media dev group (which isn't a good look if you want any respect from others in the community).

And stop kidding yourself, you just stated opinions, not the truth. And it's hypocritical of you to talk about hating on tech when you did that yourself.