How do you use the model so quickly? Google AI Studio? Maybe I've missed how powerful that is.. I didn't see any easy way to pass it a whole code base!
I just downloaded this and its very polished for a new release. Works great!
I will trial it for a bit and if I like it will definitely subscribe. Have you considered adding some premium features to help justify the subscription?
Thanks! I thought about unlocking color filters for subscribers, but opted for making everything available for free, and just showing a popup asking for a license every now and then.
Just out of curiosity, and since this is vaguely related to the content, how has Fly.io adjusted to SOC 2 when it comes to infrastructure changes and deployment? I read a while ago about how you guys passed SOC 2 which was an enlightening read, but I'm curious what systems you have put in place to keep velocity going and how you manage change more generally across infrastructure?
My current experience is that once we started transition to SOC 2 compliance and brought in new processes everything crawled to a halt, we now have multiple layers of reviews and scheduling, and the bureaucratic process is followed at the cost of expediency and doing sensible things in a sensible way (i.e., everything must follow the process, no matter how trivial or significant.)
We have a "SOC2 review" regime, for a security-sensitive subset of our code.
The very most important thing to remember about SOC2 is that your auditors are attesting that you meet a standard that you yourself set. If you set a standard for yourself that every single change anywhere is going to be reviewed in triplicate, that's what auditors are going to check you on. So the key is to be extremely deliberate about the standard you're setting in your initial Type I. Every auditor is going to want to see some kind of change review, but the purpose of that change review is something you determine, not them. For us, the SOC2-auditable change review process is about ensuring that people merging PRs aren't 3 raccoons in a trenchcoat; it's not a vulnerability management process.
The trap people fall into is that SOC2 is often the point at which they start paying attention to security process as a whole, and they led SOC2 lead security process for them. No! Death! Be thinking about security from day 1, and have clarity about what subset of your security process you want SOC2 to measure and track.
First year with 2 kids in daycare, 6 months after COVID hit, we paid $38,000 for a years worth of care before the Government intervened and made some concessions. Now it's considerably more affordable here in Australia, I think now we would be paying about $15,000-$16,000 AUD
I have a child diagnosed with ASD level 2 (in Australia), he was born premature by a few weeks and immediately put on a course of antibiotics. I am curious about the connection here but am a total layman with the science.
I hope you don't mind the correction and apologies if you do, but it's actually "the lede was buried," where lede refers to structured writing in which the opening sentence of a paragraph summarises the most important parts of a narrative.
Here is another explanation that points to the telegraph being the origin, although they could only find one reference to it, while siting countless examples of it not being used outside of this very specific context.
There's 2 things on the horizon here for Kubernetes that give me hope. KCL, its own configuration language, and Timoni, which builds off CUE and corrects some of the shortcomings of Helm.
Though these days, OLM and the Quarkus operator SDK give you a completely viable alternative approach to Helm that enables you to express much more complex functionality and dependency relationships over the lifecycle of resources. An example would be doing a DB backup before upgrading to a new release etc. Obviously this power comes at a cost.
reply