vinnymac

In case others are unaware, you just have to set https://yarnpkg.com/configuration/yarnrc#npmMinimalAgeGate to the value you want. It defaults to 1 day.

It’s on by default in yarn 4 too now, but pnpm was the first to market that default minimum gate.

https://github.com/yarnpkg/berry/pull/7135

I tried it but see a lot of false positives.

One funny thing I see it doing is deleting seemingly random comments lines, for example if a file has a comment that spans multiple lines but doesn’t use a multi line comment syntax. It just chooses one at random transforming the once useful comment into slop.

The problem is that we have an ever growing and large number of constraints, and not following even a single one means the result is sloppy.

I don’t see them fixing this any time soon, and thus human in the loop is a requirement to use these tools effectively. That is unless you love your slot machine dopamine rush enough to ignore quality gates and respect for your peers time.

It’s still early days, but I already have it in a useable state so I could share more such as early screencaps.

I plan on focusing primarily on these areas:

- mobile experience is first class, even on old/slow devices

- diff viewer is fast even on extremely large pull requests

- stacked pull request support

- user interface is modern, accessible, and theme-able with a light touch of whimsy

- search is accessible from anywhere

- opinionated keyboard shortcuts and commandk palette from day one

Many other longer term goals that I’m not mentioning here for now while the roadmap is forming.

I moved most of my projects off GitHub to Forgejo and will be using Tangled too for public repositories. I don’t think people realize that if you self host Forgejo, you get 99% of the functionality of GitHub with zero of the limitations. Especially if you have the hardware to spare for CI runners. And if self hosting isn’t your thing you can always just use Codeberg and Tangled directly.

I’m working on an open source Forgejo browser called Joui. It’s coming along nicely, and is so much snappier than GitHub in every single way.

I’m actively working on an alternative Frontend for Forgejo at the moment, completely self hostable, free, and open source.

Moving everything from GitHub to Forgejo and Tangled for now. These outages haven’t effected me for the past month because of this.

I left a similar comment elsewhere in this thread. I still remember when so many people hallucinated that we would suddenly have flying cars by 2002 at the latest. If we achieve several more major improvements on current technology, these thoughts are interesting to consider. But not before that occurs.

We need the pragmatic engineer more than ever.

I appreciate your insights in a sea of psychosis comments. I find it strange how many people think we have achieved the likes of Y2K flying cars 20 years ago, or the dream of having every car on the road be an electric fully self driving car by now (a promise made at least over a decade ago by several of these types).

The point I’m making is that we give the spotlight to people who are making absurd claims. We have not achieved the ability to remove the human from the loop and continually produce value-able outputs. Until we do, I don’t see how any of the claims made in this article are even close to anything more than simply gate-keeping slop.

Not to mention how trigger happy LLMs can be when it comes to being overly verbose and adding unnecessary bits even with explicit direction not to do so.

This made it impossible for me to read, and Safari Reader was unavailable, further cementing my press of the back button.

When doing this remove write permissions on the test file, it will do a much better job of staying the course over long periods. I've been doing this for over a year now.

Well said. I have to review PRs of non-software developers nowadays.

The “what is this trying to do?” has never been harder to answer than before. It creates scenarios where 99% is correct, but the most important area is subtly broken. I prefer it to be human, where 60-80% will be correct, and the problematic areas begin to smell more and more gradually.

In my experience LLMs, at times, may hide the truth from you in a haystack made of needles.

I carefully review far more than 14k LoC a week… I’m sure many here do. Certainly the language you write in will greatly bloat those numbers though, and Node in particular can be fairly boilerplate heavy.

I tried this for a week and gave up. Required far too much back and forth. Ate too many tokens, and required too much human in the loop.

For this reason I don’t think it’s actually a good name. It should be called planning-shit instead. Since that’s seemingly 80%+ of what I did while interacting with this tool. And when it came to getting things done, I didn’t need this at all, and the plans were just alright.

Been using Elixir with agents for over a year. Seemed like an obvious choice to me.

Node is great, but scaling Elixir threads is more so.

“NPM registry directory” sounds terribly confusing in my opinion, reads like a grammatical mishap

Especially because they mention unmaintained software (volta) in the same breadth as maintained software (fnm/mise)

Same, I am looking forward to starting my own company in the next year or two, and exploring the CTO role, especially after so many years as a Staff+ operating as an arm of CTOs and learning the ropes.

You wouldn't use it in an offline-first application. But you can use it an offline-first application, and it isn't even very difficult.

I have built electron apps for fun that utilize React Server Components entirely offline.

The official blog post disagrees.

> Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.

Most repositories try to create a poor man’s wiki inside of their README. It’s better this way until that problem is solved.

The other style I like is a single sentence with a single link to the actual wiki.

The last 18 years of tech companies I’ve worked for used AWS EC2, every single one.

Ah, a teacher telling a student to get in line, or else. A tale as told as time.

Since we defunded education in my area, my wife left teaching behind. She says the LLMs will let students ask whatever questions they want, but they make poor educators.

The difference is that the masses don’t buy these devices, only us nerds do. We are much more likely to disconnect a device as soon as they’re found being malicious. While the masses won’t even react after being told the well is poisoned. Large slow targets are more lucrative and long lasting.

Ever since I started using Wayland I’ve had this problem, even when I’m not using KVMs. I have to do a power reset of my monitor to get it to negotiate the correct resolution and refresh rate. Meanwhile Windows and macOS use the monitor without issue. I suspect the issue isn’t solely with the KVM.

The JetKVMs I have all came with a mini HDMI to HDMI cable, so this hasn’t been an issue for me.

Great work

Have you seen vert.sh? It does on-device conversion of audio, images, and documents and is open source too.

A governance model where “time-based decision thresholds” directly damaged veto power as time passes could be used to harness this sort of BDFL-only power in a consensus culture.

I used to run my own business when I was a child, and made a lot of money from it. Paid my way through school with my earnings. There was no sales or marketing, and all I did was product and engineering, and at no point was I politicking. So no, it's possible (albeit difficult) to not be part of the meat grinder, I have done it.