/home

Worst thing in software development is pushing an all-in-one architecture for software that serves different layers of an organization (departments, business units). If you do it, expect to land in leaky abstraction hell as you quickly learn that a User for marketing (lead) is different from a User for the accounting dept (billing entry). Such context collisions (an actual concept) push developers to bend the code and the code in ways it wasn’t meant to go.

All major services have policies to guard against automation. Whether its web scraping, click bots or more recently, autonomous AI agents, companies are not happy when their services are hit 10x faster and more often than a human would. My advice: always use a test account, don’t start with your 20 year old gmail account. This way you wont end up with a disabled gmail account like @iamlukethedev.

ESLint 10 is out and it comes with something truly great: config discovery starting from the directory where the linted file resides, instead of process.cwd() and moving down. This means you can have different ESLint configs for different directories without having to write a custom CLI wrapper over ESLint to deal with the whole thing. This guarantees that the config file in use is the closes to the file being linted.