Recent submissions

Comment · 17 days ago
Great video, thank you for sharing
Comment · 4 months ago
Important formatting has been lost on this page in section 14.
Comment · 6 months ago
What alternative do you propose for downloading binaries off the internet, placing them in the "right spot" and doing post-install operations like updating PATH that dont have gotchas equivalent to running "untrusted" code like curl|sh?
Comment · 7 months ago
I've found LLMs decrease the friction in enabling more pedantic lints and tooling. It is a quantity problem because enabling all the aggressive warnings in the compiler makes a lot of work, and its a quality outcome because presumably addressing every warning from the compiler makes the code better
Comment · 8 months ago
I use Rust for command line applications.

I find that CLI is a great way to model problems. When I find myself doing something that has graduated beyond a comfortable amount of PowerShell, Rust is there for me.

I have a template I've been evolving so it's super easy to get started with something new; I just copy the template and slam Copilot with some rough ideas on what I want and it works out.

https://github.com/teamdman/teamy-rust-cli

Just today used it to replace a GitHub stats readme svg generator thing that someone else made that was no longer working properly.

https://github.com/TeamDman/teamy-github-readme-stats

Decomposes the problem very nicely into incrementally achievable steps

1. `fetch <username>` to get info from github into a cache location 2. `generate <username> <output.svg>` to load stats and write an svg 3. `serve` to run a webserver to accept GET requests containing the username to do the above

Means that my stuff always has `--help` and `--version` behaviours too

Comment · 8 months ago
I enjoyed Dave Cridland's comment more than the article. The article is dismissive of AI and other technologies in an unsubstantiated way.

New things are happening and it's exciting. "AI bad" statements without examples feel very head-in-sand.

Comment · 9 months ago
for 50,000 rows I'd much rather just use fzf/nucleo/tv against json files instead of dealing with database schemas. When it comes to dealing with embedding vectors rather than plaintext then it gets slightly more annoying but still feels like such an pain in the ass to go full database when really it could still be a bunch of flat open files.

More of a perspective from just trying to index crap on my own machine vs building a SaaS

Comment · 10 months ago
Comment · 10 months ago
Comment · 1 year ago
Neat! Have a repo?
Comment · 1 year ago
Python dependency management sucks ass. Installing pytorch with cuda enabled while dealing with issues from the pytorch index having a linux-only version of a package causing shit to fail is endlessly frustrating

A good ecosystem has lockfiles by default, python does not.

Comment · 1 year ago
Neat link, thank you for sharing.
Comment · 1 year ago
Neat! Must be very satisfying for this to be working now. I wonder if it's feasible to get it working on a multi threaded runtime
Comment · 1 year ago
Tried it out, very cool! Fun to see it chugging on a bunch of rows. Had a weird issue where it would recompute values endlessly when I used it in a table, but I had another table it worked with so not sure what that was about
Comment · 1 year ago
If incentives to stay outweighed leaving, people would stay.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton