4 ms·

Thanks for the invitation and your engagement. I do disagree with some of your opinions, but I find them interesting and valuable. I've definitely changed my m

Thanks for the invitation and your engagement. I do disagree with some of your opinions, but I find them interesting and valuable. I've definitely changed my mind about things before, so you might be right on all of these counts - but our experiences might differ enough to have different opinions. > Here's a hint at the fundamental disconnect. Services shouldn't talk to other services. Period. Not if that can be avoided. I agree in principle, but I've not been able to see this followed in a large sprawling engineering organisation. I will definitely join the slack once I have some distance from this. To be honest, I didn't expect this to be posted on HN at this point in the project - and HN can be somewhat merciless :) Thanks again for engaging with me. You've inspired me to do some changes - especially in how I position the value prop and I learned a lot from reading your references. Much appreciated :)

hmeh 3y ago
I too appreciate your engagement. I understand that HN can be merciless, and I do try to be direct, which can sometimes be felt as merciless or harsh. I'm trying to give my unadulterated perspective because I care about the outcomes for the industry as a whole. And yes, I can imagine it was quite a shock to get this much unexpected feedback all at once. You handled it well, from what I've seen. > I agree in principle, but I've not been able to see this followed in a large sprawling engineering organisation. Ours isn't large and sprawling (only around 15 devs) but we managed to build and maintain ~100 back end services and ~20 front end web applications and we're only speeding up as we go. It's possible, but it takes effort and it requires doing things that go against "best practices". [1] It also requires significant cultural and managerial work (see Lean, Steven Spear's work, etc.). Good luck in your product and learning journey. Hopefully we can connect again down the road. Cheers. [1] https://github.com/aaronjensen/software-development/blob/master/best-practices.md https://github.com/aaronjensen/software-development/blob/mas...
- lunarcave 3y ago
  > I understand that HN can be merciless, and I do try to be direct, which can sometimes be felt as merciless or harsh. I definitely didn't see your engagement this way. I believe you entered the conversation and held your ground with good intentions.

hmeh 3y ago

I too appreciate your engagement. I understand that HN can be merciless, and I do try to be direct, which can sometimes be felt as merciless or harsh. I'm trying to give my unadulterated perspective because I care about the outcomes for the industry as a whole. And yes, I can imagine it was quite a shock to get this much unexpected feedback all at once. You handled it well, from what I've seen. > I agree in principle, but I've not been able to see this followed in a large sprawling engineering organisation. Ours isn't large and sprawling (only around 15 devs) but we managed to build and maintain ~100 back end services and ~20 front end web applications and we're only speeding up as we go. It's possible, but it takes effort and it requires doing things that go against "best practices". [1] It also requires significant cultural and managerial work (see Lean, Steven Spear's work, etc.). Good luck in your product and learning journey. Hopefully we can connect again down the road. Cheers. [1] https://github.com/aaronjensen/software-development/blob/master/best-practices.md https://github.com/aaronjensen/software-development/blob/mas...

lunarcave 3y ago
> I understand that HN can be merciless, and I do try to be direct, which can sometimes be felt as merciless or harsh. I definitely didn't see your engagement this way. I believe you entered the conversation and held your ground with good intentions.