Build on top of quality. Good software is more important than it ever has been before.

And, the more you think about everything you do, in the sense of multiples, you can scale it outward, with almost infinite limits.

If you scale on top of slop? That's exactly what you'll get in return, but at scale.

Scale is everything. AI is what fills the gaps that were previously near-impossible to obtain.

You build not for once, but for many. That one page you built in JS, can now be leveraged to feature implementations, new templates, PRDs, tests, NPM packages, frameworks to be used elsewhere.

Building without having a structure in place will shoot you in the foot, especially if you're using tools that get you closer to developer workflows, like Cursor, Copilot, etc.

Shoot to fill the gap! AI tools aren't ready to replace anyone at this point, so it requires the discipline to fill it.

5. Review - We need review TWICE in here. One for reviewing the plan, now you get to have the AI review the implementation.

3. Revise - Make sure the AI keeps the top 10 security issues, SOLID, DRY, and ETC (easy to change) in mind during the planning and build phases. (will share the file in the comments).
4. Execute - Let the AI move forward once everything looks good to go.

1. Plan - Let the AI write out the plan first. Have it build out a plan doc, make sure that it knows it's not writing for a developer.
2. Review - Check out the plan. Make sure that it makes sense. Ask questions and revise if it doesn't.

Here are a few rules using a PRRER method (yes, I made that up, but hopefully it'll be easier to remember. Also, it's a rolling RR, like in Spanish) that anyone can take to build software with AI, the right way.

What I know is: If done wrong, there are hundreds of traps you can fall into. And this is exactly why experienced engineers are laughing at you while you attempt to build something that ends up not working.

Helping people is important to me. Feel free to follow to learn more about the rules of business coming from a programmer's worldview. Learn to understand your world, instead of being a victim of it.

Rules are on a company to company basis, however their are a lot of CORE rules to understand. Life is a bit more complex (and, can even be more fun) to only have one or two rules.

3. Research, research, research. You need to understand a company. If you don't care about them, they're even more likely to not care about you.

1. Leetcode is the name of the game. GRIND IT OUT. Spend 10 hours a day on it if you have to (or can).

2. Learn their stack. Get so good at it you can spin several applications up in a day.

How do you know the right areas to grind? Understand the rules of the game. Look at them logically, without hate, and allow yourself to follow them (or break them entirely).

Programming is SOOO similar.

Looking to work at a big company? Here are the rules:

Look at this like a Dark Souls game. Need to beat the next boss? You'll have to grind an area for larger amounts of souls for leveling up. Or, another area to get smithing stones to improve your equipment.

It all comes down to "time-grinded" in a dedicated area.

I want to share this simple rule.

TIME IS THE ULTIMATE LEVER.

Time is what allows you to become the top 10%, top 1%, top 0.1% programmer. Leveraging it will get you to where you need to go.