Copy

The Tao of React Book

Earlier this year I wrote a long article called the Tao of React. It contains a lot of the lessons I’ve learned working with React for the last few years. I wanted to put together all the rules and guidelines that have helped me build well structured applications.

The reaction to the article was amazing and I’ve decided to go ahead and write a short ebook that will expand on the content of the article. It’s going to come out later this year and I will keep you posted with the progress. So far I’ve done the first draft, it contains twice the number of rules from the post. Next I’m going to rework all the examples and create some visuals for the chapters. I’ll keep you updated!
 

Lodash’s Structure and Architecture

To be a good developer you need to read a lot of code. I’ve been exploring the structure and design decisions of popular open source projects hoping to gain some wisdom. I decided to review Lodash because it’s the most downloaded library on npm and was surprised by how simple it was written. I imagined complex structure, abstractions and layers but there was none of that.

At the cost of some duplication and verboseness, the authors have made a library that can be easily read by anyone. Read the whole review here.
 

A Book Worth Reading

The Architecture of Open Source Applications contains reviews of popular projects, their structure, the design decisions and trade offs that their creators made. Architects explore thousands of buildings before they set out to build one. As developers, we often focus on the low level details like algorithms and don’t spend enough time learning about software architecture principles.

It’s not a book that you need to read from cover to cover. You can skim and read the chapters that you find interesting or just focus on the insights. Chapters I recommend are Berkeley DB, Graphite, Selenium and Sendmail.

A Video Worth Watching

Simple made easy is a talk from 2012 by Rick Hickey. I found it really insightful, it goes into details of why simplicity is important, how we can achieve it and why this is not easy. 

 

A Quote Worth Pondering

"Becoming an expert is often a consequence of tinkering, not the cause. Developing an intuition for what exists and what should exist has more impact than technical smarts." – Dan Abramov







This email was sent to <<Email Address>>
why did I get this?    unsubscribe from this list    update subscription preferences
Code Philosophy · 7000 Ruse · Ruse 7000 · Bulgaria

Email Marketing Powered by Mailchimp