housecor.com
Courses: http://pluralsight.com
YouTube: http://youtube.com/@housecor
Consulting: http://reactjsconsulting.com ⚛️
134 posts
2,077 followers
61 following
Prolific Poster
Conversation Starter
comment in response to
post
Tesla paid back the loan, and did so early. Implying they survived merely because of a loan is reductive.
SpaceX survives because, like Tesla, they're profitable. They're able to do things cheaper than alternatives, because they innovated and created reusable rockets.
comment in response to
post
Many current and former Tesla employees received stock options and are now quite wealthy.
Tesla is an obvious American success story. Without Tesla, EVs would likely still be rare.
What system do you propose to avoid successful entrepreneurs getting too wealthy for your taste?
comment in response to
post
With 2, we may never bother becoming stricter. And any new code is held to a low standard, which creates "type debt".
With 1, new code is held to a strict standard, and existing code can selectively have looser typing rules via nested tsconfigs, or by disabling TS in spots if necessary.
comment in response to
post
How? Because he helped build multiple extremely valuable companies.
His wealth primarily stems from *equity* in those companies, and he funded them in hard times despite many near bankruptcies. Both SpaceX and Tesla would likely have went under without his financial support.
comment in response to
post
I'm saying it's good...but it's important to know how to code so one can debug and validate the results
comment in response to
post
Example: The Dropbox team used this pattern to test many OS and file system edge cases quickly on CI.
comment in response to
post
Result: Now we can code and test against a mocked implementation in non-prod environments. The mocked implementation can be deterministic and fast, and thus allow quickly testing our business logic against many scenarios. In prod, the wrapper implementation merely forwards to the real APIs.
comment in response to
post
Still early so can’t say
comment in response to
post
Oooof wow
comment in response to
post
Could use linting
palantir.github.io/tslint/rules...
comment in response to
post
Tried using Zod for that?
comment in response to
post
Sad but true!
comment in response to
post
I agree
comment in response to
post
Oops, I didn't even realize depcheck was no longer maintained. I use Knip and agree it's preferable but I was using Depcheck for a moment since it's easier to run quickly with no config when auditing a project.
comment in response to
post
The types are in comments which can be optionally stripped during a build but are ignored in the browser either way
comment in response to
post
Example of needless RSC payload bloat:
Passing a large array of objects with many properties from a server component to a client component when only some of the properties are used by the client component.
Solution: Only pass necessary data via props from server to client.
comment in response to
post
yep
comment in response to
post
My concern: Inconsistency may infer it's an accident rather than deliberate.
Example: I wear the same polo throughout my 3.5 hour course so it feels cohesive.
To your point - does this matter to people? Not sure. Arguably changing shirts often might be more interesting!
comment in response to
post
Good points! Thanks James.