Activity Log
hackers.town: 2024-07-31 Wed 09:20
I find coding assistants genuinely helpful almost half the time, assuming they correctly process the context of language and active code base. It’s helpful like an old school code generation wizard masquerading as autocomplete, but — even when wrong — it can help start or move the thinking process.
The other more than half the time, they get in the way because they’re interrupting the flow I have in mind. All I need is good language tooling and LSP that can help with the expression I’m typing right now.
This toot brought to you by “disabling the coding assistant before I throw something at the computer.”
hackers.town: 2024-07-31 Wed 09:28
Bookmarking this for the inevitable next cycle in my PKM hyperfocus rotation.
Blogging with Denote and Hugo | Jiewawa’s blog
hackers.town: 2024-07-31 Wed 11:36
Doing that exasperated thing where I build the regular expression in Perl and then translate to the lesser language I’m supposed to be using.
I mean don’t get me wrong, Go is fantastic at its thing.
It produces the wrong answer so quick.
hackers.town: 2024-07-31 Wed 12:47
big lightning in close proximity
making sure laptop has freshest copy of current code
hackers.town: 2024-07-31 Wed 13:04
I spent a few seconds with one foot outside
before it got scary
https://www.tiktok.com/t/ZTNXBYG7F/
hackers.town: 2024-07-31 Wed 17:31
Part of learning the language is figuring out the impact of each little change or idea. Overall I’m pretty pleased with myself. Maybe someday I’ll be better able to stomach text processing in Go, because I know that’s still the slowest part of my code.
I don’t need to care about 0.15s vs 0.45s with this. Heck I don’t need to care about 1.3a. But it’s a narrow, well-defined task. I can make small changes and promptly see the difference.
I already notice in blog posts, sample code, and my own efforts: because the compiler catches type errors and executables are fast, it’s real easy to write sloppy code in Go.
Just because it’s syntactically correct doesn’t mean it’s a good idea.
So I make the silly mistakes and the naive code choices in this small project so I can more easily recognize them in big legacy projects.
hackers.town: 2024-07-31 Wed 23:48
Officially giving up on swapping backspace with space on the Model 100. Muscle memory apparently is one of the categories of retention that does not reset periodically.
More accurately, swapping two keys is not enough of a reset. Different keyboard or swap out a whole bunch and I’m cool. Still got Dvorak muscle memory even though I use it maybe twice a year.
But everything the same except these couple bits? I’m screwed. Bouncing between PC and macOS layout is similar.