Featured
Following
5 minutes ago•••
The full text of the Bitcoin Whitepaper, already on 74 relays.
34 minutes ago•••
17 minutes ago•••
18905d0a...9b08 replied 6 minutes ago
4
23 minutes ago•••
7ed7d5c3...e200 replied 8 minutes ago
1
1 hour ago•••
#Realy is one of our favorite projects. Mleku's being a big help, including with explaining how some of the relay/backend stuff works and algorithm development.
fd208ee8...27c1 replied 1 hour ago
1
1 hour ago•••
Is primal.net severely throttled for people who aren't logged in?
1 hour ago•••
Good morning ✌️🧡
1 hour ago•••
GM 🥰
13 hours ago•••
Minor release of my uploader, with some essential upgrades, unit tests, and a complete redesign. Still just a minor release because I will be adding wikis and long-form article processing, as well as folder-based 30040 structures, and some other stuff, and that'll be the 0.2 release. Everything I'll need to produce test data for #Alexandria's Gutenberg edition.
Inching my way there. GN
5 hours ago•••
I have a couple of little side-projects, that I'm building to do test stuff, but I apparently can't resist the urge to turn them into full-fledged products, in their own right. 😂
fd208ee8...27c1 replied 1 hour ago
1
8 hours ago•••
Programming with Cline-support in VS Codium.
It's tedious to get it to build what I want (on the first try, and it would need to be the first try, to be faster than I am), although writing the request in Gherkin scenarios and adding lots of reference material helps. Then I page through the changes, slowly, rewriting stuff at each step, nudging it toward the desired architectural and programmatic goal.
I'm completely underwhelmed by its ability to bug-fix, but it does a great job on documentation and unit tests. Integration tests are not very good, but that's my specialty, so that's okay. I might just start having it generate Gherkin automation, based upon my hand-written scenarios (which are the core of the development, not the code, as they determine what the user will experience).
The minor release, with bouts of manual intervention, manual expansion, manual test data creation, and manual testing, took 14 hours. Which is slightly faster than completely manual. The end result is slightly better code than I can write, with fewer minor errors, and the test coverage is much higher.
I'm next going to try a process, to see if I can make it more-efficient and get it to produce higher-quality results:
* manually write scenarios,
* manually create test data and tests,
* ask it to change the code to pass the tests and fulfill the scenarios,
* manually test everything,
* have it refactor everything,
* run the tests, again,
* have it expand the tests to cover the new stuff,
* run the tests, again,
* manually test,
* have it correct/add documentation,
* run the tests, again,
* have it refactor, again,
* run the tests, again,
* manually test,
* push to master,
* faint in exhaustion.
fd208ee8...27c1 replied 7 hours ago
1
8 hours ago•••
Geniuses learn from everything and everyone Normies learn from their experiences Fools already have all the answers
LOAD OLDER THREADS