Lessons Learned from the AI Roadmaps Project

| Product Engineering

These are the lessons I learned while building my AI Roadmaps project:

  1. Set Clear Goals: Define your goals for the project before starting it. Focus on achieving these goals and avoid distractions.
  2. Design High-Level System First: Before writing any code, design the overall system and its components. Break down the system into independent components and prioritize the most important one. Focus on one component at a time to avoid overwhelming yourself.
  3. Prioritize Foundational Work: Start with things that will be used throughout the project and make later development easier. For example, set up schemas, models, and centralize data fetching.
  4. Design API Responses Early: Clearly define API responses before starting to write code.
  5. Write Independent Schemas: Design schemas as independent modules so they can be reused across different parts of the project, such as API documentation, data validation, and ensuring consistent API responses.
  6. Follow Layered Architecture: Use a layered design pattern for the backend. For example, separate the API layer, service layer, and repository layer for better maintainability.
  7. Centralize Configurations: From the start, store all configurations in a central location so they can be easily updated when needed.
  8. Use Environment Variables: Place environment-dependent variables (e.g., API keys, URLs, log levels, paths) in a .env file from the beginning. It will help you shift your project to multiple environments easily.
  9. Adopt a Mobile-First Approach: If your users are primarily on mobile devices, prioritize mobile-friendly design from the start.
  10. Show Loading/Processing States: For actions that might take time, show loading or processing indicators. For example, the server’s response may be fast in local development but could take longer in production due to the internet speed of the user or server issues.
  11. Be Consistent with Naming: Use consistent naming conventions for resources in the system. For example, choose between “Users,” “Clients,” or “Customers” and stick with one term throughout the project.
Scroll to Top