design - How to keep my code simple? -


- edit -

I believe this is a valid question with multiple answers (As defined). It is not discussed and there is no survey. Apart from this, this question is not clearly rational because none of the respondents still argue with each other.

- Original Text -

Wonderful! I do the software for almost 15 years and I still do not know what I am doing :)

Seriously, I still struggle with fundamentals: / P>

  • Dangerous innovation vs. tedious good old stuff
  • Li> Enjoy the freedom of working vs team power vs. alone
  • But the worst thing is that the code complexity goes to get my code evil even after a few weeks Ud bites. I work hard on keeping it simple, readable, maintained, elegant, beautiful, united, loose coupled, simple straightforward effect. But all this effort goes down the drain!

    Do not think of me wrong, most of the people, by my standards, my code is very good. I mean that it is flexible, more or less unit-tested, and what is needed to do it though, it is far from simple.

    Every change requires sufficient refactoring. If another person opens his code with the intention of adding a feature then he will have to do something stupid. There is no way he will be able to correct it, even though he was a genius, even though he was unfamiliar with his own coding codebase. Why, why does this happen to God?

let me know your pain , Find friends The struggle for simplicity in complex systems is the struggle of software engineering. If you have rejected it, then you are probably not working on difficult engineering problems and hard work does not always mean complicated, it may be possible to "apply the sky to fall from tomorrow to tomorrow". is.

On simplicity ... TDD is well described, fully agree that TDD is a move that should be done to keep the code in mind and not anymore. Reactor often mentioned fully agreed.

Simplicity versus complexity and work alone ... do not work on shipping codes alone. Review the code in each investigation, and encourage code reviewers to rack you on the charity, keeping it on track to make you the right pact and balance. Talk to someone about your code at least once a day. Rotate the reviewer My job is more clear and better with a partner. They do not care how green they are. Indeed, greenery is better to ensure clear code.

On the job alone ... The work alone is the place in R & D, and the code has been sent the best, lonely shepherd projects make good stuff that is terrible pain to maintain. Work alone alone reinforces a month or two and maintains the code by humans and some giant is necessary to roughly recover. This is really painful if you hit that month or two when you send cowboy codes.

EDIT: In the broad side, I found useful in providing various ways to create super clear codes on domain disk design. DDD is not applicable to every problem.

If you are responding to the equilibrium between simplicity and over-engineering ... well, I do not even know what to do again. I think I will get bored and get the second row of work.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -