TK

I come from a place that I'm pretty familiar with TypeScript before reading this book. But it was a great experience learning more about this language in depth.

The first chapter was awesome in a way that the book shows more about language than simply about the syntax. It talks about the relationship between JavaScript and TypeScript, how does the structural typing works, the differences between the type and value spaces.

The second chapter talks more about how TypeScript can improve the developer experience together with a code editor.

The following chapters are about how we can use types to be more effective.

I used this book as a reference to write my long-format essay about A Mental Model to think in TypeScript (https://leandrotk.github.io/tk/2020/07/a-mental-model-to-think-in-typescript/index.html).

I really recommend this book for beginners and experienced developers.

For me, there is doubt that Elon is a special and very different person. I liked that the book painted him not only as a visionary solving real humanity's problems but as a human being that's always learning, improving, failing constantly, and very passionate about interesting problems and the space.

A very interesting book if you intend to follow the technical leadership track and are not really into management. This is a career I want to follow and helped me have a clear understanding of how staff+ engineers can operate in an organization.

Each engineer's story was a little different because each organization requires different skills to solve their specific problems, but the ones that caught my attention were related to engineering sponsorship, technical vision & strategy, a lot of collaboration, and leadership.

Most of the stories and content are in Will's blog: https://staffeng.com

I focused more on advice like ‘little bets', capturing career capital, deliberate practice, having control over your work, and organizing a mission-focused career. I also think we can benefit both from the passion and the craftsman mindset he talks about. My concern was regarding putting these mindsets against each other over using both to have an accomplished career.

It was an interesting read about how software engineering works at Google. There are some things that are particular to Google itself (problems and scale) but most of the topics mentioned I already saw as a process or best practice working in the industry.

It's an interesting resource for newcomers and people who didn't have the chance to work in companies that are solving difficult technical and scalability problems.

I liked that it's a fast-paced book. Divided into topics and easy to digest. Some of the topics, like LSC, are very Google's (scalability) problem, and maybe it's not that useful for most of the companies in the world. But the overview on culture, tools, and processes were all interesting to me.