React will update state throughout the user’s session. localStorage won’t change.When the user ends their session, save whatever the state is at that time to localStorage, making it available for hydrating in the next session.

So rather than continuously keeping localStorage in-sync with React state, let’s simply save state to localStorage whenever the user ends their session, either by leaving the app (‘unmounting’ the component) or refreshing the page.

set(key, v) { localStorage.setItem(key, JSON.stringify(v)) store.set(key, v) return v },

Our large project is going to need highly structured and predictable state management, and Svelte’s flexibility scales from trivial projects up to our big one. We’re looking at statecharts and XState to wrangle this problem.

Microsoft says it will make changes in its new Productivity Score feature, including removing the ability for companies to see data about individual users, to address concerns from privacy experts that the tech giant had effectively rolled out a new tool for snooping on workers.

Almost all interfaces today, with the exception of TheBrain visual user interface, are limited to organizing information into hierarchies, where a piece of information can only be categorized into one place. For simple applications this is fine, but for users engaging in more complex business processes, it is simply inadequate. A document will have a variety of different issues or people associated with it – with hierarchies one cannot show all these relationships without multiple copies of the information.

This conflicts in very basic ways with what other engineering disciplines expect. Toyota's stylists might be able to sell their renderings in art galleries, but you can't drive to work in one. In software, you can.

Similarly, we use an opportunity algorithm to quantify which of the customer’s desired outcomes are unmet, and to what degree. A desired outcome statement is a uniquely defined need statement that describes how customers measure success when getting a job done. We assign a number to a desired outcome that indicates whether products or services used in a given market adequately or inadequately serve it.

Imperative UI causes all sorts of problems, most of which revolve around state, which is another fancy term meaning “values we store in our code”. We need to track what state our code is in, and make sure our user interface correctly reflects that state.

Yet many teams struggle to achieve a unified way of evaluating what they’ve delivered. Only 1 in 10 have a process for assessing the success or failure of newly-launched products and features.

For the product teams lacking a systematic way of logging these feature requests, pain points, and other bits of user feedback, a lot of valuable information ends up slipping through the cracks.

Microlearning: Knowledge management applications and competency-based training in the workplace

Instead of using classes and local state, Deku just uses functions and pushes the responsibility of all state management and side-effects onto tools like Redux.

It adds a few constructs to the language to solve one of the most complex problems in UI development — state management.

role-based access control, or RBAC

State changes flow from the roots of this graph (which we call atoms) through pure functions (which we call selectors) and into components.

Recoil defines a directed graph orthogonal to but also intrinsic and attached to your React tree.

For reasons of compatibility and simplicity, it's best to use React's built-in state management capabilities rather than external global state.

Recoil

Solid’s State primitive is arguably its most powerful and distinctive one. Through the use of proxies and explicit setters it gives the control of an immutable interface and the performance of a mutable one

Since Solid uses fine grained updates and Components are only rendered in their entirety once, you can wrap over state simply by using closures.

MobX - for me personally MobX is a far better way to manage state than React Hooks. It doesn't care about the UI layer so it can be used outside the React ecosystem, and it's simple to mutate data.

The $ contract for auto-sub­scrib­ing is lovely in its sim­plic­ity and flex­i­bil­ity. You can adapt your own preferred state-man­age­ment pattern or library, with or without Svelte stores as helpers. Svelte does not fuss about how you want to manage your state.

So today, as a somewhat limited experiment, I played around with my Hypothes.is atom feed (https://hypothes.is/stream.atom?user=chrisaldrich, because you know you want to subscribe to this) and piped it into IFTTT. Each post creates a new document in a OneDrive file which I can convert to a markdown .md file that can be picked up by my Obsidian client.

This last characteristic may be the easiest to evaluate. Unless the position is very junior, I’ll usually hire product managers who’ve actually shipped a product. I mean from start to finish, concept to launch. Nothing is a better indication of someone’s ability to ship great products than having done it before. Past performance is an indication of future success

I always insist that at a minimum, representatives from engineering, design, and marketing meet a potential PM candidate.

I often joke that much of the time your job is to be the advocate for whoever isn’t currently in the room - the customer, engineering, sales, executives, marketing. That means you need to be capable of doing other people’s jobs, but smart enough to know not to. Great PMs know how to channel different points-of-view. They play devil’s advocate a lot. They tend to be unsatisfied with simple answers.

So what do I look for in a PM? Most importantly, raw intellectual horsepower. I’ll take a wickedly smart, inexperienced PM over one of average intellect and years of experience any day. Product management is fundamentally about thinking on your feet, staying one step ahead of your competitors, and being able to project yourself into the minds of your colleagues and your customers.

2. Develop specific superpowers — don’t just rely on being a smart generalist.

Whatever the future intentions of the PM, one thing remains for certain: this position is at the intersection from where founder strategy, user feedback, development team management, and market awareness come together. From what’s been said, it certainly appears that this is not a role that you “fall” into, but rather could aspire to be in.

What’s more, to be a good PM, individuals also need to understand that it’s all about the bigger picture. Great managers “win” games, meaning that it’s not about getting a product out the door, but by ensuring that over the long-term, the team helps solve a larger problem. Nash says it’s not about getting an “E for effort” and brush off things that don’t work.

The product manager isn’t the one that’s just sitting around overseeing the various teams and seeing whether it’s on track to meet the scheduled delivery or launch date. They are the ones who need to understand the market and that means knowing who the competitors are, what consumers want, and being able to help the marketing and sales teams better target them.

More tactically,helping your team often means being the person who writes and summarizes notes after a long meeting, or writing a spec to make sure you have captured the team’s consensus and plan in written form.

A lot of people describe a product manager as a CEO of the product or the “owner” of the spec, but I think that over-ascribes influence and authority to the product manager. The best teams operate in a way where the team collectively feels ownership over the spec and everyone has had input and been able to suggest and promote ideas. The best product managers coordinate the key decisions by getting input from all team members and are responsible to surface disagreements, occasionally break ties, and gather consensus (or at least ensure that everyone commits to a plan) when decisions get made.

Great product managers understand the very tricky balance between getting it right and getting it out the door.

While shipping matters, the best product managers help the team make sure it’s the right product. Building something that doesn’t exist yet is always fun, but never a slam dunk.

More importantly, once shipped, the best product managers can measure whether the product shipped is the right one. They should work closely with the team to make sure the right moments in the product are measurable, and that the hard questions about whether people are really using the product can be answered.

Great product managers listen to user feedback all the time — whether it’s from usability tests, meeting users in the field, reading support emails or tweets, or working with the people in your company who do all of those things on a daily basis.

What do you think the most important things we should be doing over the next year? What will get in the way of us doing that? What’s going well, i.e. what should we make sure we don’t change? Is there anything you think I should know about?

To me, abandoning all these live upgrades to have only k8s is like someone is asking me to just get rid of all error and exceptions handling and reboot the computer each time a small thing goes wrong.

React Stately is a library of state management hooks for use in your component library.

Provides state management for tree-like components. Handles building a collection of items from props, item expanded state, and manages multiple selection state.

So why don't we extract the shared state out of the components, and manage it in a global singleton? With this, our component tree becomes a big "view", and any component can access the state or trigger actions, no matter where they are in the tree!

Stores are global state. While context is local state.

Notice it's not related to components. Another crucial difference is that it's accessible from outside of components. And good way to determine where goes where is to ask yourself, can this particular state and functionality still makes sense outside of the displayed component?