Software engineer with 4+ years of experience in building products for numerous domains like fin-tech, real estate, video streaming, retail, and now e-commerce.
🦊 Writing about developer experience, leadership, and mental health
🐻 Co-Founder/CTO at Speakbox
🤓 Software Engineer
🎸 Amateur musician
Techstars Boston Alumni W21
Unexpected requirements are unfortunately pretty common!
The first important thing is inspiration. I usually am the most productive when I work on what inspires me at the moment. It is not possible every time, some tasks are going to be required and not inspiring, but if you have some flexibility on the timeline to deliver them, wait until inspiration comes to work on those. If you work on related tasks, the inspiration for less inspiring tasks can be provoked. Check out this episode of SchiShow, it really describes well my vision on this topic: youtube.com/watch?v=FDPJTo-gNUI
The second important thing I try to force myself to do is to stay lean. I try to lay down the main vision and principles/values of the project. Create a good framework to prioritize the tasks based on that.
Then I try to define the requirements for the application. If anything doesn't match the main goal, the main vision, the principles/values of the project, it will go on the backburner. Deliver the high-value items first, the rest can wait for post-MVP. Repeat.
All the best with your projects Sagar, you got this!
Software engineer with 4+ years of experience in building products for numerous domains like fin-tech, real estate, video streaming, retail, and now e-commerce.
That's awesome Man 👨 !!
I want to do the same thing but failed to do so because I have an unexpected requirement that is not fulfilled over the deadline.
Could you please share with me "What process are you following for building any kind of apps from scratch?"
Thanks in advance 😊
Unexpected requirements are unfortunately pretty common!
The first important thing is inspiration. I usually am the most productive when I work on what inspires me at the moment. It is not possible every time, some tasks are going to be required and not inspiring, but if you have some flexibility on the timeline to deliver them, wait until inspiration comes to work on those. If you work on related tasks, the inspiration for less inspiring tasks can be provoked. Check out this episode of SchiShow, it really describes well my vision on this topic: youtube.com/watch?v=FDPJTo-gNUI
The second important thing I try to force myself to do is to stay lean. I try to lay down the main vision and principles/values of the project. Create a good framework to prioritize the tasks based on that.
Then I try to define the requirements for the application. If anything doesn't match the main goal, the main vision, the principles/values of the project, it will go on the backburner. Deliver the high-value items first, the rest can wait for post-MVP. Repeat.
All the best with your projects Sagar, you got this!
Thanks for sharing your experience of build things. I'll try to implement the same thing in my life.