Thread by @chalmagean

I used to spend hours googling a solution to transition my ideas into code.

Fast-forward 15+ years, the code writes itself.

And it's so simple, I wish I knew this back then. Here's how 🧵

1. Start with the end in mind (WHY)

Most web applications exist to solve a problem for the user.

- What's the user's goal?
- What is the user trying to achieve?

2. Map out the user's journey (HOW)

There are usually steps involved in achieving a goal (e.g. submit this form, click here, etc.).

- How does someone get from point A to point B in your app?
- What are the steps needed for the user to solve his problem?

3. What data do you need to make it happen? (WHAT)

At a high level, it's mostly about processing data.

- What data do you need to be able to solve the user's problem?
- Where does it come from? (e.g. the user, an API, etc.)

4. Start implementing (EXECUTION)

Now you know WHAT your technical requirements are, HOW the application looks like when it's done, and WHY you're building it so you can make decisions about the little details on your own.

The plan writes your tests, which write your code.

That's the magic!

If you want more tweets about #rubyonrails, make sure to follow @chalmagean.