5 ms·

Sure if you are doing embedded programming in C. How does one do this in web development though where there are hundreds of dependencies that get updated monthl

by cudgy 2y ago

Sure if you are doing embedded programming in C. How does one do this in web development though where there are hundreds of dependencies that get updated monthly and still add functionality and keep their job?

kragen 2y ago
Maybe switch to less frequently updated dependencies and rewrite the easy ones in-house?
- pdimitar 2y ago
  Yes, and I should overrule half the business decisions of the company while I am at it. Oh, and I'll push back on "we need the next feature next week" and I'll calmly respond "we need to do excellent engineering practices in this company". And everybody will clap and will listen to me, and I will get promoted. ...Get real, dude. Your comments come across a bit tone-deaf. I am glad you are in a privileged position but you seem to have fell for the filter bubble effect and are unaware to how most programmers out there have to work if they want to pay the bills.
  - ori_b 2y ago
    Yes, sometimes things are unfixably broken, and it's impossible to build anything good. For everything else, there's MasterCard.
    - pdimitar 2y ago
      Any golden MasterCards with $50M one-time limit you could offer for free? I can think of a few things to fix with those. RE: unfixably broken, well, not necessarily in concept but de facto you are sadly correct. Most people resist even the provably good changes.
    - klibertp 2y ago
      > For everything else, there's... ...the very definition of brokenness :D Not much of a (good) choice there...
    - inkyoto 2y ago
      > For everything else, there's MasterCard. I'm pretty sure that the original meme was «In God we trust; for everything else, there’s American Express» (with or without cocaine).
  - kragen 2y ago
    I know a lot of people have terrible jobs at profoundly dysfunctional companies. I've had those too. That situation doesn't improve unless you, as they say, have the serenity to accept the things you cannot change, the courage to change the things you can, and the wisdom to know the difference. Not everyone has a position where they have the autonomy to spend a lot of effort on paying down technical debt, but some people do, and almost every programmer has a little. I think it's important to keep in view both your personal incentive system (which your boss may be lying to you about) and the interests of the company.
    - pdimitar 2y ago
      The serenity in question boils down to "I'll never make enough money to live peacefully and being able to take a two years sabbatical so let's just accept I'll be on the hamster wheel for life and I can never do anything about it". No. I'll let my body wither and get spent before my spirit breaks. I refuse to just "accept" things. There's always something you can do. BTW is that not what HN usually preaches? "Change your job to a better one" and all that generic motivational drivel [that's severely disconnected from reality]? Not throwing shade at you here in particular, just being a bit snarky for a minute. :) RE: your final point, I lost the desire to keep view of both my personal and my company's incentive systems. Most "incentive systems" are basically "fall in line or GTFO". Before you ask, I am working super hard to change my bubble and get a bit closer to yours. To say it's not easy would be so understated so as to compare the description of a lightning hit on you and you enduring the said lightning hit. But as said above, I am never giving up. But... it's extremely difficult, man. Locality and your own marketing matter a lot, and when you have been focused on technical skills all your life and marketing is as foreign to you as are the musical notes of an alien civilization... it's difficult.
      - kragen 2y ago
        I can't recommend others follow my path. Some of the results have been pretty bad. Hopefully your path works out well. We all die in the end.
silver_silver 2y ago
The current state of web development is unfortunately a perfect example of this quality crisis. The tangle of dependencies either directly causes or quickly multiplies the inefficiency and fragility we’ve all come to expect from the web. The solution is unrealistic because it involves design choices which are either not trendy enough or precluded by the platform

by cudgy 2y ago

kragen 2y ago

Maybe switch to less frequently updated dependencies and rewrite the easy ones in-house?

pdimitar 2y ago
Yes, and I should overrule half the business decisions of the company while I am at it. Oh, and I'll push back on "we need the next feature next week" and I'll calmly respond "we need to do excellent engineering practices in this company". And everybody will clap and will listen to me, and I will get promoted. ...Get real, dude. Your comments come across a bit tone-deaf. I am glad you are in a privileged position but you seem to have fell for the filter bubble effect and are unaware to how most programmers out there have to work if they want to pay the bills.
- ori_b 2y ago
  Yes, sometimes things are unfixably broken, and it's impossible to build anything good. For everything else, there's MasterCard.
  - pdimitar 2y ago
    Any golden MasterCards with $50M one-time limit you could offer for free? I can think of a few things to fix with those. RE: unfixably broken, well, not necessarily in concept but de facto you are sadly correct. Most people resist even the provably good changes.
  - klibertp 2y ago
    > For everything else, there's... ...the very definition of brokenness :D Not much of a (good) choice there...
  - inkyoto 2y ago
    > For everything else, there's MasterCard. I'm pretty sure that the original meme was «In God we trust; for everything else, there’s American Express» (with or without cocaine).
- kragen 2y ago
  I know a lot of people have terrible jobs at profoundly dysfunctional companies. I've had those too. That situation doesn't improve unless you, as they say, have the serenity to accept the things you cannot change, the courage to change the things you can, and the wisdom to know the difference. Not everyone has a position where they have the autonomy to spend a lot of effort on paying down technical debt, but some people do, and almost every programmer has a little. I think it's important to keep in view both your personal incentive system (which your boss may be lying to you about) and the interests of the company.
  - pdimitar 2y ago
    The serenity in question boils down to "I'll never make enough money to live peacefully and being able to take a two years sabbatical so let's just accept I'll be on the hamster wheel for life and I can never do anything about it". No. I'll let my body wither and get spent before my spirit breaks. I refuse to just "accept" things. There's always something you can do. BTW is that not what HN usually preaches? "Change your job to a better one" and all that generic motivational drivel [that's severely disconnected from reality]? Not throwing shade at you here in particular, just being a bit snarky for a minute. :) RE: your final point, I lost the desire to keep view of both my personal and my company's incentive systems. Most "incentive systems" are basically "fall in line or GTFO". Before you ask, I am working super hard to change my bubble and get a bit closer to yours. To say it's not easy would be so understated so as to compare the description of a lightning hit on you and you enduring the said lightning hit. But as said above, I am never giving up. But... it's extremely difficult, man. Locality and your own marketing matter a lot, and when you have been focused on technical skills all your life and marketing is as foreign to you as are the musical notes of an alien civilization... it's difficult.
    - kragen 2y ago
      I can't recommend others follow my path. Some of the results have been pretty bad. Hopefully your path works out well. We all die in the end.

silver_silver 2y ago

The current state of web development is unfortunately a perfect example of this quality crisis. The tangle of dependencies either directly causes or quickly multiplies the inefficiency and fragility we’ve all come to expect from the web. The solution is unrealistic because it involves design choices which are either not trendy enough or precluded by the platform