Palantir’s second-quarter net income was more than the company generated in total revenue the year before.

Revenue in the three months ended June 30 increased 93% year over year, totaling $1.94 billion

we’ve raised $200M at an $11 billion valuation

But what if you want to update this user instance? For example on your website you have a form where the user can change their name, username, or avatar. When the form is submitted this gets stored on the server, but the site still shows the old user information, for example it still shows the old avatar of the user in the top menu. The user variable isn’t writable, so how do you overwrite this?

One pattern that I love to use in my SvelteKit projects is returning writable stores from the layout’s load function. This makes it possible to fetch data from the server (for example the user object for the logged in user), and then you make this object available as a writable reactive store throughout the whole application. So when the user updates their username or avatar, you do the PUT request to the server and you get the updated user object back from the server as the response, you can simply update the $user writable store value and every place in your app where you show the user object gets updated immediately.

Anything that isn't explicitly enforced by contract is vulnerable to misunderstandings. It's doing your teammates a great service, and reducing everyone's effort, by eliminating ambiguity and enforcing information flow by design.

I like to think of thoughts as streaming information, so I don’t need to tag and categorize them as we do with batched data. Instead, using time as an index and sticky notes to mark slices of info solves most of my use cases. Graph notebooks like Obsidian think of information as batched data. So you have a set of notes (samples) that you try to aggregate, categorize, and connect. Sure there’s a use case for that: I can’t imagine a company wiki presented as streaming info! But I don’t think it aids me in how I usually think. When thinking with pen and paper, I prefer managing streamed information first, then converting it into batched information later— a blog post, documentation, etc.

The combined stuff is available to components using the page store as $page.stuff, providing a mechanism for pages to pass data 'upward' to layouts.

Build data pipelines, the easy way

R (flowBeads

flow cytometry data were analyzed in R using the flowCore Bioconductor package (

Like with React, you can pass in callback props like onSave and onDelete, which is the main way you send data out of a component to a parent.

In this app, we have a <Hoverable> component that tracks whether the mouse is currently over it. It needs to pass that data back to the parent component, so that we can update the slotted contents. For this, we use slot props.

This is probably one of the biggest things to get used to in React – this flow where data goes out and then back in.

Furthermore, and differentiating digital time from clock time, he suggests that a lack of adherence to chronological time is compounded by the fact that digital technologies connect with a flow of information that is al-ways and instantly available. He argues that continual change, which is bound up with web services such as social network sites, blogs and the news, is central to the experi-enced need for constant connectivity.