4 ms·

Well, all I can say is that I personally often find the full stack interesting when debugging exceptions, and might still try and implement passing stack info i

Well, all I can say is that I personally often find the full stack interesting when debugging exceptions, and might still try and implement passing stack info in my monolithic system (in spite of this discussion which might have been above my pay-grade honestly). In case it breaches some important CS principle that I don't fully grasp yet then it will surely come back and bite me - which has happened before ... :) . Anyway, thanks for your time.

hvidgaard 9y ago
You're welcome. I juggle those concepts and requirements daily, and I value explaining it to the developers. The "why are we doing it this way" is really important for their job satisfaction, and it happens that they have an aspect I didn't consider, or a better solution.
edem 9y ago
Your intuition is right. As a programmer your primary job is in most cases not mental masturbation and/or adhering to CS principles but shipping working software. We are all bound by the 80/20 rule and our job is do decide when to adhere to the principles and when to cut corners. In practice no one will care that you implemented a 100% pure microservice if you miss an important deadline, your company loses a $300M deal and your team ends up laid off. I'm not a business person, but a programmer. I also like writing beautiful code but we have to know the tradeoffs. If the tradeoff of having a beautiful service vs a nice service is 3 weeks of additional keyboard bashing it is not worth it. I once had a colleague who insisted on implementing all REST endpoints between microservices using HATEOAS/HAL because it will enable the consumption of such endpoints by programs and generated code. He spent a month refactoring our services and we ended up never using that feature, but modifying endpoints still carry that overhead he added.

4 ms·

Well, all I can say is that I personally often find the full stack interesting when debugging exceptions, and might still try and implement passing stack info i

by stareatgoats 9y ago

hvidgaard 9y ago
You're welcome. I juggle those concepts and requirements daily, and I value explaining it to the developers. The "why are we doing it this way" is really important for their job satisfaction, and it happens that they have an aspect I didn't consider, or a better solution.
edem 9y ago
Your intuition is right. As a programmer your primary job is in most cases not mental masturbation and/or adhering to CS principles but shipping working software. We are all bound by the 80/20 rule and our job is do decide when to adhere to the principles and when to cut corners. In practice no one will care that you implemented a 100% pure microservice if you miss an important deadline, your company loses a $300M deal and your team ends up laid off. I'm not a business person, but a programmer. I also like writing beautiful code but we have to know the tradeoffs. If the tradeoff of having a beautiful service vs a nice service is 3 weeks of additional keyboard bashing it is not worth it. I once had a colleague who insisted on implementing all REST endpoints between microservices using HATEOAS/HAL because it will enable the consumption of such endpoints by programs and generated code. He spent a month refactoring our services and we ended up never using that feature, but modifying endpoints still carry that overhead he added.