I'm developing a website for my aunt and trying to approach it like a professional project. I've conducted a requirements interview to create documentation including a Software Requirements Specification (SRS), Business Requirements Document (BRD), and a Business Case. The challenge I'm facing is balancing my enthusiasm for newer technologies, like Bun—because it's fast and great for developers—with practical concerns, like the lower hosting costs of NodeJS. I want to provide a solid solution, but I'm concerned my aunt, who isn't tech-savvy, might not provide input that aligns with what she needs. What's the best way to determine the right technology for her project?
3 Answers
It's definitely tricky to balance personal preference with what's best for the project. I usually start with my go-to stack for ease of deployment, but if it doesn't meet the project's needs, I'm open to alternatives. When I switched to Go for a project, it took longer to get up to speed, but I learned it's all about finding the right fit for the specific needs.
You're already on the right track by recognizing the balance between your preferences and the project requirements. Instead of thinking about what you want to use, shift your focus to what will keep things simple for your aunt. She won't care about the tech as much as she wants a working site that’s easy to manage. Often, the boring options are more reliable!
Without more specific details about requirements, it’s hard to give you a concrete answer, but if it's just a simple site for your aunt, maybe consider simpler platforms like Wix instead of diving deep into SRS documents. Sometimes, keeping it straightforward is both faster and more effective!
I get what you're saying, but I’m using this project to practice and learn. It’s kind of like how artists grow through small projects and reflection!