keybase proof:
[ my public key: https://keybase.io/randysyring; my proof: https://keybase.io/randysyring/sigs/o62LIbXLLJnsPvGLSV5A9hcVhOB9pnjZPnnDN3KuCIE ]
Submissions
Pi (Rust): High-performance AI coding agent CLI written in Rust
github.com
1 points·by rsyring··0 comments
aube: A New Dawn for Node Installs (from mise author)
aube.en.dev
6 points·by rsyring··1 comments
Agent sandboxing tools that mount projects R/W have gaping exploits
3 points·by rsyring··0 comments
Given AI, should I still consider becoming a computer programmer? Yes, and...
htmx.org
5 points·by rsyring··0 comments
Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt
margaretstorey.com
1 points·by rsyring··1 comments
How AI reflects the hidden truths of your software pipeline
thenewstack.io
1 points·by rsyring··0 comments
How Generative & Agentic AI Shift Concern from Technical Debt to Cognitive Debt
margaretstorey.com
2 points·by rsyring··0 comments
Ask HN: How do you run LLM Agents safely?
6 points·by rsyring··1 comments
I've Been at NPR for 25 Years. Here’s How We Lost America’s Trust. (2024)
thefp.com
5 points·by rsyring··7 comments
Testing is better than data structures and algorithms
nedbatchelder.com
188 points·by rsyring··176 comments
Taxonomy of Procrastination
dynomight.net
1 points·by rsyring··1 comments
Coding for the Future Agentic World
addyo.substack.com
3 points·by rsyring··1 comments
[untitled]
3 points·by rsyring··0 comments
Unpoly: A Batteries Included Htmx
unpoly.com
3 points·by rsyring··4 comments
Linux criticized for permitting numerous kernel patches from China's Huawei
nationalcybersecuritynews.today
14 points·by rsyring··6 comments
Celery (Distributed Task Queue for Python) 5.0 Released
docs.celeryproject.org
2 points·by rsyring··0 comments
Android 11 will only permit use of the built-in camera app
androidpolice.com
2 points·by rsyring··0 comments
Humane Email Validation (2009)
nedbatchelder.com
1 points·by rsyring··0 comments
Show HN: Easy Distributed Locking Using PostgreSQL Advisory Locks (Python)
github.com
3 points·by rsyring··0 comments
Congressional Budget Office releases study on minimum wage increase to $15 [pdf]
If you are really concerned about my being a bot, a quick look at my comment history, going back over a decade, should dispel that concern.
Edit: I once had someone apply for a job and their written communication was pretty caustic. After rejecting their application, I wrote and explained how unprofessional I found their interactions, encouraging them to step back and reconsider how their communication appears from the other side.
To my great surprise, they wrote back and said they had never had anyone give them such feedback and they agreed with my assessment of their interactions. They just had never seen it before. They thanked me for the feedback.
Such interactions are exceedingly rare. But I sometimes offer unsolicited advice on the off chance that said advice can make a difference.
I've read through all the sub-comments you've left here.
In short, you seem to have a grievance against linters that goes way past reasonable. You assert this example you give is "perfect" below. You also complain linters waste time and commits despite able evidence in the field they do the opposite.
You seem willing to add drama, grievance, and personal bias to what could have been a rather straightforward technical discussion. The sum of which is: linters sometimes make changes to code that I don't like.
I'd encourage you to reconsider what's really important when it comes to team development and try listening more to those around you. You seem overly focused on asserting your opinion instead of having a discussion.
These types of exchanges are usually very unproductive and stressful in a team environment. They are evidence, IMO, of a dev having the wrong priorities. I'd encourage you to step back and really consider how you view craftsmanship in a team dynamic and whether or not you are fighting the right battles.
FWIW, we started with a system that was essentially this. We eventually moved to pgbackrest and it wasn't any harder to setup. But the ROI on that investment is a lot higher because pgbackrest does a lot more for us than the home rolled solution.
Having done both, I'd recommend just starting with pgbackrest.
FWIW: I find passkeys to be a very simple and easy to use concept.
Simple: it's like a password that I don't have to type in
Easy to use: because I use 1Password and just have it installed on everything. On Android, it can be set as the default passkey provider so, even on mobile, I am using passkeys shared across devices.
Is this "less secure" because I'm sharing the keys through 1Password. I suppose, at some level. But before that, I was simply sharing passwords through 1Password in the exact same way. So, I don't think my security posture has changed any.
What has changed is the UX and IMO for the better. Now I don't have to generate/fill/copy-paste text strings for user names or passwords. 1Password knows what site I'm on and usually responds automatically when I'm in a passkey context. If I have more than one passkey available, because I have multiple accounts (for something like Google Workspace), it shows me options and I pick the one I want.
Honestly, it's mostly a "just works" system and I like it a lot better than passwords.
My experience with Hetzner VM pricing has turned me off of considering them for anything else. Maybe the experience in other world regions is not the same but this is what happened to us:
I started to use Hetzner's VM options in the Virginia, US datacenter. They had a great performance to cost ratio when I compared them to Linode/Akamai and Digital Ocean about a year ago. At that time, 4vcpu / 8GB server cost $24.99 per month.
Now, to get a VM like it, it's quoted $73.49 a month. Almost a 3x change.
I understand data center economics are changing due to LLM usage. But the Hetzner jump has not been mirrored by their competitors. I'm disappointed I made the switch from Linode. We still have some older VMs there and we'll likely continue to use them instead of Hetzner moving forward.
There are all kinds of nuances and complexities to the human condition, especially when it comes to something like depression.
I think the parent comment, with it's implied blame/shame of the deceased, is missing a lot.
As someone with depression, to others who might read this, know that there are those out there who care about what you are going through, have compassion, and don't need or want to blame you for what you are experiencing.
There is a place for responsibility and ownership of consequences. But the parent comment isn't the way to do it.
And, apparently, I now have to reactivate the service to one of the published plans if I want to use more than low-speed data. Previously, I still had high-speed bandwidth for $10 a month just not a lot of it.
They must have changed things recently. And, now that I'm thinking about it, I probably skimmed an email that said something about this a month or two ago but, since the charge was staying at $10 a month, didn't pay much attention to the details.
Because it's security related, the trust needed to consider using it is just higher.
Trust at two levels: who are you? What HFT firm do you run? How do we know you are actually this HFT leader? What are you doing in the HFT firm that lends credibility to build a project like this? I.e. if you lead the sales team, and have no software dev background, it doesn't increase trust in this project. If you built all the software for the HFT firm, that matters.
Since it's security related, we want there to be signals in the project that we can trust it to not start sending all our data to some bad actor state or org.
Then there is trust at the code level... Does it work? Will it continue to work?
You built it in two weeks because, for the last four years, you were busy with other things. If you get busy again, will the project lag for the next four years?
You don't owe us any of these answers. It's OSS, engage at whatever level you want. But, understand that when you publish your efforts to a place like HN, we are going to find and mention the things that make us uncomfortable.
That said, it's a good sign that people are pushing back. It is a cool project and fits a real need. So if you can increase the trust signals in the project, I think you will get more users... If you really want them. More users means more critique. :)
I hope you do make an effort to increase the trust signals and keep working on the project because I'd like to use it.
Interesting project but can't find anything useful about the author's background on GitHub.
Commit history shows the project is a couple weeks old and the commit velocity only seems possible with heavy LLM involvement. Not unexpected but worth noting.
The repo's CLAUDE.md is huge which conflicts with published best practices around agent instructions and makes me wonder how much experience the author has using LLMs.
All that said, I'd like to use something like this for my personal devices since my personal and work Tailscale networks still can't run at the same time. But there aren't enough trust signals for me for this project yet.
I don't claim to understand the business or politics between RedHat and Ubuntu.
I do know many projects with way less resources seem to be able to support Ubuntu and other popular distros just fine. Often through PPAs or their own apt repos (like Docker, PostgreSQL, or Incus).
If RedHat doesn't choose to, so be it. But IMO, they can't really compete with Docker when getting a recent release on the most popular distros is such a major cluster F.
My point is that it's not good enough to compete in this space.
Look at the distros that Docker supports. That kind of support is what users expect. When Podman just leaves it up to the distros to support, it's understandable. But, yes, it's not enough.