HN user

TheLudd

38 karma
Posts5
Comments18
View on HN

You said:

No, we pay less for it. But there's much higher demand so overall use goes up.

This is economics 101, not a paradox.

To clarify how I read you: "If the price goes down, more people will want to buy, hence more units are sold"

The paradox is that _one_ person, or entity, pays more as the price goes down.

Right. That is not a paradox as stated.

The paradox would be:

  * a TV used to be really expensive. So a home just had one

  * over time TVs become half the price.

  * now a home has 3 TVs, i.e paying 150% of what they initially payed.

Should the paradox not be that we PAY more for it? Or, if some process is made more effective, i.e. takes shorter time, we spend more time in that process.

One interesting factor that I rarely see discussed is this: Let's say a DevOps person does some improvement to internal tooling and a task that devs had to oversee manually now is automated. Every dev spent about 2 hours per week doing this task and now they don't have to anymore. Now, have we saved 2 hours of salary per dev per week?

Not sure. Because it totally depends on what they do instead. Are they utilizing two hours more every week now doing meaningful work? Or are they just taking things a bit more easy? Very hard to determine and it just makes it harder to reason about the costs and wins in these cases.

Modules that are part of your build, tests and npm scripts should be installed locally so that any contributor can run npm install/yarn and the develop your project without any other need and they will also get the correct version of the module.

Global installs are for modules that are outside your projects dev cycle. With that in mind, a module such as nodemon can be installed both globally and locally. It depends on the use case.

Open-Sourced Logos 10 years ago

I could not throw anything together of this quality. If I were to create a product by myself, using one of the ones available would certainly be a step up.

I cannot respect a TDD guide that is dependent on your editor. Doing tdd is about code structure and implementations decisions imho. If you need to check some box in a dialog window of a certain editor in order to run your tests, your test runner isn't good enough.