Nathan Drake

“AI is going to write bad code and cause tech debt.”

As opposed to now, when human devs write perfect code with no tech debt.

Dark and way zoomed in!

My forearms are sore just thinking about it.

Next time you face imposter syndrome, just remember: your outie is a good coder.

I’ve never been a junior dev.

I started my web3 agency immediately after my boot camp. I was hired to my current job at mid-level.

Being a junior is a state of mind. So when they say they don’t hire juniors, just say, “I’m not a junior.” Then show them how you’re the solution to their problem.

lol yes. I generally use milk but I don’t get the hate for dry cereal.

Fruit Loops are better raw. I don’t make the rules.

#EpicWebConf was an amazing experience! It’s invigorating to meet so many passionate developers from around the world. Thank you @kentcdodds.com for taking the time to bring all of us together.

See you there!

I have 4 email accounts. I implemented @sanebox.com yesterday and this is what my inbox looks like now.

Code Quality in the AI Era: Modern React Workflows, Wed, Mar 19, 2025, 5:00 PM | Meetup **React Office Hours** Starting @ 5pm we hold office hours. Come on by to get some help, ask questions, and meet other developers. Or just hang out! **Code Quality in the

I'll be speaking tomorrow at the @reactjsatx meetup on AI workflows. It's always a good time, I hope to see you there!

I’ll be there! Should be a good time.

What if...? #eslint #prettier

Learn how to utilize AI to make yourself more productive. People will notice, and they will pay you for it.

AI is doing more of the manual code writing so that I can focus on the big picture and get more done. Even before AI, a fraction of my job was actual coding. There are meetings, support, documentation, PR reviews, planning, strategizing a problem, etc.

That thought process is pointless. Doom and gloom about the future without actionable advice is just an attention grab.

All we can say for sure is that our jobs as developers are changing, I have little reason to believe they're going away.

AI doomers tend to say the same things:

- "Developer jobs are going away."
- "No one should go to school for computer science."
- "There's no point in going to a code boot camp."

But when you press them on what to do instead? They deflect. They have no answer.

js-style-kit A zero configuration style guide for ESLint and Prettier. Latest version: 0.1.6, last published: 2 days ago. Start using js-style-kit in your project by running `npm i js-style-kit`. There are no othe...

www.npmjs.com/package/js-s...

In any configuration, it's set up to honor the user's preference for filename and things like `it()` vs. `test().`

If the user prefers Jest, I still use a Vitest rule to enforce that test filenames are used consistently (".spec" vs. ".test").

The user could also pass in "node" or "bun" and import their test suite from "node:test" or "bun:test" while still using the Jest ESLint rules.

I decided to use both plugins simultaneously and optimize them based on the user's preferences.

If the user is using Vitest, I add the recommended configuration for Vitest but keep some formatting rules from the Jest plugin.

I added testing support to js-style-kit yesterday. It was a fun challenge because I wanted to support Jest and Vitest. The ESLint plugin for Vitest is based on the Jest plugin, but they have some different rules.

Well I was gonna play video games all day, but I might just submit a PR to @nextjs.org to convert eslint-plugin-next to ESLint v9 flat config instead.

Thanks! Let me know how it goes if you try it.

I wouldn’t fight you on that one! I wanted to go with Prettier defaults, but I don’t mind a bit more space. 80 can be restrictive, especially if you’re not a multi-tab kind of coder.

js-style-kit A zero configuration style guide for ESLint and Prettier. Latest version: 0.1.4, last published: 13 hours ago. Start using js-style-kit in your project by running `npm i js-style-kit`. There are no ot...

Please try it out and let me know what you think!

www.npmjs.com/package/js-s...

Roadmap:
- Docs, docs, docs.
- Nextjs plugin
- Strongly-typed rules
- Listen to feedback and adjust (I want to reduce config as much as possible)

- It includes all dependencies; let me worry about the updates.

- Anything you don't use is removed from your config for performance. As long as you install it as a dev dependency, no unused plugins will hit your bundle.

- Prettier config includes JSON and package.json sorting for consistency, CSS sorting, and optional Tailwind support.

- ESLint config plugins include Typescript, Import, JSDoc, React, React Hooks, and React Compiler. Perfectionist to sort all imports and objects consistently.

JS Style Kit does it all for you. It is opinionated (I like a strict setup) but reasonable. My aim is for it to be zero-to-minimal config. Install and set it up once, then focus on shipping.

Getting them working together to help you and not fight you can be difficult. There are many configuration options and plugins, and keeping up with the updates over time is hard.