2,094 karma · joined October 30, 2010
Currently bootstrapping:
https://ai.unturf.com
https://www.makepostsell.com
https://www.remarkbox.com
Tech Blog: https://russell.ballestrini.net
Mastodon: https://social.unturf.com/@russell
Contact Russell: https://russell.ballestrini.net/contact/The white colonizer did not get colonized by tribes in Africa.
The author needed to reverse engineer what could have been on the spec sheet...
Also code is like math which is public domain.
Step 2: write a slack style message as if you are discussing the solution with a teammate that you have authority over as a delegate to get shit done & to revise as needed.
Step 3: press enter, LLM does something you don't like, delete history, fix prompt in step 2 and ask again, rinse and repeat until you have working code.
Step 4: ask for the changes to be written as a bash file that cat EOF all the files that change into place, run the script.
Step 5: git diff & play test the changes using functional testing (use your mouse & keyboard test the code paths that changed...)
Step 6: continue prompting & deleting history as needed to refine.
Step 7: commit code to repos
a handful of dependencies (mostly Pyramid based at the moment) & whatever dependencies those have, pull it all down & serve it out of a tarball or zip file of a portable virtualenv.
So we really need ~40B or G model (two cards) or like a ~20B with some room for context window.
5090 has ??G - still unreleased
just made an battleship game today, look at research for for more
https://www.nytimes.com/2024/06/24/climate/ozone-satellites....
Future work is supporting api/secret keys to bring your own s3 bucket/digital ocean spaces, while keeping the database shared. otherwise it costs roughly $11/mo to host a copy of the platform ($6 for a virtual server and $5 for the digital ocean space)
As for taxes, this will be something that will need to be tackled at some point but so far I've been kicking the can down the road hoping I could find a partner to help figure that out in a clever way that is proper.
It's open source and public domain, uses stripe for holding card information
real 0m22.188s
user 0m14.702s
sys 0m0.449s
It's still a lot faster but less so, could you explain why I would want to run --jitless in production?