|
|
|
|
|
by tdr
5128 days ago
|
|
If you work in a small team, especially a startup, knowing what’s going on and how your product works is valuable also to a non-technical business co-founder Couldn't agree more! (especially for product people) Can you give more specific details about how it helps you/the team? (no sarcasm here, I'm genuinely interested to understand this form the marketers' perspective) |
|
If you are working remotely, you want to be able to see the latest development version and run it locally, not just the latest alpha push. In the real gritty details, I just had to update Maven on my local machine and fix a Github conflict, and had to ask for help figuring out where the missing components were and how to fix the error messages. If someone has to take an hour helping me get this done, it is unnecessary overhead. I still almost broke things in vim though, but know what I have to learn.
More generally, a technical product understanding just helps in communication. If the tech lead makes the decision to refactor the code, which leads to delays affecting the business, it's good to know why.