You unfortunately get what you pay for.
AWS is more expensive than God, but I'll be damned if you can't have a throat to choke in less than 10 minutes whenever something like this happens.
Readit NewsDumbStarbucks commented on Let's Encrypt has issued 3M certificates in one day infosec.exchange/@letsenc... · Posted by u/gslin
What attack vector could be here?
Companies losing money from processing certain renewal doing espionage.
DumbStarbucks commented on Show HN: Auger, know the ROI on SaaS products before you buy getauger.com... · Posted by u/baetylus
shouldn't this be... augur?
auger is a type of drill (or refers to Pierre Auger, as in Auger electrons or the Pierre Auger Observatory).
it should. that’s hilarious
DumbStarbucks commented on The Development of the C Language (1993) bell-labs.com/usr/dmr/www... · Posted by u/gus_leonel
People who know how to use C rarely if ever have problems with undefined behavior. I particularly have written a huge amount of C code and my bugs have never been related to undefined behavior. This is an idea that has been spread to make people even more afraid of using C/C++. While there is a possibility of finding these problems, in practice it is almost a non-issue.
> People who know how to use C rarely if ever have problems with undefined behavior.
I think the CVE database would disagree with that statement.
DumbStarbucks commented on The Concise TypeScript Book github.com/gibbok/typescr... · Posted by u/revskill
This is one of the reasons I find it hard to like TypeScript. Despite proclamations about reducing errors and maintainability, I have seen many developers largely motivated to introduce TypeScript for no reason other than the ability to hit "." and see what comes next. While that is a good goal, transmogrifying a type system (and a rather weak one at that) into an IntelliSense annotation mechanism seems excessive.
It's comments like this that make me feel better about my own decisions.
Because if that was the only benefit typescript had, it would be a win. I mean that was the whole point with JSDOC.
Anything that shortens the feedback loop from writing the code to seeing if it works is a win.
This is the equivalent of saying, "I see many people switching jobs for no reason other than to make more money". Like... That's the not the only reason but it's a big one.
Then you get into algebraic data types, and encoding logic constraints into the type system, and you can make entire classes of bugs impossible to write.
Type systems are about safety and productivity.
As someone not incredibly experienced with devops, I always wonder what is best with databases? Should they be provisioned in Pulumi or do I just manually create them in RDS?
Secrets Manager seems like a bit of a pain point as does IAM which I think I just about understand until I get lost! Giving everything access to ingress and egress also seems a bit overly complex/powerful.
Probably the time to get something working is dramatically shorter than it once was with ChatGPT to help.