Whatâs Coming Up Next For ESLint
ESLint was a pivotal dev tool in the Web space. Itâs reaching a stage where adding new features is held back by the architecture of the project.
I love articles like this, where you get insight on how to pivot large software with millions of projects depending on you. What tradeoffs do you make? How do you slice up the work?
https://eslint.org/blog/2024/07/whats-coming-next-for-eslint/
Itâs probably time to stop recommending Clean Code
âClean Codeâ is historically one of those books that always gets mentioned in the list of âyou should read this if you want to code.â Reading responses to texts like this is always a great way to learn to evaluate technical decisions. Itâll involve you having to read Java, but its a good exercise.
Fifteen Years of Contributing to WebKit
Get some insight onto the career path of Ryosuke Niwa, a developer on Appleâs WebKit team. How did he get started? What led him to browsers?
Its a short read, but it stresses something I think a lot of people in WebDev miss. Try to build stuff. Not just websites, but try to make something that already exists! Your own babel transform, your own re-usable component library. Re-implement lodash. Make your own React. Whatever it is, always push the boundary of what youâre capable of.
https://rniwa.com/2024-07-20/fifteen-years-of-contributing-to-webkit/
Deep JavaScript: Theory and techniques
Wanna learn more about Javascript? Yes, yes you do. Read this book! Take the time to understand the concepts, bookmark stuff you find interesting!