3 ms·

Application shall be usable without any network. It is mainly about creating new tools, some of them currently existing as spreadsheet. Update/fixing small bu

• Jugurtha 6y ago
  How have the current tools that need revamping been updated so far? Even if the "tools" in question are the spreadsheets, how do they update and share them? How many users will you have to deploy that for? I'm asking these questions because you'll have a payload that has to find its way to disconnected environments. There will be updates that need to be rolled out as well, and you want to think about that. I am a newly hired engineer, how do you provision my workstation, and how do you make the tool available to me? A week goes by, and the tool crashes and stops working for me, how do I get that to you? You get my bug issue, where do you do development, and where do you push your code and collaborate with your colleagues and get my opinion? You fix the bug, how do you make the new version available to me, and I imagine to others as well? Will you bring a thumb drive given that my workstation is disconnected? Does that thumb drive do the rounds to others? How many people will use it, and how do we ensure the payload we're using is the same you built? Will you be shipping the whole thing or do you have to do incremental diffs? Have you gathered the engineers you're building for and what were their thoughts on a workflow that would make sense for them and not get in their way?