Vanit

7 ms·

1.
by Vanit 24d ago
The one real caveat to this is that if your application has particularly heavy cold starts it can be hard to actually run your worktrees. I usually end up swapping to a regular checkout as each worktree is due for hands-on attention.
2.
by Vanit 3mo ago
Replaced by projects with nebulous ownership of copyright.
3.
by Vanit 4mo ago
Vault is an Obsidian thing. This is just an "agent" (read: LLM harness in a loop) with access to it, a system prompt and a few markdown files. Nothing meaningful has changed in the LLM primitives, nor will it :)
4.
by Vanit 8mo ago
The American discourse around these killings are actually insane. In any other developed country it wouldn't be possible to escalate these situations like this regardless of what you were doing.
5.
by Vanit 9mo ago
Ugh a terminal purist. Just as insufferable as the ones in person at work. Yeah have fun with your gigantic unorganized git diffs I guess.
6.
by Vanit 9mo ago
Like you said I think it's culture, particularly ones that are food oriented. It's gonna be hard to get buy-in if people think it's too weird.
7.
by Vanit 10mo ago
The tact aspect seems like a real possibility. In a world where users are likely to cut&paste responses it can't really be sprinkling in references like this.
8.
by Vanit 1y ago
Is this written by AI? Also pretty funny to compare to peanut butter & jelly, goes to show American self-centrism, and also the same bubble that's around AI tooling.
9.
by Vanit 1y ago
My favourite one was debugging a crash in an Electron app deployed to iOS. It turned out throwing an exception from a point event callback (deep in our app's code) was bubbling up into the device's kernel code.
10.
by Vanit 1y ago
I agree with the article, but that's not how the vibe coders see themselves. From their perspective they can't see the gap between programming and product, and in my experience are pretty hostile to feedback from real software eng
11.
by Vanit 1y ago
I realise your answer wasn't assertive, but if I heard this from someone actively defending AI it would be a copout. If the selling point is that you can ask these AIs anything then one can't retroactively go "oh but not that
12.
by Vanit 1y ago
Ah, somewhere you can find all those terrible interviewees in one place!
13.
by Vanit 2y ago
You may as well just use a singleton pattern if you're going to do this, and at least that's easier to maintain if your use cases change.
14.
by Vanit 2y ago
I read through half the docs and couldn't get a definitive answer on if nested custom components (ala React) we're even possible.
15.
by Vanit 2y ago
I'm throwing some shade here, but this reeks of backend engineers not caring about UX.
16.
by Vanit 2y ago
I'm keen to drop in a few PSX-era Final Fantasy backgrounds to see what it does!
17.
by Vanit 2y ago
I read some of your other replies and I can't quite get a read on your line of reasoning. The issue is we would give less attention to these things if it wasn't for the social credit the humans gave the vomit. So we engage in good
18.
by Vanit 2y ago
Bit of a different answer to the others; play Hypnospace Outlaw. It's a quirky game that captures the geocities aspect of what you're talking about.
19.
by Vanit 2y ago
I don't understand the use case, can someone enlighten me? I've always used them as a caching mechanism for derived / expensive data, and they work perfectly for that as-is. If you want to enumerate them I can't help but
20.
by Vanit 2y ago
Hearing about this is very reminiscent of current day React web dev as well.
21.
by Vanit 2y ago
It's not apparent if you're not already an expert in the domain you're querying, so users trust its answers, especially because it's delivered with an air of confidence (until you challenge it). Unfortunately that's
22.
by Vanit 2y ago
Null is the sole case in js that should always be == checked. Null or undefined should never be === unless you're explicitly encoding a semantic difference in your types.
23.
by Vanit 3y ago
The second I saw this was about OIDC support I knew what's up. This is a great way to flood your support bandwidth with "doesn't work with X" complaints.
24.
by Vanit 3y ago
I don't know who this is or why I should care about their opinion, but seems like a pretty evenhanded review. It does reinforce my apprehension due to bad UX because everything has to be on the touchscreen even when it doesn't mak
25.
by Vanit 3y ago
Ditto, for me 418 has always meant "check response body for the application error code".
26.
by Vanit 3y ago
Not at l surprised by this. I conducted a similar experiment when I was trying to get it to generate a body for a "Nigerian prince" email. It outright refused at first, but it was perfectly happy when I just told it that I, Prince
27.
by Vanit 3y ago
I used to work for a company that made an app for drafting evacuation signs, and we had a usecase for using a map as an underlay to show the surrounding buildings/terrain for the siteplan. I recall that quite a few map providers had a
28.
by Vanit 3y ago
What's the policy for attribution and saving copies of annotated maps for distribution?
29.
by Vanit 3y ago
I've been using a Razor Kishi with my phone to achieve this effect; it folds up nicely when not in use so effectively has the same travel footprint and I'll always need my phone anyway. I still miss that immediacy of instant paus
30.
by Vanit 3y ago
Ah, it's the users who are wrong! In all seriousness, as engineers we of course can't assume the happy path is common, and to ensure good UX more often than not we need to account for these cases.

More ›