• 0 Posts
  • 442 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle
  • The better way rather than using a vague “make no mistakes” is to feed a template of stylistic preferences like “only var type this, only structures like this, we avoid certain structures or variable types” - as the context window is repeatedly compressed during work, “make no mistakes” probably gets contorted to, “mistakes! make!” then, “MISTAKES!!!”, like “NO, money down!”

    Bonus points if the style is stored in the repo as a template, so when the change is done you can just simply go, “ok, now read that style doc again and fix what you re-f’d up”. Sometimes it’ll even go re-read the style doc itself of its own volition.

    Using an LLM for dev is like directing an intern on 5 espressos to complete a coding task, but dumber.




  • The Senate folded, which forced a vote in the House because that bill changed in the Senate, which brought the House back into session, so she had to be finally sworn in.

    It is all, oddly, related.

    Extrapolating from there, the Senate Dems decided to gamble American citizens’ health insurance in exchange for some tabloid headline documents. Hoping for…mass sentiment against the Mango presumably? Strike while there is bipartisan support for something in the House. To then what, maybe oust Mango for Couchfucker? Sow distrust? Maybe they just pulled back because they realized the US was inches from doing a general strike? What better time.

    Meanwhile, citizens were ready for the long-haul. Effect real change. Get actual attention to being pissed off at this sham of a government. Thrown away for some documents that will be buried in a few disaster news cycles.















  • The problem comes in so many directions in real life though. Say your company has a very large database. Replicating it across regions means you’re paying for data ingress/egress and more than one region’s copy of that already sharded and/or duplicated database. It even applies when transferring data across AZs in a given region. Backing it up to S3 is expensive, backing it up to Glacier is cheaper, until you ever have to do a restore, and then you have to lay off half the staff to pay for it.

    Other issues can arise, possibly through the fault of yourself, sometimes at the fault of Amazon, if data traffic routing has a glitch and data is routing to the wrong place. The onus either way is on your company to show Amazon the receipts if you expect to get credits for the overage. At larger scale, this could be hundreds of thousands of dollars in overage. Easy to torpedo smaller companies with one mistake.

    They didn’t used to nickel and dime as hard as they do now, which doesn’t help, but outside of history, they set up AWS to be the biggest slippery slope of wallet-deletion, as almost every move you make costs money. Entire companies exist to manage your AWS costs (for more money, of course) and other companies’ products you may use that are hosted in your infra may accidentally delete your wallet if you don’t constantly monitor them.

    Using AWS cost-efficiently is only accomplished by ostensibly day-trading your cloud resources like a high frequency stock trader, capitalizing on unpopular/weird system types, and keeping your code as portable as possible.

    …but if one didn’t care about cost, one would probably get pretty good reliability out of them, sure.


  • Not to be that guy, but having had to repair ovens with these GE control boards on and off, what that display is saying (as the oven is on) is “PRE” for pre-heating.

    The updoot lover that created this image just photoshopped the E over the R. You can tell as the segments on both Es are exactly the same in brightness and intensity, which is highly improbable in simple digital electronics design used for these types of boards.