Rafał Pocztarski is a software developer at Paramount. He got obsessed with programming when he was 6 years old and hasn't recovered since then.
Much to everyone's surprise, it was recently revealed that the TypeScript team at Microsoft had been secretly evaluating multiple programming languages to rewrite the TypeScript compiler in. The best language for that task turned out to be Go.
How to increase your server bills and ruin user experience in few easy steps using widely used techniques and programming styles that are common both on the frontend and on the backend.
JavaScript has always been a functional language in object oriented clothing. The same can now be said about TypeScript, maybe even to a greater extent. This talk will describe the evolution of functional programming in JavaScript and TypeScript, and the future that is likely to happen.
Few programmers and programmers plan their careers beyond the senior position, but at every stage of this path it is worth knowing in which directions you can further develop in order to manage your personal and professional development in such a way as to adapt future work to our capabilities and preferences. During this lecture, I will try to tell you the most important things that I did not know when I started, and which would help me a lot.
Since Node.js came out, a fullstack developer could know just one language - JavaScript and later TypeScript - to write the entire code base. There are many professional software developers today who don't even know any other language. WebAssembly is going to completely disrupt this and it's time to learn low level systems languages, out of which Zig is an interesting choice for many reasons.
Once upon a time, it used to be the case that frontend developers having learned the basics of backend development could have been considered sufficiently proficient in the full development tech stack, or being full-stack developers if you will. Now, in the era of DevOps, knowing only the Dev part is no longer enough. This short presentation will introduce some of the most important concepts and abstractions to know in the modern world of cloud computing
Recently, after one of my talks, someone has told me that he is getting into Deno because I discovered Node.js in 2009 so now when everyone is crazy about Node and I'm shifting my focus to Deno, then I must know what I'm doing. This talk is about the technologies on my radar that I think are worth keeping an eye on in the year 2020.
It is undeniably true that writing unreliable software is irresponsible. This talk will present the foolish alibis that are used by developers whose code is crashing on null or undefined, explain why crashing on bad input is never acceptable, and show techniques to avoid those crashes in your frontend and backend code written in JavaScript and Typescript.
In 2009 Ryan Dahl presented Node.js, a server-side JavaScript runtime. In 2018 in his presentation "10 Things I Regret About Node.js" he announced a new project called Deno. This talk is about the difference between Node and Deno, its current status and the changes since its original announcement.
I will talk about the roots of object-oriented programming, how we deviated from them over the years and what can we do to rediscover the fundamental idea of objects and make our code more maintainable.
TypeScript dla średnio zaawansowanych
Node.js dla średnio zaawansowanych
Testowanie kodu 3/3: Testy integracyjne
Testowanie kodu 2/3: Testy end-to-end
Testowanie kodu 1/3: Testy jednostkowe
