Embed Notice

Coding is software development. But not all software development is coding.

Everyone who's worked on a software development team knows this.

Before you code, you have to model out what it is that will be coded. You have to define what it is the software will do.

When you arrive at one screen, what happens next? How do you expect humans to behave when they see something in your app? Will they even behave in ways you intend?

And funny enough, it's people who code that often can't answer these questions.

It's not because coders don't know but it's because they've been operating under a certain mental paradigm for so long, it's hard to get them out of it. That's entirely expected because what makes coders good at what they do is that they follow their own logic for how to execute a function.

But where product dev, UI/UX, QA, documentation, and bug testing come into play is in trying to understand additional paradigms. Namely, what happens when someone does something unexpected? How do we account for the unexpected?

That's all software development. Every experienced coder I talk to knows this They are more than happy to have that discussion, and are incredibly grateful that another pair of eyeballs considers this for them.

Because trust me, it's never just about coding.