Hi Daniel, my intention was not to say that you should avoid abstraction. It is that you should be aware of its cost and to know where, when and how much to apply it. Often times articles touch only on the positive side of things, which can trick entry level engineers into thinking that a particular pattern, technology or architecture is without cost and should be applied everywhere and always.
One example would be the JWT token, which could often times be replaced with a basic bearer token, depending on your use case.
Giovanni gave a good heuristic, go with the Pareto's principle, and never forget that your job as an engineer is to provide value to the business. To do so, it helps to reduce cost of development to a reasonable minimum, but of course no lower than that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Daniel, my intention was not to say that you should avoid abstraction. It is that you should be aware of its cost and to know where, when and how much to apply it. Often times articles touch only on the positive side of things, which can trick entry level engineers into thinking that a particular pattern, technology or architecture is without cost and should be applied everywhere and always.
One example would be the JWT token, which could often times be replaced with a basic bearer token, depending on your use case.
Giovanni gave a good heuristic, go with the Pareto's principle, and never forget that your job as an engineer is to provide value to the business. To do so, it helps to reduce cost of development to a reasonable minimum, but of course no lower than that.