HN user

granra

258 karma

hn[at]codedbearder.com

Posts16
Comments71
View on HN

But now kids grow up with social media and fake news. I too grew up seeing stuff I shouldn't have online and I turned out fine but I see the online landscape today as much scarier place and as a recent father I'm scared of what it can do to my child and will need to police it.

I'm not entirely sure what an agentic workflow could mean today but I think so. I use a coding agent (crush), prompt it to brainstorm an implementation with me (or sometimes I know exactly how I want to implement it but ask it to challenge it), correct any wrong assumptions or request the implementation to look differently than suggested if I don't like it. Then finally when I'm positive I've cleared the most important assumptions I ask it to actually write and edit files and run tests and such (this just ends up being a "implement this").

With any model I've tried I've found it to be a huge pain to have it fix things where it made a wrong assumption without the code becoming a mess and burning a lot of tokens. I'm aware that not everyone works like this but I'm still very opinionated on what the end result should look like so I can still work on it without an LLM.

How are you using it? I have the lite plan and I've only ever maxed my weekly usage a few hours before reset. I will concede that I'm not a super heavy LLM user but it's been really good for me.

My workflow is usually:

- read file. I want to achieve X, how do? Do not implement anything.

- I would do a, b and c

- sketch a brief implementation of your suggestion

- <code> (not writing files yet)

- instead of your approach x, wouldn't it make sense to instead do z? What would that look like?

- <code>

- nice, implement this

- starts writing files, run tests, etc.

I remember that there were these talks called "Linux sucks" (IIRC) and the premise wasn't that we should start using Windows but more like "we can do better and improve it." Not every complaint needs to come with a solution or better alternative.

I made an MCP server that basically implements all the tools an agent harness would provide. The code is checked out on my server, the MCP server creates git worktrees on "activation" and it can read, modify files, run bash commands etc. I have this setup in typingmind so I can do everything from my phone :p The only problem is that typingmind needs to be in the foreground on my phone, otherwise it will kill the connection.

There was a time where I was often stuck for an hour with nothing but my phone and I kept copying file contents into chat for context so I made this and it works surprisingly well.

Generally I think you have a point when making landing pages or things of that sort. I however basically only use static site generators for blogging and I think markdown/asciidoc/whatever + metadata is nicer for writing content than directly in HTML.

I made nixtml and I take no offence :)

I had seen a few of those `__findFile` hackery articles lately and did actually consider doing that but I think having a nice way of adding HTML attributes would've been clunky :p

Edit: although looking at this article it seems to be supported.

I'm the author of nixtml. It's already doing IFD by using python to parse markdown content + metadata and superhtml to format the final HTML (a bit unnecessary, but I liked it while developing it).

I really wanted the templates to just be nix functions. It shouldn't be an issue to pass the context to an external program with `pkgs.runCommand` or something and then read the result (IFD like you mentioned).

Edit: I'm glad to hear you like it :)

What I saw as disturbing was the content of the post, failing to see that he wasn't directly voicing his own opinion on the matter.

I didn't like the use of the word "pro-abortion". I generally address them as pro-life even though I don't like that it indirectly indicates that the other side would be "anti-life" but I agree that it's not productive to get into a flame war on terminology.

Logically I see your point. But one side is fine with the other side having the opinion to not have an abortion under any circumstances while the other is fighting to take the right away from anyone to have an abortion. So I feel like one side has more reason to go for the anti-* card, although I don't think it's very productive.

Fair enough, I may not have picked the best example while skimming it quickly (he seems to have thousands of posts on his blog). I didn't like him using the word "pro-abortion" though (and not pro-choice) which to me seems to be used to villainize the other side.

Íslenskur? :D

IMO using string templating for creating structured data in a white-space sensitive configuration language always ends with pain and cursing beyond the most basic application manifests. I'm not saying Terraform or HCL is necessarily the solution either but it certainly wouldn't be Helm in my book.

It's a shame language like CUE or nickel didn't take off for this.

At a previous employer they were using helmfile. I don't remember what exactly I needed to do but I needed a value to be templated by helm _after_ helmfile had done its work (iirc) and ended up having to write along the lines of "{{ `{{` }} .Values.something {{ `}}` }}" but actually had more levels of nesting which required use of `printf` iirc and I don't remember how I actually solved it.

My point is though that using string templating for YAML creation is IMO always a bad idea and using helm for anything more complicated than the most basic application always makes me sad in the end. helmfile adds another templating layer and my limited exposure to it made me really dislike it.

edit: I remember now that this was for rendering config for vector, which itself has templating support with the famous `{{ .key }}` syntax. So not entirely helmfile's fault, but I still stick to my point as I needed to get through 3 levels of templating.

I'm not one for preaching about software :p

I thought I'd miss the infinite extendability of neovim with all my plugins and such but it didn't end up mattering to me and it was quite freeing actually to be just bound to what is supported in the core editor (as long as it's enough for you). I've been waiting for editorconfig support since before switching but it doesn't look like it will be merged into core.

Afaik there's plans to add plugin support using some custom lisp language which I'm excited about (I wrote all my neovim config in fennel).

But overall it's really fast and comes with essentials built-in like LSP and tree sitter support. There's some learning curve coming from vim in terms of key commands and such as helix is inspired by kakoune in that realm.

I don't think I did a really good job at convincing you but that's what came from my head quickly :D