cheapsteak

would PostToolUse be a better place to do it than pre-commit? (trigger on `"^(Edit|Write|MultiEdit)$"`)

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

I wonder if the start of the causal chain (or at least the intended audience) might be book publishers rather than people in Amazon

wrt checking the generated spec files in

does that not get a bit cluttered after a while? do you ever clean up old ones?

I'm predicting that Test-Driven Development may be having a comeback

English behaviour descriptions -> generated tests

Use both behaviour descriptions and feedback from test results to iterate on app development

Telling people to stop being losers is a not winning strategy; might feel good, wouldn't do good.

The open source and free platform be able to handle the patchwork of regulations that are now in place that differ between city to city

Curious what you've found to be reliable / would recommend?

You don't let your phones sit on their chargers while at 100% battery, do you?

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

How's the Pixel 6 holding up?

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?

Wrote this a while ago and continues to feel relevant as I'm reviewing pull requests from newer teammates and staring at force-pushed commit trying to figure out what changed between now and when I last reviewed it

(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 )

To save people a click

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

Curious whether source maps and breakpoints still work?

Do you have link to the developer productivity analytics? Or is it stuck in video form at the moment? Very curious

Better support for usage without Webpack/Babel/front-end build tools

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

How would you compare it with Create React App in terms of ease of use and build/dev speed for front end projects?

I've rarely seen a technology so eagerly embraced by both bleeding edge tech enthusiasts and also enterprise behemoths (granted, tech behemoths, but still)

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

I had the same misunderstanding, thanks for pointing that out

The amount of money required to adequately do what the world wants facebook to do might exceed the amount required to fund the 3rd party org

If the org is not as competent as people wish it to be, the blame is somewhat insulated

Heads up that the article's first link to your site is broken

The link is showing up as https://sourcesort.com/interview/browserless.io instead of https://browserless.io

https://npmcharts.com/compare/react,vue?interval=7&start=500

Vue adoption does seems to be tapering

(Naively looking at download counts)

Which one gives you access to the actual server?

I can corroborate that we were unable to activate a wechat account for my (western) friend. Not payments, just a normal chat account.

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)

People skills and conversation skills are also what I typically associate with "soft skills", but it doesn't seem to make sense when applied to (maybe half of) those books?

Could you clarify what you mean by "soft-skill"?

Or they never carry a balance on their card

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)

I made a chart of the download counts of the alternatives :D

https://npmcharts.com/compare/react-apollo,react-relay,urql,...

Convenience is one

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

Curious to know if you would count "ecosystem" as a point towards either? Afaik there isn't a standardized way of creating statically typed schemas for REST. A standard statically typed schema like GraphQL's allows a community to create and maintain tooling around it. A person would create"[some tool] for GraphQL" instead of "[some tool] for [specific api]"

Was the carbon not already sequestered when it was in the form of a tree?

Hot damn

https://npmcharts.com/compare/carbon-react,antd,@blueprintjs...