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.

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.

if this 4 year old is proficient with emacs i’m going to kill myself

“programming” is so broad though. surely there’s room to have it be both work and a hobby ?

i mean, it is for me and lots of folks i know.

there are tons of developers and technical folks that still find it fun and enjoyable to work on personal projects.

i mean, how else do you build new skills or gain familiarity without stuff you don’t use at work?

you can show activity without showing the details of the activity. which is at least demonstrating you’re active.

i do terrible at the live challenge, and great at the take home stuff. i don’t k ow what it is about the former, but i just cannot think while someone is looking over my shoulder.

functional dev environments have been the hardest part of learning cl for me. i don’t really want to use emacs, but it’s the wild west for other editors.

setting up emacs wasnt hard per se, but emacs is just so much. i spent more time troubleshooting how to use emacs and fix issues with it than learning the language, which just makes it all a little lame.

fair!

i said “email” but what i meant was “show me a complicated example”. i don’t disagree with anything you said.

respectfully disagree—this is very much a regex dsl. folks still need to conceptually understand regex to use this, which begs the question about who this is for.

the best use case i can think of is large and complicated expressions, but i’d need to see more of that to have a definitive opinion.

this is really the problem here. it’s very much lipstick-on-a-pig and doesn’t actually reduce complexity.

i mean, you can learn the basics of matching in 30 minutes or less. that core knowledge will be broadly applicable across any tool that uses regex. things get much easier once to have a handle on the basics.

…or you can learn this regex dsl and still have to learn regex. the difference is you’re learning a non-portable regex syntax.

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.