When we code, we tend to focus on the “happy path”. Yet in the real world, there is validation, logging, network errors, and other “unhappy paths”.
The good news is that we know about these different paths. We know that validations may fail, and we know that network requests may not come back. Railway-oriented programming is an approach that makes sure we think about and handle all these possible outcomes. Some languages regularly benefit from it; now, it’s time for TypeScript.
|T for TypeScript, T for Train, robust code you will maintain
|Your biggest opportunity to learn is out there
|Weby budoucnosti s AMP
|The Habits of Highly Effective Engineers
|Typed Functional Programming in TypeScript with fp-ts
|React Day Berlin
|Symbols complicated it all
|Node.js Meetup #34
|Jest can do whaaat?
|React Open Source Berlin
|Async testing Koa with Jest
|Node.js Berlin Meetup
|Async testing in Jest
|React.js & React Native Berlin Meetup
|15 months of AMP
|Two years of Elm (Dva roky Elmu)
|Purifying React (with annotations)
|CSS Code Quality with Automatic Tools (Automatické nástroje pro kvalitní CSS)
|Jak nám responzivní web rozbil obrázky (cs)
|Organizace kódu v týmu (cs)