xavdid

8 ms·

1.
by xavdid 19d ago
Right, your hobby is either 3D printing or maintaining a 3D printer, but not both
2.
by xavdid 21d ago
I traded a Prusa MK3S for a secondhand Bambu P1S and it was night and day. I believe the prusa could have gotten to a place where it printed well and consistently, but the P1S *just works*. It printed better out of the gate with 0 tinkeri
3.
by xavdid 26d ago
I would not personally sign onto (or put money) behind a DHH-run project because of his frankly abhorrent political views: - https://po-ru.com/2026/07/29/it-doesnt-matter-whether-matz-i... - https:/&#x2
4.
by xavdid 28d ago
That makes sense as a personal preference for him, but it's odd for that to still be the company/project stance. Like, surely he knows he's the minority for not wanting highlighting?
5.
by xavdid 28d ago
I love these release notes but I really wish they would add syntax highlighting to the Go blog. I'm always a little bit surprised/disappointed whenever I land on a go.dev link since I know the code will be just a little harder t
6.
by xavdid 29d ago
There's also different building pressures. Before, companies would want to build / power / maintain the smallest amount of data center hardware they could while still serving their needs. Overprovisioning just meant worse ope
7.
by xavdid 1mo ago
Even using staticcheck directly is slow. Just very surprising- do all other Go writers not use a 3rd party linter (and just use `go vet`)?
8.
by xavdid 1mo ago
> Linting is really good as well. Maybe we are using different tools (or we've set it up wrong) but I'm consistently surprised at how slow Go's linting is (using golangci-lint). Takes nearly 5 minutes on our codebase after
9.
by xavdid 1mo ago
Bummer. Airtable's a killer product and I've been using and evangelizing it for nearly 10 years at this point. Built whole side projects around it (and its API), plus organized a ton of personal information. I've made some cu
10.
by xavdid 1mo ago
Unfortunately it's a hard requirement. Apologies- you sound great on paper!
11.
by xavdid 1mo ago
Stripe | Hybrid (50% of time in Toronto office) | Senior Go developer We're looking for a senior-level Go developer who can design and ship idiomatic code our users love to work with. We can all write Go that compiles, but don't a
12.
by xavdid 3mo ago
> People will claim real harms but the connections are spotty at best. This is a wild claim because it's trivially provable. There's been tons of reporting around the effect they have on the immediate vicinity, and that'
13.
by xavdid 3mo ago
There's a sign next to a bridge that says "Weight Limit: 10 tons". Calvin asks how they know the limit and his dad says they build the bridge, then drive progressively heavier trucks across it until it falls down. Then they r
14.
by xavdid 4mo ago
If my cloud provider brings my startup down, it's my problem. If they bring all the startups down, that's their problem.
15.
by xavdid 4mo ago
Stripe publishes a very similar doc: https://support.stripe.com/questions/stripe-shares-or-stock-...
16.
by xavdid 8mo ago
Sure, where you draw the line will vary between projects. As long as its exact placement doesn't matter too much. For me personally, I tend to draw the line at write operations. So in your example, I'd want a dry run to verify the
17.
by xavdid 8mo ago
Yes, but it depends on the context. For little scripts, I'm not writing unit tests- running it is the test. But I want to be able to iterate without side effects, so it's important that the dry mode be as representative as possi
18.
by xavdid 8mo ago
I like this pattern a lot, but it's important that the code in the dry path is representative. I've been bitten a few too many times by dry code that just runs `print("would have updated ID: 123")`, but not actually runn
19.
How well can you predict the state of the world in 2041?(xavdid.fillout.com)
1 points by xavdid 8mo ago|1 comments
20.
by xavdid 8mo ago
We recently welcomed a new baby and have been discussing whether she'll ever learn to drive. I love bets with long time horizons, so we put together a survey so friends and family could pick a side. We kept thinking of fun questions to
21.
by xavdid 9mo ago
Not all the way down to 4KB, but https://512kb.club/ matches this vibe
22.
by xavdid 11mo ago
This was originated (or at least popularized) in an episode of Archer from season 1. It remains maybe my favorite 5 minutes of comedy ever out to screen. It's just so tight! https://youtube.com/watch?v=dNYMQpcqscA
23.
by xavdid 1y ago
Ah, these are great! f-strings are so powerful, but I can never remember the arcane little syntax. Definitely bookmarking this.
24.
by xavdid 1y ago
that's fascinating - I've definitely been saying "you've" and "tie". I assumed this was "picks"
25.
by xavdid 1y ago
If you're interested in some (light) science behind rivalry and/or the Michigan/OSU rivalry, I highly recommend the documentary "Rivals: Ohio State vs. Michigan". It's a fun look into why a rivalry drives bette
26.
by xavdid 1y ago
I don't remember if it links to it, but this pairs well with https://cryptopals.com/ , which are practical examples of many of these theories.
27.
by xavdid 1y ago
I found this to be an interesting new direction from Airtable, a product I've really enjoyed. I hope it doesn't muck up the core functionality too much.
28.
The AI-Native Airtable Has Arrived: A Letter from Our CEO(airtable.com)
2 points by xavdid 1y ago|1 comments
29.
by xavdid 1y ago
I mean, there are 3 equally valid ways to write an if statement: `test`, `[`, and `[[`. In the case of the latter two, there are a mess of single-letter flags to test things about a file or condition[0]. I'm not sure what makes them &q
30.
by xavdid 1y ago
My rule of thumb is that as soon as I write a conditional, it's time to upgrade bash to Python/Node/etc. I shouldn't have to search for the nuances of `if` statements every time I need to write them.

More ›