

Almost always use parameterized style tests, always have a name field, I don’t use full sentences tho, that seems like too much. Don’t believe I’ve ever seen a test like that either
These toy examples feel like strawmen to me
Almost always use parameterized style tests, always have a name field, I don’t use full sentences tho, that seems like too much. Don’t believe I’ve ever seen a test like that either
These toy examples feel like strawmen to me
For this kind of thing i usually go by popularity (active repo/popular repo), mostly to have the most other people in your boat. It doesn’t always work but generally if other users have to migrate at least you can ask them questions.
On the face of it i’d go with the csi driver version, only because we use alternative csi drivers ourselves, and haven’t seen any issues (ours are pretty aws vanella though).
We use storage classes (for our drivers) the “dynamic provisioning” section of https://juicefs.com/docs/csi/guide/pv, you’ll need to make one of those, then create a statefulset and mount the pv in there.
I do find statefulsets to be a bit of a not as well supported part of kubernetes, but generally they work well enough.
I guess i shouldn’t have answered, I do have experience with multiple storage-classes, but none of the classes you mention (so like i don’t really know anything about them). I envisioned you dealing with pod level storage issues and thought that’d be something most programs would have lots of difficulty dealing with, where as a more service oriented approach would expect remote failures (hence the recommendation).
All of the things you mentioned don’t seem like they have provisioners, so maybe you mean your individual nodes would have these associated remote fs’. At that point i don’t think kubelet cares, you just mount those on the machines and tell kubelet about it via host mount
Oh shit look there’s a CSI driver for juicefs https://juicefs.com/docs/csi/introduction/, they kinda start out recommending the host mount https://juicefs.com/docs/cloud/use_juicefs_in_kubernetes/.
We make some use of PV’s but people i find my team often tend to avoid them.
I probably should have shut my mouth from the start!
My gut says go multi cluster (or not) at that pointbut treat the remote as a service, have a local container be a proxy
Hate this title, how about:
“A novel by author Lena McDonald, accidentally leaves AI prompt in published version.”
assuming i learned, lol :D
Ugh, i thought this was a question, not a link. So i spent time googling for a good tutorial on floats (because I didn’t click the link)…
Now i hate myself, and this post.
ECC encryption seems semi preferred now a days i thought
Point of a corporation is to make money. Point of a “limited liability company” is to prevent losses on the company side from financially damaging the owners. LLC’s do not (and should not) protect owners from criminal acts.
This shit happens all the time. Look at car settlements, it starts at the top. I’m not against a whistle blower framework at all, but it seems like executives get all the pay and none of the culpability (see headline).
Executives, focus on executives.
I’m very lazy so I’d probably start by looking at filters on those sites, if i really wanted to tackle this with programming, i’d:
see if there’s an api, or rss feed for these sites, if so i’d pull that down with a cron job and do filtering locally with probably regex.
if not i’d scrape the html and pull out the relevant links with whatever the latest html parser is for the language i use (i.e. it used to be beautiful soup for python, but there’s i think a new better one).
but as i said i’m rather lazy, and haven’t been on the prowl for jobs for some time.
I was thinking of amazon.com and kind of happy about it… now i’m sad
In my experience only kinda, and by convention (up is on), and three-way switches break this (indicator becomes the light itself).
As a parent, this is a parenting/personal issue, fuck off and please spend my money doing useful things (like supporting health care, or housing) not attempting to protect my children.
Could be in vogue and also true
Interviews are a crapshoot, and feedback from them is usually valueless. Good luck to you in your future interviews
I hear this quite a bit, and think there’s actually a good deal of nuance to it. I’ve seen places that insisted on comments for everything, and it was silly, a significant number of comments had no value. This made people not read comments, as opposed to other places I’ve worked with very few comments - when you ran across a comment you gave it more weight (something here was complex, or not as simple as it seemed).
So imo, use comments which can communicate effectively, but use them sparingly for important parts that are complicated, for the rest attempt to communicate with the code itself.
Go has an idiom like so https://github.com/hashicorp/vault/blob/8da4386caceb3fdfaa90074bb29c77e8a99c7dad/api/kv_test.go#L27, when i mention name i’m referring to that string.
I get what your saying, we’ve all worked in terrible code bases, i’ve also worked in code bases where this kind of article was enforced. What you wound up with was something that was very wordy.