655 karma · joined April 3, 2012
for lint issues that are autofixable, the tool use can trigger formatting on that file and fix it right away
for type issues (ts, pyright), you can return something like `{\"hookSpecificOutput\":{\"additionalContext\":$escaped},\"continue\":true}"` to let the edit complete but let Claude know that there are errors to fix next turn
does that not get a bit cluttered after a while? do you ever clean up old ones?
English behaviour descriptions -> generated tests
Use both behaviour descriptions and feedback from test results to iterate on app development
Yup guilty, I'm a bit neurotic about keeping things charged in case I need it later, didn't realize this affected battery life
TIL, thank you
I've had battery discharge problems with the Pixel 4 and 5 just a few months out of warranty. Hope that's been fixed in more recent generations?
(Title in submission is the title I originally intended and submitted to freeCodeCamp. Their editor changed it to what it is now ("How to" and "keep your code reviewers happy"). I then edited it back to what I originally submitted. The editor then overrode my edit and reverted it back )
Perpetual enterprise local license dropped from 15k EUR to 3.5k USD
Lowest tier pay-per-input cloud credits dropped from 20 EUR for 8k megapixels to 10 USD for 14k megapixels
It looks like it's reasonably easy to setup run-time JSX compilation by using a service worker with babel to intercept and transpile .jsx files. I imagine the performance tradeoffs would be similar to using Vue with string templates? Could be faster actually since you could memoize/cache in the service worker
Having API documentation that is guaranteed not to go out of date with your code. Having a shared standard for describing your endpoints in a machine-consumable way. Being able to automatically generate typescript types from any schema (correct me if I'm wrong but I don't think there's any tooling that would do the same for arbitrary REST APIs). Being able to get autocompletion when writing queries for free ^ Those were all things I didn't know I needed until I started using them, and like Typescript, it feels painful to go back to not having them
If the org is not as competent as people wish it to be, the blame is somewhat insulated
The link is showing up as https://sourcesort.com/interview/browserless.io instead of https://browserless.io
Vue adoption does seems to be tapering
(Naively looking at download counts)
Upon registration, Wechat asked him to get someone to confirm/sponsor his account. I tried to, and was told that my account couldn't verify other accounts because my account was suspicious.
I then solicited my spouse's help. She managed to go through the process of verifying his account, but when I told my friend to try logging in again, he said he was still marked as "suspicious" and wasn't able to log in
Edit: this was recent (last week)
Responsibly using CC isn't about "relying on future income to pay off present debt". If you have 5k in the bank, don't spend more than that, and pay it off at the end of the month (or if you're paranoid like I was right out of school, pay it off every week)
https://npmcharts.com/compare/react-apollo,react-relay,urql,...
I've used redbird to create a local dev proxy that can run be via npm scripts (which were already in the repo) so our engineering team didn't have to run the entire constellation of docker containers if they were only working on frontend code, and the only setup required was `npm install` which they already needed to do
I do wish you could just `npm install nginx` though