146 karma · joined September 24, 2017
I liked thought the article as I never deep dived in the differences
I appreciate that it’s minimal in functionality, but times changes and slop infiltrates every single platform, HN no exception
I use for the last many years NetNewsWire and have never had any problems reading the news I want to read.
Any credible studies to back this up? I find the contrary when I looked last time around, and it does not feel reversible when you disrupt the most important phase of your development (body wise).
But maybe I miss context here so happy to learn
What exactly are the safeguards for real? It’s literally irreversible damage when you mess up with hormones while on puberty.
I am conflicted myself, but I think I err on the side of caution and think that avoiding messing with your hormones should be no brainer.
My “stack” is self-control for blocking social and Gmail access.
And now I built QuiteCode to focus on deep coding and learning on a more mindful way.
Making this bold assumption as I don’t see yet a valid way to remove plastic from the modern supply chains. It’s embedded in every aspect of our lives so this will be huge if it holds true.
Thankfully at least LLMs could figure out things t help me setup SXT LTE 7
We are building Cherry, a tool designd to solve the "spam crisis" currently hitting open-source maintainers.
With the rise of LLMs and agents, the volume of low-quality, automated PRs is making it impossible to find the good contributions.
How we want Cherry to work: - Connects to your repo: We monitor incoming PRs. - Whitelists the good bots: Dependabot, Linear agent etc., get a pass. - Verifies the humans: We intercept new/unknown contributors and ask them to verify their intent and understanding of the code before the PR alerts the maintainers. - Silences the rest: Low-effort scripts and drive-by spam get filtered out.
We are trying to walk the line between stopping spam and remaining open to new developers. It’s a hard problem.
We’d love to hear your thoughts on how to solve this without discouraging legitimate junior developers. What kind of heuristics do you currently use manually that we could automate?
From SVG shadow bugs and weird audio glitching to WebKitGTK lacking WebRTC support on Linux, I wrote up a retrospective on the specific technical hurdles we faced. We are now looking at moving our heavy-duty windows to a native Rust implementation to bypass browser limitations entirely.
It was indeed long supported, but not a smooth experience. Have anyone tried the new profile management out?
Meaning no much pruning in the space, but utilizing Object storage for long term retention, and cache-hit staying in nvme?
Curious how it compares as companies like Linear and Cursor are using it but not sure if it would help in this case.
The streaming quality was also quite good with Zed. VSCode and JetBrains pairing features were a pain, as you needed to share a URL. The experience in general was not optimal. Not something you want to do multiple times a day.
With Zed, the only drawback was that the scope is always IDE (view mode also for whole screen). But from my experience, pairing is more than your IDE. It's terminal, debugging your unnecessarily complex AWS setup, fiddling with Grafana dashboards, etc.
My bet is that git hosting providers like GitHub etc. should start providing features to allow us for better signal/noise ratio
That means for moderate cases you do not even have to care about this. 99% of PostgreSQL instances out there are not big "scale".
As a sr. engineer is your responsibility to make a decision if you will build for "scale" from day zero or ignore this as you are mindful that this will not affect you until a certain point.