Conversation

Notices

1. Embed this notice
   Rusty Crab (rustycrab@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 00:07:16 JST Rusty Crab
   I think part of the "slop grenade" mentality is just seeing all of the code written that you didn't personally write in one commit. You probably don't realize how many files you were changing doing it manually on the same project over several checkpoints.
   
   I still hand review all of the new code like a boomer and I can't particularly see anything that didn't need to be changed for most tasks (sans certain cases where it could have reused a class). It's just shocking seeing all of it so quickly.
   • mischievoustomato repeated this.
   • Embed this notice
     binkle (binkle@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 00:49:29 JST binkle

     in reply to
     @RustyCrab bad code is "any code I didn't write"
     
     but that doesn't mean they're necessarily wrong. I think programmers take kinesthetic learning for granted and the lack of it is what they're reacting to when they say things like this. It's always easier to understand code you've typed out yourself, because you physically felt it and reinforced it during the process of typing it out
   • Embed this notice
     mischievoustomato@0.5dollah.click's status on Wednesday, 07-Oct-2026 01:25:39 JST mischievoustomato

     in reply to

     @RustyCrab you're absolutely right!

   • Embed this notice
     mischievoustomato@0.5dollah.click's status on Wednesday, 07-Oct-2026 01:31:32 JST mischievoustomato

     in reply to

     • binkle

     @RustyCrab @binkle i actually used a flow chart to debug a problem i had with a program im writing, and it lead to me fixing the issue. Its so nice.

   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 01:31:33 JST Rusty Crab

     in reply to

     • binkle
     @binkle when I get a chance to breathe I want to explore ways that make code dead simple to read that would be retardedly infeasible to write as a human. Stuff like making every big function have a unique return type so there is no possible confusion for what plugs into what. Exploration of functional programming where you can pack away implementations and hammer them with retard strength in isolated testing
     
     So much of our old ways are centered around saving manual labor and typing and it's going to be mentally difficult to break away from that
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 01:31:33 JST Rusty Crab

     in reply to

     • binkle
     @binkle i'd also really like to explore state charts as direct programming. There was a tool called Yakindu that I think is still around but costs big enterprise money to use. It was one of the most useful tools for network programming I've ever seen and the concept seems completely unexplored by most other people. The only thing really stopping it was it was a pain in the ass for other people to use your projects but that was purely because the tool was badly written (Eclipse :niggavoid: )
   • Embed this notice
     mischievoustomato@0.5dollah.click's status on Wednesday, 07-Oct-2026 11:04:04 JST mischievoustomato

     in reply to

     • binkle

     @binkle @RustyCrab I havent read the whole discussion yet but I get the itch to make functions out of stuff when I recognize I do things repeatedly.

   • Embed this notice
     binkle (binkle@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 11:04:05 JST binkle

     in reply to
     @RustyCrab that itch to try to make everything a tiny piecemeal function may allow more tests to be written but falls prey to a form of premature abstraction which carries with it a lot of extra baggage that's always left unaccounted for by the people who evangelize it. I mark it as another sort of ideological commitment, akin to hardcore OOP or Rust's safety culture.
     
     Not that I'm saying YOU'RE being ideological of course, I don't think you are, but this Logan guy really set me off :kirbyangery:
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 11:04:06 JST Rusty Crab

     in reply to

     • binkle
     @binkle well now I'm curious
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 11:04:07 JST Rusty Crab

     in reply to

     • binkle
     @binkle
     >ways that make code dead simple to read that would be retardedly infeasible to write as a human
     
     This video popped up on my feed and it kind of answers that question. Specifically the part about NormalizedVector. You could do a lot to bake contracts and invariants into objects in a way that isn't feasible by hand
     
     https://m.youtube.com/watch?v=2OMRWPOSw9s
   • Embed this notice
     binkle (binkle@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 11:04:07 JST binkle

     in reply to
     @RustyCrab this video was so difficult for me to get through I wound up skipping most of it to get to the part you mentioned and while that one part was good almost the moment it was over he stepped on another rake and I had to turn it off :melt:
   • Embed this notice
     mischievoustomato@0.5dollah.click's status on Wednesday, 07-Oct-2026 20:43:22 JST mischievoustomato

     in reply to

     • binkle

     @binkle @RustyCrab right, yeah. I try to do it if it's meaningful enough. Like there's a little thing I do (just 2 lines) that repeats in 2 arms of a match, but I don't turn that into a function cuz that's tarded. But in some other places I managed to slim things due to turning other things into functions, and I think I keep stuff tidy enough that I don't lose understanding of my stuff...

   • Embed this notice
     binkle (binkle@clubcyberia.co)'s status on Wednesday, 07-Oct-2026 20:43:23 JST binkle

     in reply to

     • mischievoustomato
     @mischievoustomato @RustyCrab that's normal and I wouldn't advise against it - it's only when you make it an ideological commitment and decide to start breaking things out before the shape of the program is really visible that it becomes a problem