@rafaturk erm, just run dragonfly on the machine and check it the key exists with an 0(1) microsecond lookup?
lmao. A bloom filter is really not correct here, because the cost of just checking existence is identical or cheaper vs. bloom. if you had to compute something, bloom filter.
@onarchbtw the needs of a dev shop are vast and traditionally underestimated. there's a lot of bullshit to deal with; it makes sense to foist that complexity off onto anyone that can solve it for you at almost any price.
@robsnextmove@CasJam yeah it pisses me off when the LLM describes the shape of things. mfer it's not a pentagon it's a null check at the top of a ten line function
@mbriggs_dev@thepanta82 well, again, once you are a developer for a long time you start to take pride in the solutions and the saga rather than the code
are you a new developer by chance? I feel like 90% of my time was always looking thru shit code (my own sometimes) and so there's really nothing to go back to at a certain point. you get quite used to dealing with uncertainty in the professional world and much of that comes from other teams' code anyway
@staysaasy@jackinwarsaw maybe give them a better offer in the first place? not sure why you feel entitled to the work of a developer that is more highly valued elsewhere, given that you have zero personal connection, it's purely business (i.e. the reason you low balled them too)
harness means just... Something you structurally wrap around something else, typically to get consistent results or reduced complexity. So a test harness is something that gives the tests a repeatable pattern without blowing up the tests' code; an AI harness is just a bunch of tools you use to give it consistent results.
@TheBalkanHacker@fjzeit erm you can still read states on a stateless mcp, brotha.
you just need to read it in per request. I'm not sure you know what a stateless webserver is
@ImLunaHey those guys love to usgage ban but at any rate yeah you can't otp 300 times per day; it's unlikely that you need to though and npm will end up being the wrong distribution medium for new packages at that rate
right but otp a couple times a day for something presenting a decently sized security hole is meh. like if Claude can manufacture the otp that means your dev computer can manfacture the otp which would let people hijack your mom account if your dev machine goes south. I recently had a trojan on my dev box from npm (it didn't get anything, but just because it sucked) supply chain attacks so I am increasingly paranoid about endpoint devices having credentials these days
@dtcb@thdxr word the main time you should use any is just when you're dealing with external application layers, by the time the data hits your real business logic, you don't even need any of these indeterminates