3 October 2018, 6 min read
This is the second part of my blog post series about dealing with React components that have too many responsibilities. Have a look at the first part of the series (Single Responsibility Principle in React Applications – Part 1), if you haven't already.
Jacek is a senior front-end developer at Sunscrapers. He earned a MSc degree in Computer Science from the Silesian University of Technology and has since worked as a full-stack developer for a number of companies, today focusing on front-end applications. Passionate about best practices in software development processes and opportunities offered by the newest web application technologies.
