@etscrivner In my https://t.co/dHzsiCEtVQ I tell it to plan first, critique the plan and revise with me, implement via TDD, then revise implementation with me / run e2e. Oh and also cleanup any old bullshit it wrote.
Tedious but the formal process helps a lot.
11/ Thankfully, we've found a solution using the principles of M/M/C queue theory. We can scale our workload based on estimated block execution time using a mathematical formula involving block arrival rate (ฮป), steps per second (ยต), and number of workers (s).
BOUNTY ALERT: We're looking for web3 enthusiasts to solve our crypto bounty!
First 50 finishers will get $250 in ETH, first 500 finishers will earn an exclusive NFT, and an opportunity to score a convo with a recruiter at Coinbase. ๐
Check it out ๐
https://t.co/bDewzzEwE1
@etscrivner Thatโs awesome. I built an intel 8080 emulator a while back which was fun. But testing the whole system / making sure every instruction was correct was tedious and painful
gm! Slide is building products that enable web3 applications (dApps) to serve effortless experiences to everyday users.
Weโre excited to announce our product and $12M fundraise from web3โs best investors.