3. Think First!
Eager to dive into a new project? The questions an architect asks before writing a line of code — so a fast start doesn't become a slow recovery.
At the start of a new project, developers are often eager to dive right in. A favorite framework is quickly set up, the standard set of libraries is installed, and everyone gets to work. 💻🚀
But after a few days, the first issues arise:
- ❌ Data is not being handled properly.
- ❌ State is managed and updated in multiple places.
- ❌ Naming conventions are inconsistent.
- ❌ Components have a lot of overlap, leading to duplicate code.
- ❌ The chosen framework doesn't support that one feature essential for the project.
- ❌ Or worse: the technology doesn't work in the client's environment.
In short: we started too quickly, without carefully considering our technical choices. 🧠💥
"Think First!"
...is therefore the next tile in our "Developers Tiles of Wisdom" series.
🛑 Don't start building right away; take the time to think things through.
As an architect and lead developer, I always start projects by mapping out the technical options and constraints. A good start prevents frustration later on. 💡😊
🧠 These are the questions I ask myself
🛠️ Frameworks and Tools
- Which framework best fits this project?
- What skills do the developers on the team have?
- What already exists in the current codebase?
🌐 Technical Environment
- How does the backend work?
- Are we using third-party APIs?
- Does the client environment support the chosen technology?
🏗️ Architecture and Naming
- How will we structure the architecture?
- Which naming conventions will we follow?
⚠️ Risks and Bottlenecks
- What are the technical and planning bottlenecks?
- Are there dependencies within the project?
❓ Uncertainties and Planning
- What do we not know yet?
- When will we have that information?
- How will we handle changes during the process?
🔍 Think first, build later
Thinking things through is not a waste of time but an essential part of the development process. It is better to start a bit later and make the right choices from the beginning than to start quickly and run into problems later. 🕰️
✅ Mistakes and learning are part of the process. Don't be afraid to make mistakes or to adapt when you gain new insights. But only start once all the major doubts have been resolved. 🤔💪
📢 So ask yourself: do you always take the time to think things through, or do you sometimes jump in too quickly? 🤔
💡 Need help with starting a new project? Choosing the right framework? Implementing a solid architecture? Identifying risks? Following the best processes?
👉 Feel free to reach out—I'm here to help!
