oxidant

7 ms·

31.
by oxidant 1y ago
The licenses for the Microsoft extensions explicity don't let you use them in non-MS editors. They seem to be cracking down now. To be fair, Copilot came before Cursor and the "agent mode" isn't a Cursor specific feature
32.
by oxidant 1y ago
Spreading arrays and objects is such a common performance hit. It works fine for small instances but falls over in large instances. Here's the JS CRM engine https://github.com/nuejs/nue/blob/master/p
33.
by oxidant 2y ago
WordPress, despite all of the current drama, is an example of an open source project with many different competitors and development seems to move just fine. Creating an artificial moat and misrepresenting capabilities, as outlined in the a
34.
by oxidant 2y ago
You're off by three orders of magnitude. 3k lines. You also don't know what the wrapper does.
35.
by oxidant 2y ago
I've had similar issues and the trick I've found is to jump to Google/SO to find examples or docs as soon as Claude stops making progress. If you got NullValueHandling, jumping to the library documentation would give you imme
36.
by oxidant 2y ago
Your post suggests authorization as a feature: > For each replay that we run, Roark checks if the agent follows key flows (e.g. verifying identity before sharing account details) I don't know if AI will be more susceptible or less s
37.
by oxidant 2y ago
Wonderful, thank you. I've already cut my typing in half with rg, I'm ready to commit to another 50%
38.
by oxidant 2y ago
`find` comes to mind. I consistently need to look up the syntax.
39.
by oxidant 2y ago
Cursor + Sonnet has been great for scaffolding tests. I'll stub out tests (just a name and `assert true`) and have it fill them in. It usually gets them wrong, but I can fix one and then have it update the rest to match. Not perfect, b
40.
by oxidant 2y ago
> The product why belongs in a linked issue that describes the bug or use case in full detail. That's nice until you switch git hosts or project management systems and the context is lost. Commits live forever, use them. At least a
41.
by oxidant 2y ago
I think you take the wagons apart and put them on a ~boat~ edit: was it a raft? In this context, "Float them down" doesn't refer to the wagons floating by their own bouancy, but rather their position atop the water.
42.
by oxidant 2y ago
This was an interesting read, thanks. One nit on mobile (Firefox and Chrome, Android), your code blocks overflow the background instead of scrolling.
43.
by oxidant 2y ago
I used Bench in the past and they partnered with Taxfyle up until ~November 2023 (date of the email I received stating the partnership was ending). The service was fine, interesting that their relationship ended just over a year ago.
44.
by oxidant 2y ago
Javascript doesn't, AFAIK. I work in Elixir, which doesn't. I'm for it if it's possible but it can still make it harder to follow.
45.
by oxidant 2y ago
Then you need to make those functions public, when the goal is to keep them private and unusable outside of the parent function. Sometimes it's easy to write multiple named functions, but I've found debugging functions can be more
46.
by oxidant 2y ago
Preserve log is still helpful for SPAs when you want to compare requests across full app loads.
47.
by oxidant 2y ago
Not OP, but I believe Clojure has a REPL that lets you run and edit code, persisting the changes from the REPL. Off the top of my head you would want a Dockerfile with the version of Clojure you're working in, a mounted volume for shar
48.
by oxidant 2y ago
This isn't a knock on you. The prompt (including additional context like specific examples/docs) has an incredible influence on the output. Do you know what your friend asked? "Query an API with SQL" sounds like you&#x27
49.
by oxidant 2y ago
I've had my share of non-stick pans, including higher quality ones. They all degrade to the point where I need to use oil. I switched to carbon steel as a daily driver two years ago and it is is trivialy non-stick with a little mainten
50.
by oxidant 2y ago
`git add .`, `git commit -m "wip: some note about what I was doing" Then checkout the new branch and do my work. When I come back, `git reset --soft HEAD^`, and continue
51.
by oxidant 2y ago
This article[0] about tech debt was posted the other day on HN. It seems to be a good guide for how to determine what type of tech debt to take on. Exactly what you're saying - does this tech debt Work™ or is it affecting future develo
52.
by oxidant 2y ago
"gay" in that sense is a pejorative against homosexual people. You could almost make it work with the original definition though. From Wikipedia - > Gay is a term that primarily refers to a homosexual person or the trait of bei
53.
by oxidant 2y ago
Not OP, but less than a dollar for a great espresso that I don't have to wait in line or walk further than 100 feet for is practically free, especially considering the opportunity cost of the time it would take me to walk to the cafe
54.
by oxidant 2y ago
Put the input inside the label and still use "for" on the label. No way to test right now but that's what I usually do.
55.
by oxidant 2y ago
I mostly like a comment with a succinct explanation and a longer commit message. Comments are less likely to be refactored and lose the immediate git blame, while the function might change over time. Ideally the future user would trace the
56.
by oxidant 2y ago
I'm not sure. There are 64 bases. Probably quantum proof.
57.
by oxidant 2y ago
This narrowing is probably not the best. I'm not sure why the TS docs suggest this approach. You should really check the type of the key to be safer, though it's still not perfect. if (typeof animal.swim === 'function&#x
58.
by oxidant 2y ago
Astronvim[0] is plug and play. Easy to add LSPs (Mason), easy to add syntax highlighting (TreeSitter), and easy to configure (Lua, no JSON). I can't stand VSCode due to personal preference [1], but I won't fault someone else using
59.
by oxidant 2y ago
My guess is that "now()" is the DB function that returns the current timestamp.
60.
by oxidant 2y ago
I had a netbook around this time and putting an SSD in it was a HUGE upgrade (similarly the upgrade from 2 to 4GB RAM). I still have it, and when I put an 32bit version of Debian on it a couple years ago, it was molasses. Somehow I used it

More ›