I'm not sure I fully understand the point you're making on the 80-20 rule. I think it can be helpful guide that prevents premature optimization and over-engineering in general. It can guide devs how to prioritize changes to their software projects. Apologies if I misunderstood your point though.
No we are all correct. But i was trying to say was the fact that senior engineers knows alot of third party and how they can use shortcut to achieve a goal, in the long run, the third party got which might be 80%, got their negative issues. Its best they cncentrate on bulding their own API with junior teams.
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.
I'm not sure I fully understand the point you're making on the 80-20 rule. I think it can be helpful guide that prevents premature optimization and over-engineering in general. It can guide devs how to prioritize changes to their software projects. Apologies if I misunderstood your point though.
No we are all correct. But i was trying to say was the fact that senior engineers knows alot of third party and how they can use shortcut to achieve a goal, in the long run, the third party got which might be 80%, got their negative issues. Its best they cncentrate on bulding their own API with junior teams.