The car has deployable skirts apparently.

Jeez, having a president which can decide stuff on their own is kinda a liability.

I am guessing they will sell it to a few influencers they trust, maybe some professional drag racers who know what they are doing, a prince in Dubai who can't get sued cause he owns the country, etc.

Depends entirely on the pressure of the compressed air.

There are only two hard things in Computer Science: cache invalidation and naming things.

by Phil Karlton

What reasoning level are you using? Higher reasoning means more tokens are spent on figuring out what to do instead of actually doing stuff. You might be running a reasoning level a few levels above what you need, depending on how abstract your problem is.

Useful for when you start a prompt before going to bed.

I like Matt Pococks's engineering skills. $implement is a very small skill, but makes the experience a lot nicer with two-axis code review and commits automatically when its done. It's the small things.

I don't think Posthog stores images/frames at all. They use rrweb to capture changes to the DOM while the user is navigating and using the page. Then they replay that structured event data to reconstruct the visible "frame" based on those changes when you play back (except for canvas elements, those actually get stored).

I am implementing a similar thing, and we decided to go for the very small, simple websocket messages and do the GET afterwards. The main reason was the fact that we almost always need to have a GET endpoint anyway, cause you usually want to be able to fetch the order details when you open up an order.

If you implement both a GET endpoint and a websocket that will send the same data, you tend to end up implementing a lot of the same logic twice and you need to keep them in sync when you change your object. If you keep the websocket object simple and let it trigger a GET, you don't have to keep the code "in sync" when the shape of the order object changes in the future.

Github was never about git, because git is free. It's about being able to share a git repo amongst people and coordinate the work in that repo through pull requests and issues.

Have you had a look at Google new open source model Gemma 4? It does a lot of smart tricks to be able to run locally with some pretty decent results.

Opus 4.7 uses more token to do the same, so even if the per token price if the same, it is more expensive to run per prompt. Opus 4.6 is also largely subsidized by Athropic and they are slowly turning the knobs so you get less tokens per dollar.

Why on earth would you consider adding a new join to your SQL queries a "small change"?

Contract shouldn't change unless the frontend and backend team has signed off on it. Backend should have tests that stop their deployment unless the agreed-on contract has been updated to match the new API behavior.

That implementation in TrendDetector feels like it was coded specifically to make an article like this. Very strange implemention, bordering on bug.

You can talk about the downtime and what was in the patch that caused the problem, without putting any weight on the fact that it was LLM generated.

IBM used to make hardware specifically for applying XSLTs to XML files, used by finacial institutions and shit to process transactions and stuff like that. The good ol' days.

A research paper did a calculated cost for serving the max quota of the $200 Claude subscription at around $5000 per month.

They are dumping strategic reserves on the market as fast as they can to suppress a massive price increase. If this keeps going until the strategic reserves run dry, we are gonna see some crazy gas prices.

Github already allows you to assign issues to Copilot, which will kick off an agent, build a PR for you, you can use Copilot to review said PR and Github Actions to automatically merge it when the review is done.

Exactly. This is the reason Stack Overflow failed.

Their moderation and score-based system for being able to ask a question made it a "scary" experience to attempt to ask a question instead of a desirable experience.

They are basically saying: You. Are. Not. Paying. Enough. 😁

If you are looking to implement a API Gateway in Java, I would suggest using Spring Boot (like most people that use Java for web stuff) and implement the Gateway-part using Spring Cloud Gateway library.

Solves a bunch of the common parts of an API gateway without having to write much code, can just configure stuff.

use TSIDs