I can’t express the amount of visceral discomfort this brought me.
- 0 Posts
- 5 Comments
I’ve also started using it recently and I’m not sure if the way I’m doing it is particularly “right”.
I don’t have a lot of knowledge of practical coding practices because in school we literally had a new project every two weeks so I never learned things like you need unit tests or proper architectural design. It was mostly making sure whatever project there was that week ran and didn’t crash.
So now I’m working as a sysadmin doing the random junk a sysadmin gets pushed on them. What I’ve been doing is telling it my project plan, Claude will write up something that looks better, and I continue to have a back and forth about architecture and libraries, asking it if it thinks any particular idea is good or bad, until I get to a place I’m happy.
Then because I want to learn rust and implement it myself, I’m having Claude basically guide me through creating it like a teacher would, with it taking on a very Socratic tone (“now that we’ve done this, what do you think is the next step?” “We have a list of CSVs so what do you need to do to read their values?”). And I’ve been moving forward but by bit like this.
I don’t know if it’s a particularly good way, honestly, I’d love feedback from anyone who’s done something similar or whatever!
This implies that Pluto is a lovecraftian entity, and that brings me much joy
Barnyard gossip with a pinch of divination. Mad science is actual science but for the explicit purpose of being evil or off the walls whacky; given enough time or a proper application mad science can turn into normal science.




I feel strongly that “next” Thursday should be not the next instance of a Thursday but rather the first instance of a Thursday past the contained set of the current week (so the next row on a calendar). I.e. if it’s Tuesday, “next Thursday” isn’t the Thursday two days from now but the Thursday 9 days from now.