Source originale du contenu
- You spend more time contemplating and discussing code than you do writing it.
- You spend more time thinking about how the end product affects users than you do about how pleasurable it is for you to write its code.
- You think in terms of relationships and systems, not just the thing you’re coding up at the time.
- You choose technologies based on what they can achieve, not how new, trendy, or ergonomic they are.
- When a bug ticket is given to you, you take the time to consider what its implications are rather than just diving in to write it off your list.
- You’re not happy to add new features just because it gives you something to do.
- You’re not happy being told what to code or how to code it. You think you should be part of that decision making process.
- You think of code as means to an end. It’s a tool for realizing design thinking.
Is this you? Then you are not a coder. You are a designer who is skilled in coding.