End-to-End TypeScript: Database, Backend, API, and Frontend

[@mikkelmalmberg3060]

Great format, Gary! Here's to hoping this channel will become a thing !

[@sesgoe]

Watching you navigate around your codebase using Vim is what I've always wanted to be as a programmer. Might have to pick up Vim...

[@seanyohara]

Funny to see only your hard gestures as you're speaking. Great video, as always! Your blog posts inspired me to use io-ts in a project at work.

[@roberthuberdeau7433]

Watching this made me miss the old destroy all software screencasts. Thanks so much for making this!

[@vinitkumar2923]

Finally it is here. Thanks for these videos. Also, like this format. I think DAS videos takes more time, takes to make, so hoping these videos keep on coming.

[@ricp]

cool way of presenting, explaining this - and the voice is conducive for learning - it reminds me of Sam Harris , great content!

[@warmupz]

Made me miss Destroy All Software even more!

[@michaelr280]

You have accurately captured what makes things like typescript great

[@viktormalmedal265]

Great demo! Would love to see more typescript examples in "real" applications :)

[@ee7keelt]

Wouldn't you have your dotfiles for nvim available by any chance?

[@yowchun95]

Thanks Gary for such an awesome video!

[@xakonable]

Great format, amazing content, as always!

[@nokalko]

How would you roll this out to production? You need to be able to keep everything still running while you are deploying. The client does not share the type definitions but when a running client gets a number instead of a boolean from the API it'll potentially break.

[@ChristopherOkhravi]

You have a KZbin channel? :O Instant subscribe.

[@rahmadsubekti718]

who is him? Sorry, because I didn't familiar with him.

[@MichaelMerritt]

Here to watch you become a youtube GOD.

[@imtk]

Is it a monorepo with frontend and backend in the same repo? If so, what would be a good approach to use shared types between different repositories (front and backend in separate repos)?

[@balotofi]

Yes I think that's the reasoning behind the name monorepo. Maybe having a base file that is identical in both repos where the types can be imported from would be good. Like a general schema

[@highwind81]

What's the keyboard?

[@philipp7145]

Durgod Taurus K320 TKL

[@RobertoFrobs]

@@philipp7145 Which switches do you think he's using?

[@MikeMannix]

@@RobertoFrobs sounds like blue to me

[@drew1321]

What keyboard are you using?

[@dpassen1]

Do you normally not use line numbers or it that for presenting?

[@pyrhho]

What's up with the split between api/endpoints, and api/pages? Just POST vs GET? or is there some other distinction?

[@cagmz]

@@garybernhardt7185 are you doing multiple GET requests per page to fetch data for different components?

[@finnwillows6031]

Nice. Typescript used to become the opposite of loosey-goosey JS.

[@guillaume_simard]

What if you do progressive rollout? Now you've coupled your database to your API and to your client. You can't have two versions of your app running concurrently. If you have a mobile app, you need to forcefully deprecate older versions since they rely on an API that doesn't exist anymore. I love the idea here, but I do feel that you'd benefit from a bit more abstraction between the database and the core logic, between the core logic and the API (and versioned APIs). This might be completely overkill, depending on your needs, but there's definite downsides to have a database column type change propagate all the way to the client.

[@dimitardimitrov3421]

Can someone who knows vim (I’m still a newb) tell me how he searches for files and opens them right away? His workflow looks really cool.

[@charlespeters91]

What's the backend stack?

[@nomasprime]

www.executeprogram.com/blog/porting-to-typescript-solved-our-api-woes

[@Goodvvine]

"What is version skew?"

[@Goodvvine]

@@garybernhardt7185 sure, it's just that it reminded me of the main cause for outages every weekly release on one of my previous teams 🙃

[@Puffypoo574]

Cool

[@ignazioolivieri3795]

Woooww all this for one check box iput a one notification? Seems that we come back to the past!!! We are shure that is good linguage code?

[@programmedlive]

Most of these pieces have equivalents in server-rendered apps. If this were a server-rendered Rails demo circa 2005, it would've had a db migration file (same here), a db model file (same here), two controller methods (corresponding to the two server endpoint files here), and various views (corresponding to the React views here). The only piece with no equivalent in most 2005 apps is the API schema file. That's the piece that makes it maintainable while still being a single-page app.

[@aviolito]

@@programmedlive and lots of tests, that we run.