k3vinw

Jump navigation is a nice way to solve this. Something like FlashJump for Mac. Tab navigation too for close proximity jumping.

Should have called it Bunz!

I appreciate the perspective, but code reviews are subjective. The tooling and the language can be so good that it shifts to this kind of utopian state, where all bugs are caught and eliminated by guarantees in the language and tooling. Or they could be dismal to the point a human needs to check for mundane issues like bugs in the code.

> Nice idea but I don't understand why people write bash scripts more than a few lines long.

From a pragmatic perspective I agree. But I think you’re missing the point here. A lot of the most entertaining, and dare I say inspiring content, found on Hacker News is about exactly things like this. Things that seem silly, but are also very intentionally pushing the boundaries to the extreme/absurd.

Awesome! I’m the author and I created that project as a way to teach myself Bash at the time. I called it NanoBlogger because it was inspired by MicroBlogger, yet another Bash blog.

I still have fond memories of the open source community’s warm welcome and amazing contributions to the project.

like declarative vs imperative?

> We can stop reading LLM-generated code just like we don’t read assembly, or bytecode, or transpiled JavaScript; our high-level language source would now be another form of machine code

This is too weird for me. At least with programming languages I can consult the documentation and if the programming language isn’t behaving as documented, it’s obviously a defect and if you’re savvy enough you often have open channels that accept contributions. Can we say the same for Claude or other AI solutions?

Never occurred to me how much ms dos batch syntax must have been inspired by basic when I saw the comments (aka remarks) start with “rem”

Fair point. I’m still learning how best to take advantage of Ai. And to be honest, a statically typed language would have caught the issue with the wrong return type before the AI tool.

I’m not so sure. I had a recent experience where Kiro was convinced there was a defect in the testing library when I asked it to refactor some existing project code.

However this conclusion made no sense as we had similar scenarios across our project that worked flawlessly. After intervening I determined the root cause was a combination of an async issue with the production code and some incorrect mocking that was covering up the async issue.

It never occurred to the AI agent to do some simple cross examination before essentially throwing in the towel?

Gives me a whole new perspective to the phrase clean code.

Interesting. I replaced most of my gripes with power toys and WSL. That and a ridiculous amount of hardware. YMMV.

I’m most excited for the scheduler and memory footprint improvements. As bad as I hear Windows 11 is, I’ve rarely had issues with it. For the most part it just works and stays out of my way. My only gripes are the occasional forced updates and a rare hard crash that happened once in a span of a year of using it as my daily driver.

Well that and I have to be mindful of running too many resource starving processes at the same time including WSL. Otherwise performance will quickly degrade. But that’s not much different than my 2015 ASUS zenbook running Linux off of 8gb of ram. In comparison my work laptop runs on 32gb of ram with much more powerful cpu cores.

WSL is my favorite and most used feature of Windows 11. So I’ll be happy as long as they don’t screw that up.

If you think that's wild just wait until you find out what programming language their AI tool was written in.