“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.

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.

#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.

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

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

What if...? #eslint #prettier

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.

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.

I am announcing my first open-source project: JS Style Kit!

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

Just got my ticket for #EpicWebConf! Looking forward to meeting some of you!

`useEffect` is often overused in React. But there's a straightforward way to think about when to use it.

Are you syncing to an external system? If the answer is no, you should not be using a `useEffect`.

I settled on an API I like for the style guide. It's a function that takes an optional config object for customization.

I submitted my first open source PR today.

I use `prettier-plugin-json-sort` to consistently sort JSON keys. This makes it easier to find what I need, and reduces PR diffs.

My goal for the holiday break is to release my first NPM package.

It's an opinionated, zero-config style guide for ESLint and Prettier. You can set up the whole thing with one line of code.

Why can’t AI companies use semantic versioning? OpenAI went from 3 to 3.5 to 4o. Claude went from 3.5 to 3.5. Do they know that there are more numbers?