Bitcoin developer meetup serving the Research Triangle NC ⚡[email protected] #nostr npub18z4n70qxqv40xef4je7fd0zya462gmkhvf2eax695f6sfgrk9yvq55lrpv
Raleigh/Durham/Chapel Hill, NC
Joined November 2021
- Tweets1.3K
- Following128
- Followers690
- Likes505
it doesn't include the secp256k curve which has known constants. but it does give confidence that these particular curves were not engineered with backdoors in place. we'll talk about it at the next bitdevs!
I spruced up the agenda site with summaries. Here's what we talked about at today's meeting: trianglebitdevs.org/socratic…
i am open to different schedules and locations, i just need data on what works for people who actually show up
no pics or videos, sorry
where are you located? is there a bitdevs nearby?
if you can't make it at our normally scheduled time, is there a better time? i ask for feedback about this all the time and just get crickets
Is it right to blame the agents? Obviously not if your prompt is trash.
But in the general case...I dunno. If these things are supposed to be superintelligent then they should have the agency to scrap a feature that's not working before it goes to prod.
Sometimes I push too hard for a feature that's just not right and have to scrap it.
That's ok too because A) I learn what not to do and B) it can provide pressure to refactor parts that are not well designed.
My agents do pretty much what I want them to. I like to think it's because I take a lot of care to provide excellent context, tools, discuss important decisions until there are no lingering doubts.
A lot of people talk about code slop but not many people talk about prompt slop.
