kronin
Joined 12 years ago
Karma
230
Submissions
72
Member since
Jun 7
Recent submissions
Comment · 4 years ago
Comment · 4 years ago
> On other nitpick is that startups live and die with automation by their lean nature. They have fewer resources and must automate everything they can. It's built into startups mindset.
I am at a medium sized company. We acquired a startup. They did not "live and die with automation", instead they contracted out the production operations. A dozen customers, all on snowflake systems which were constantly tweaked directly in prod with no documentation or audit process.
My experience on the acquirer side is that startup engineers like to just build stuff and deploy it. Design? Testing? Documentation? Automation? None of that existed in this company in any fashion. And they are themselves grating against a modicum of process. Please explain what you want to do, why, and provide a high level design. You are going to replace the whole auth system, it's not something you just "figure out" as you go along... Sigh.
Comment · 4 years ago
Agreed. It's sad how many security engineers still push outdated processes, when there is significant research which indicates _why_ it actually _reduces_ security.
Comment · 5 years ago
> I think there's another word missing: "data sovereignty". Depending on your business, your customers might need to keep user PII within their country.
That's assuming a single multi-tenant saas footprint.
There is absolutely nothing preventing you from standing up a footprint in each compliance region and customers are assigned to the region that satisfies their requirements for data location.
You get the benefit of less footprints to manage, while still meeting the requirements necessary to serve your customers.
And if you have a customer that absolutely must have isolated infrastructure, stand one up for them and pass along the increased cost associated.
Comment · 5 years ago
The study states:
"We studied sera from adults (ages 18 to 55 years) who received two doses of the Moderna mRNA-1273 vaccine in phase 1 clinical trials (12). The majority of our study focused on 14 individuals who received the 250-μg dose, although we validated key conclusions with a smaller subset of eight trial participants who received the 100-μg dose. The sera were collected at 36 and 119 days after the first vaccine dose, corresponding to 7 and 90 days after the second dose."
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8369496/
Strange that the study would focus on individuals who received a 250-μg dose. The adult dose is 100-μg (https://reference.medscape.com/drug/mrna-1273-moderna-covid-...). Yes, the study states that key findings were validated with 8 participants who received the regular dosage, but still seems odd to me.
The comparison dataset is explained as: "The convalescent plasma samples were characterized in earlier studies (13–16) and grouped into an early time point of 15 to 60 days after symptom onset and a late time point of 100 to 150 days after symptom onset."
So the comparison was between vaccinated individuals, most of whom received a higher dose than is being given out, to infected individuals, and the time periods don't exactly line up. For the vaccinated dataset, the time periods were 7 and 90 days after the second dose. For the other dataset, the time periods were 15-60 days, and 100-150 days after symptom offset.
Deeper into the study, there is also this: "The escape maps of the 100-μg cohort resembled those of the 250-μg cohort and fell into the 456/484-targeting, core-targeting, or flat categories (fig. S6). Although the sample sizes are small, and a higher fraction of the 100-μg dose escape maps were flat than for the 250-μg cohort (4 of 8 versus 5 of 14, respectively), this suggests that 100- and 250-μg doses elicit antibody responses similar in the breadth of their RBD-binding specificity."
Comment · 5 years ago
Or NPM is having issues ;-)
https://status.npmjs.org/
Comment · 5 years ago
Wildfires burn up all the dead brush and make way for new growth, along with fertilizing the soil.
Comment · 5 years ago
Please share the package managers that handle this, thanks!
Comment · 5 years ago
Can't read whether this is sarcastic or tongue in cheek ;-)
Java 11 is the newest LTS release. The next LTS release will be Java 17. Many companies won't touch anything that isn't LTS. There are still a large number of companies staying on Java 8 :shrug:
Comment · 5 years ago
Have you ever found confirmation that they use OpenDistro internally? I've looked and have been unable to find such a statement.
Comment · 5 years ago
I put one of these [1] in my office 2 years ago and am very pleased. It wasn't cheap, but I use it daily. It always wipes clean, and there is no ghosting. It's right behind my back when I'm at my desk, so I can also turn my webcam on it when in meetings.
I've tried to use electronic whiteboard alternatives and it's just not as fluid when trying to get ideas out. Maybe an iPad Pro with a Pencil, but I haven't sprung for one of those yet...
[1] https://www.pegasusav.us/pegasus-magnetic-glass-marker-board...
Comment · 6 years ago
You don't have to hand-write your openapi.yaml. we are using quarkus, and by annotating the endpoints you get a generated openapi.yaml.
We then use this in a typescript generator to generate client code.
Comment · 6 years ago
Is it this one?
https://vimeo.com/267445424
Comment · 6 years ago
When I interview (and yes, there's whiteboard time), I tell the candidate up front and very clearly, "I will be your Google. I know we don't work in a vacuum"
Comment · 6 years ago
2 of starboard's capabilities are to run kube-bench and kube-hunter, and yeah, aqua has been doing some great work for the community in this space.
Instead, build your artifact and publish it to an artifact repository, just like we used to.
_then_ wrap that artifact in a Docker image.
Vulnerability found in the docker image? No problem. Build a new image with the same artifact.