anoviceuser

5 ms·

1. 1.▲
   by anoviceuser 6y ago

   Thanks Steve for sharing this. I am sorry to hear about your condition. I am sure as you survived Big C, you will survive the small C as well. Take care and thanks.
2. 2.▲
   by anoviceuser 6y ago

   Great work @dexterlang. Thanks for building it. I am already actively using it and really like it.
3. 3.▲
   by anoviceuser 6y ago

   Thanks @rails. Really appreciate the clarification.
4. 4.▲
   by anoviceuser 6y ago

   @1ba9115454, Really appreciate your inputs. Thanks.
5. 5.▲
   by anoviceuser 6y ago

   @javamantra, Thanks a lot for your elaborate inputs. These are valuable insights. Thanks.
6. 6.▲
   by anoviceuser 6y ago

   @rails, By "Make decisions easy to change later", do you mean, 1. Getting the Module structure of the system correct with well defined contracts between them so that they can be changed, updated independently of each other. Thank
7. 7.▲
   by anoviceuser 6y ago

   @maps7, Thanks for your inputs. Do you want to share any further insights about what factors you use to narrow down the choices about the correct ways? Similarly how do you go about managing the Constraints & Trade-offs - Do you change
8. 8.▲
   Ask HN: What Learnings can you share from Being a Software Architect

   7 points by anoviceuser 6y ago|10 comments
9. 9.▲
   by anoviceuser 7y ago

   I agree this is an awesome post and a really great example of how every Root Cause Analysis needs to be done. I am also impressed by their incident response.