sunshowers

3 ms·

1.
by sunshowers 12d ago
You understand that people get better at things over time?
2.
by sunshowers 12d ago
I came in on an H1B as an IC3 at Meta. Now, with the skills I gained during my career, I maintain core infrastructure that has a massive benefit to the industry and is critical to tech companies of all sizes (I learned last week that a majo
3.
by sunshowers 12d ago
Unlike offshoring, immigration increases supply and demand at the same time. Also: https://en.wikipedia.org/wiki/Lump_of_labour_fallacy
4.
by sunshowers 12d ago
all H1B posts turn into Klan rallies.
5.
by sunshowers 20d ago
My complaint is directed at the Rust Foundation, not the authors, to be clear. Yes, it's free labor, but the Foundation ought to have standards. I showed Bryan the post while in a meeting room with him, left the room, and a few minutes
6.
by sunshowers 28d ago
Well, one example is that patterns in code now can make you recall bugs you've seen in the past. I had this realization where I used an LLM to do a big refactor, and it fixed a bug along the way that I should have realized was much mor
7.
by sunshowers 1mo ago
Right, when used incompetently. When used competently they can carefully reason through every edge case and flag things no human would have picked up on. One example: in some old code I wrote I had assumed that the Rust Hash impl for a type
8.
by sunshowers 1mo ago
This whole week I've been dealing with incidental complexity created by shortcuts taken and edge cases not handled in code written in the before times, both in mine and in others'. I realized at some point yesterday that these kin
9.
by sunshowers 1mo ago
Are you aware of comparative advantage? What matters is opportunity cost, not raw output. (Also, unit labor cost is wage per hour divided by output per hour, so the number of hours worked is not really relevant. In other words, longer hours
10.
by sunshowers 1mo ago
This is only tangentially related, but libuv and mio's Windows implementations use the undocumented AFD readiness-based poll interface [1], since there isn't a documented readiness-based interface on Windows. The undocumented inte
11.
by sunshowers 1mo ago
> Can I get non-interger display scaling yet? I'm using 1.25 scale on Niri + DMS right now, on a dual 4k monitor (G9 57) at 240Hz. Probably the most demanding single monitor setup right now.
12.
by sunshowers 1mo ago
By security scanners, the moment a crate is uploaded to crates.io. The way forward here is dependency cooldowns enabled by default for ordinary users (and crates.io changed to show the old version until the new one is a day or two old). Ess
13.
by sunshowers 1mo ago
Every Rust crate is heavily scrutinized these days using LLMs (which also caught this issue). The days when no one looked at dependencies are gone.
14.
by sunshowers 1mo ago
BTW not sure how you feel about LLMs but merge conflicts are not really an issue with them any more.
15.
by sunshowers 1mo ago
Lots of people want to buy our stuff!
16.
by sunshowers 2mo ago
I mean, really no one is fully independent — we are all dependent on each other for the necessities of life. But in this context "independent" means "not a subsidiary of another company".
17.
by sunshowers 2mo ago
Right -- customers don't have to port their stuff to a new platform or arch or anything. It's just normal x86_64 Linux/Windows VMs, or Terraform if they're so inclined.
18.
by sunshowers 2mo ago
We are trying to build a sustainable long-term business! It's just that you need enormous amounts of money to get there when shipping this large a product. The idea behind VC funding generally is that you need large infusions of capita
19.
by sunshowers 2mo ago
It's not actually secret — it's open source! We talk openly about our architecture. Bryan has a good take on the incentive structures holding back commodity hardware vendors: https://m.youtube.com/shorts/O8GSW
20.
by sunshowers 2mo ago
That's wonderful! Good luck.
21.
by sunshowers 2mo ago
Indeed, and I happened to have been part of the creation story for one of them :) https://lobste.rs/s/ghdv6w/i_see_future_jj#c_nx6flj (not otherwise affiliated, though)
22.
by sunshowers 2mo ago
GitHub has a chance to get a generation of developers on to better coding practices. LLMs make it more feasible than ever to maintain high-quality patch series/stacked diffs — they can take care of all the mundane things like rebase co
23.
by sunshowers 2mo ago
I use `spr` which translates a local rebase + amend workflow into a GH-friendly new-commit + merge on the remote (which is then squashed). They are kind of equivalent from a 30k foot view but the dev experience when working with source cont
24.
by sunshowers 2mo ago
The seeming lack of engagement with prior art is so frustrating.
25.
by sunshowers 2mo ago
You don't have to expose change IDs in the UI other than as a secondary thing! The current integer index would work just fine.
26.
by sunshowers 2mo ago
That is nowhere close to the experience Gerrit and Phabricator have, where you can diff two arbitrary versions in history. Comments on previous versions also get lost along the way.
27.
by sunshowers 2mo ago
I apologize for being somewhat direct but what prior art did you engage with? Why are you making people create a branch for each change in a stack? Why do developers have to create new commits when iterating on the PR? Where is the proper s
28.
by sunshowers 3mo ago
Like all things in life, there is a balance :) I didn't remove the cattle vs pets analogy but I did replace "terminate" with "handle".
29.
by sunshowers 3mo ago
Look, you can either let people make a living and manage their own lives while contributing to society, or you can not let them make a living and ensure they're housed and fed. You can't be angry at A and also be angry at B.
30.
by sunshowers 3mo ago
Nextest does run tests in lexicographic (binary, test name) order by default, so first executions tend to be staggered. Unfortunately this is a known problem that is much larger than nextest, and it is why Windows introduced Dev Drive with

More ›