|
- What should take precedence: YAGNI or Good Design?
At which point should YAGNI take precedence against good coding practices and vice versa? I'm working on a project at work and want to slowly introduce good code standards to my co-workers (curren
- SOLID principles vs YAGNI - Software Engineering Stack Exchange
When do the SOLID principles become YAGNI? As programmers we make trade-offs all the time, between complexity, maintainability, time to build and so forth Amongst others, two of the smartest guid
- YAGNI principle put to practice - Software Engineering Stack Exchange
The good thing about YAGNI is the fact that you posted this question It's a great subject to make a decision on with the team Then it's a recorded decision that you do support multi language or you don't It's in general not a decision you should make when you are implementing the texts It's a decision you make in your meetings
- single responsibility - Is there a conflict between YAGNI and SRP . . .
I often leaned upon YAGNI to make my code simpler by removing needless modularization Conflict between SRP and YAGNI: We were having a work flow implemented in the system And there was a need to collect data about the usage of Work Flow We needed to find out about the percentage distribution of parameters used in the work flow
- What hurts maintainability? - Software Engineering Stack Exchange
YAGNI (what's called "waste" in the Lean vocabulary) will make a system much harder to refactor and maintain as a lot of time will be wasted (pun intended) on maintaining code and backwards compatibility for features that aren't even used
- C# encapsulate field is a violation of YAGNI
YAGNI isnt a principle, its an excuse for not doing stuff Here we can use the syntactic sugar public DataAccess Service { get; set; } and its cost us 10 characters worth of typing to get the benefits of a property over a field Maybe in the old days you could get away with fields, but so much stuff expects properties now, You are going to need it Get into the habit of doing stuff in full and
- object oriented - Do I need to create an interface for every service . . .
YAGNI is a principle not taught to us in school so today is the first time i've come in contact with it I was also worried that if I use an interface in 1 place that I should use it everywhere for consistency
- Scrum team not following the YAGNI principle
That is why YAGNI is important-- you don't want to write code that can't be tested, and if the only purpose of the code is to support a feature that nobody is using, it is difficult to test It shouldn't be a judgment call I would suggest you get the team to agree on the unspoken requirement that you apparently missed and get it written down
|
|
|