Readit NewsOK turns out it was not a summary, just a preview paragraph that mixed headers and text from the original, leading to strange casing and reading. I'd suggest not to include headers there or distinguish them!
Example (had to search on kagi with site:minifeed.net):
You Can Either Steal Great Developers or Farm Them To grow software development teams, you can either steal excellent developers or you can develop them internally.
Yeah, the parsing is suboptimal right now. I'll work on that!
Can we add / suggests sites?
Sure, here: https://minifeed.net/suggest
Shameless plug, but hopefully relevant enough: my directory and search engine for personal blogs[1] indexes over 1000 RSS feeds, and naturally lots of them are about engineering and software development. Full-text search is implemented with Typesense, and there are also "related" recommendations for each post, example [2].
Location: Finland (EU Citizen)
Remote: Yes
Willing to relocate: Ireland only
Technologies: Python, Rust, Go, Ruby/Ruby on Rails, Clojure, Java, TypeScript/JavaScript; PostgreSQL, Docker, Kubernetes, AWS, GCP, Cloudflare Dev. Platform
Résumé/CV: https://rakhim.org/Rakhim_Davletkaliyev_CV.pdf
Email: hello at rakhim.org
Ex-startup founder, technical lead, currently staff software engineer at a superconducting quantum computers manufacturer.
freetonik commented on How AI conquered the US economy: A visual FAQ derekthompson.org/p/how-a... · Posted by u/rbanffy
Interesting that the profits of those bottom 490 companies of S&P 500 do not rise with the help of AI technology, which is supposedly sold to them at a reduced rate as AI vendors are bleeding money.
freetonik commented on We shouldn't have needed lockfiles tonsky.me/blog/lockfiles/... · Posted by u/tobr
In the world of Python-based end-user libraries the pinned (non-ranged) versions result in users being unable to use your library in an environment with other libraries. I’d love to lock my library to numpy 2.3.4, but if the developers of another library pin theirs to 2.3.5 then game over.
For server-side or other completely controlled environments the only good reason to have lock files is if they are actually hashed and thus allow to confirm security audits. Lock files without hashes do not guarantee security (depending on the package registry, of course, but at least in Python world (damn it) the maintainer can re-publish a package with an existing version but different content).
It's a cool idea, but maybe a improvement could be to select a random handful per day, and let them stay there for a while? Fewer surprises this way!