![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.team/api/v3/image_proxy?url=https%3A%2F%2Fprogramming.dev%2Fpictrs%2Fimage%2F8140dda6-9512-4297-ac17-d303638c90a6.png)
helix
helix
this is a conversation you usually have before the technical stuff. you’re making sure your ideal pay and their band is in sync.
being pushy early in the process is terrible advice.
even then, a position may not be for a certain level so they’re can be a fairly wide band of pay depending on how the interview goes.
i think most folks vastly overthink it. just ask for the money you want to make. either it’s in the ballpark or it’s not. all this “don’t say a number first” stuff is bullshit imo.
you definitely do want to know if your desired pay matches their range though. that’s very important.
that reads like it was written by ai.
if this 4 year old is proficient with emacs i’m going to kill myself
yaaaaarrr tis cheaper than eva matey
i said “email” but what i meant was “show me a complicated example”. i don’t disagree with anything you said.
so, where’s the email address regex? that’s where this lives or dies. there is no reason to use this for extremely simple happy-path regexes.
i’m having a tough time understanding who this is for. a beginner might think this is great, but they’re shooting themselves in the foot by adding an additional layer of abstraction rather than reading something to learn the basics.
hating on k8s is very in vogue currently. simpler systems like ECS exist and are really good too.
anybody bitching too hard about the tools today isn’t remembering 10 years ago correctly.