joshribakoff

Brex went from virtual reality goggles -> corporate finance saas

They basically started on the billing system for their VR and decided to pivot to that.

Types help verify you have done the necessary validation, assuming your validation library does type narrowing.

> Hooks was the natural evolution that removed all possibility of accidentally referencing stale data.

It unfortunately does not, you can hve various foot guns with refs or omitting dependencies from the array argument; but to your point it makes it a lot easier to ensure you do it correctly by collocating logic related to each cross cutting concern instead of entangling the code in the lifecycle methods.

More precisely it makes it easier to follow correct patterns, but as always that is subjective and hooks can be contentious :)

I have an eight year old and no matter how many times I explain the concept of sarcasm he just can’t get it. Even seconds after explaining the concept, I test him with an absurd statement and he takes it literally. I have made repeated attempts to teach him and he just doesn’t get it. Their brains are still developing

Some companies do tender offers (stock buyback) to give employees liquidity, but unfortunately the c suite and investors (those who typically have a more favorable liquidity preference) can cause the tender offer to be oversubscribed if they enter more sell orders than there are buy orders. Usually this means common stock owners do not get to participate. Preferred stock can also be converted to common, but not the other way around.

They were trying to execute the principles in “the innovators dilemma” by acquiring customers while they are small and helping those businesses grow. I speculate that the sudden pivot came from the VC investors not the founders. First the drive for profitability most likely stemmed from emerging competition like ramp, and the now with growth stocks losing momentum and the credit market drying up, the VCs have more leverage to run things the way they want.

Many people don’t understand how card networks work. Generally there are many parties involved in a payment. There is an issuer (usually a bank), acquirer bank, the visa network itself, the payment processor company, etc.

If peering between any of these entities is interrupted, there are sometimes “stand in authorization” that allows the card to continue to work, or people may assume the visa network itself is at fault even if it is not the issue per se.

It’s possible (even likely) that a retailers payment processor is having issues in certain scenarios and the retailer just issues a blanket statement “visa is down” which is actually a misnomer.

Mostly to make the API declarative, similar to what you could do with OOP. If you have a 3D UI, a 3D UI framework might make sense, for example react has “suspense” for loading states, and you can imagine having 3D loading states, with placeholder models being rendered

The problem with your statement is that AI drivers do rely on traditional logic already, but that cannot be applied to the perception part of the stack. It doesn’t matter if your rule is “if perceives truck, stop” if perception is telling you there is no truck stopped there. The rule also can’t be “if white pixel, stop” or “if Lidar bounces off steam and returns, stop”

> NHTSA notes that Tesla’s Boombox and the company’s pedestrian alert sounds are mutually exclusive

I wouldn’t characterize this as Tesla allowing users to swap the pedestrian alert sound, even though the NHTSA is expressing concerns consistent with that, they go on to concede unambiguously that it’s not the case.

It sounds like actually they are concerned both features can emit noise at the same time.

A good faith interpretation is that blind users may not realize it is a car because they didn’t hear the “car noise” over the noise of the boom box.

However, this seems like NHTSA is being sensational. A driver could also just have music playing inside the cabin with their windows down, and it doesn’t seem that different. From that perspective, forcing tesla to do a “recall” seems dubious. Whether the “boom box” noise comes from the “pedestrian alert” speaker or some other speaker seems like a technicality to me.

Either way, the NHTSA’s request is pretty reasonable, despite their concern seeming contrived. Disabling the boom box while summoning the car doesn’t create undue burden for tesla or it’s users, but it doesn’t really solve anything either (as noted by Tesla there have been no issues with the previous functionality). It feels like theatrics on behalf of the NHTSA.

what you’re referring to is just simulating, at least after the point your modified algorithm does something slightly different in the simulator than the real car did in real life.

I haven’t seen anything about devtools altering runtime semantics but I may be wrong, that is something I think I disagree with because of the possibility to have bugs that go away when trying to debug

Blame the employer (or yourself for not switching) if it’s really that unbearable, it’s not the React team’s fault

The hacker news post doesn’t even link to the article about what’s new in react 18: https://reactjs.org/blog/2022/03/29/react-v18.html#new-stric...

> To help surface these issues, React 18 introduces a new development-only check to Strict Mode. This new check will automatically unmount and remount every component, whenever a component mounts for the first time, restoring the previous state on the second mount.

the hacker news title just isn’t precise about what part of it changed and doesn’t even link to the relevant article

https://reactjs.org/blog/2022/03/29/react-v18.html#new-stric...

Excellent synopsis.

> React complains that you tried to change the state on an unmounted componment.

They actually got rid of that in the new react :)

> handle the double rendering issue when interacting with the DOM directly

I think the idea is whatever they do to the DOM needs to be idempotent. Those should be using useLayoutEffect usually.

It’s totally opt in, and in development only, so react doesn’t prevent you from using that other lib

> Are the people building React completely oblivious

Perhaps the people criticizing it so flagrantly are oblivious to the goals motivating their design choices.

No one is forcing you to use it.

I think you mean it logged log messages twice?

I don’t believe having devtools opens changes the runtime semantics of the app.that would defeat the point of the devtools.

I do know it annoyingly logs things twice

> I’m surprised they even offered to let him stay if he removed them

Isn’t it just like with the police, they can legally lie in this context? “If you turn yourself in we’ll go east on you”. They can just turn around and fire him anyway because it is an at will work state

For something in demand that takes decades to master that less than 1% of the population can do in one of the most expensive cost of living areas in the world, so yes.

Read the hooks FAQ, the linter is not wrong, you are :) https://reactjs.org/docs/hooks-faq.html#is-it-safe-to-omit-f...

The idea with hooks is a compiler could generate the dependency array. The flaw isn’t with the hooks paradigm

Prisma uses rust for two main reasons from what I understand. 1) to keep the engine portable and maximize code reuse, to make projects like this Python adapter possible for example 2) under the hood Primsa does not use joins. It does a waterfall of queries (but not n+1), then stitches the data together in memory, which happens in the rust engine for performance reasons

Maybes mapped types are an example? https://www.typescriptlang.org/docs/handbook/2/mapped-types....

I use Prisma and it’s far from perfect but what I love about it is you can introspect a legacy database and generate a Prisma schema, and use the database as the source of truth. You’re not tied to a 1:1 relationship between classes and tables, and the correctness of the types do not depend on tediously annotating code correctly. Excited to see more languages supported!

When I first got my Tesla, the “gas” pedal was annoyingly further forward than the brake pedal. As “full self driving” progressed I drive “manually” increasingly less often and now what once annoyed me is convenient, I can easily rest my foot there near the gas pedal without accidentally pressing it, at the ready to hit the brake pedal if needed which is located next to where my foot sits. It took several years before the design started to make sense and grew on me.

When your car drives more and more autonomously having manual controls that can accidentally be activated start to make less sense, we’re not there yet, but someday there will likely be no steering wheel at all and people will react the same way they are now.

You have to pull the update, all that they push is an icon that shows up that you can click to download the update

It does if you have the AC on “auto”. There’s also another UI element that displays “defogging limited by settings” if you make manual adjustments and it detects the need

For some people “i” and “j” are a better name than “currentStepInOuterLoop” or whatever other verbose names. I think it really depends on context, though