4 ms·
So you're taking code that you haven't validated locally to see what resources it uses, you're putting this up on the cloud to test it, then you are immediately
by jjk166 6y ago
So you're taking code that you haven't validated locally to see what resources it uses, you're putting this up on the cloud to test it, then you are immediately going to the middle of nowhere without your laptop/phone/etc, and you can't arrange for a coworker or friend to pull the plug for you if something goes wrong?
- patrickaljord 6y ago> and you can't arrange for a coworker or friend to pull the plug for you if something goes wrong? This is HN, many of us are solo founders with no coworkers or employees. Also how could a "friend" pull the plug? If it was a physical server running in your house maybe, otherwise you can't really give them access to your AWS account with all your private clients data in there.
- jjk166 6y agoIf you don't have anybody who can monitor your test, and you're not monitoring your test, why are you doing a test? As for having a non-employee pull the plug, set up an IAM user with permission to access the test instance
- WrtCdEvrydy 6y ago> you're not monitoring your test, why are you doing a test? Agile. Bringing you bankruptcy at the speed of cloud.
- jschwartzi 6y agoIf I'm the only developer on a project and I really need to get to market I might do just that. I sometimes do day hikes on weeknights so this is actually a likely scenario for me.
- jjk166 6y agoDo you go hiking alone without your phone? That seems dangerous. And why would you start a test if you won't be there to see the results of the test? Seems more sensible to either leave after you've run the test or wait to do so until you get back.
- jschwartzi 6y agoYeah pretty frequently. It's not dangerous at all. Maybe if I was climbing alone it would be.
- jschwartzi 6y agoIf a test is going to take more than an hour then I'm not going to sit around after work waiting for it to finish.