22 min
13 Be Lazy (strategically) Blissful Programmer
-
- Teknologi
A lot of times when you are working with other teams, you would be given an impossible deadline. In my opinion, 9 out of 10 times it is out of no where. Impossible deadlines makes sense for a doctor where patient can die, or may be a fire fighter, or paramedic or a stock trader, but for a software engineer? Why?
We all know software development should be strategic and not tactical. You should take a step back and ask the why before jumping on coding. A working code is just the start. If you don't do due diligence and jump on building softwares, most of the times it will not be useful and thrown away since you didn't strategically asked the right question to understand the whys. Remember that you are the expert in building softwares not the sales team or the client. Its your responsibility to inquire and poke and sit down with them and weigh in all the alternative and ways. After doing this heavy brainstorming, go back build MVP and then come back, let them test and repeat.
In this podcast I will discuss the same along with examples and what should you do in these scenarios.
---
Support this podcast: https://podcasters.spotify.com/pod/show/blissful-programmer/support
A lot of times when you are working with other teams, you would be given an impossible deadline. In my opinion, 9 out of 10 times it is out of no where. Impossible deadlines makes sense for a doctor where patient can die, or may be a fire fighter, or paramedic or a stock trader, but for a software engineer? Why?
We all know software development should be strategic and not tactical. You should take a step back and ask the why before jumping on coding. A working code is just the start. If you don't do due diligence and jump on building softwares, most of the times it will not be useful and thrown away since you didn't strategically asked the right question to understand the whys. Remember that you are the expert in building softwares not the sales team or the client. Its your responsibility to inquire and poke and sit down with them and weigh in all the alternative and ways. After doing this heavy brainstorming, go back build MVP and then come back, let them test and repeat.
In this podcast I will discuss the same along with examples and what should you do in these scenarios.
---
Support this podcast: https://podcasters.spotify.com/pod/show/blissful-programmer/support
22 min