How to get rid of the habit of complicating the task?

Alexander Sinitsyn2016-11-15 16:51:25

Programming

Alexander Sinitsyn, 2016-11-15 16:51:25

There is a habit to complicate the task more than it is necessary. How to develop a sense of the border on which it is time to stop?
For example, there were two text fields in the table Point_1, Point_2, then the thought went ... it seems like the fields need dates ... why not separate them into a separate table with the fields ID, Text, Date ... but the point has Value value... The value can be of different units of measure... there can be several of them... You need a reference book of measurement units... maybe kg and grams you need to bring them... then you realize that a little more will come. instead of going back to the text fields in which the user can write whatever he needs )))

Answer the question

In order to leave comments, you need to log in

11 answer(s)

romy4, 2016-11-15
@a_u_sinitsin

This process is called identifying milestones. You first determine the MVP (minimal value product) - that is, the level of completeness (without bells and whistles) at which you can benefit and then you are already building based on the MVP

Saboteur, 2016-11-15
@saboteur_kiev

You have too much free time, so you don't know what to do with it.

xmoonlight, 2016-11-15
@xmoonlight

Divide into basic and advanced functionality.
Basic - this is the minimum without which it is impossible to use the system.
Extended - something that can be "hung" after starting the main one.

Rou1997, 2016-11-15
@Rou1997

Too soft deadlines? Find a part-time job, second, third, and so on until they become tough! And get richer too!
Do not want to get rich, do you consider yourself wealthy enough? Contact, say, Daimler-Benz, or rather Bugatti, etc., they will quickly convince you!

Alexey Nikolaev, 2016-11-16
@Heian

Master the methodology "hu*k-hu*k and into production". Then you improve. It's better to underdo it first and get a portion of edits than to do too much and then cut out the unnecessary.

Anatoly, 2016-11-24
@Skit25

Yesterday I read an article.
A sign of a qualified specialist, his ability to solve a problem is simple.
Study and study again. Above TDD is advised, also a topic! In fact, I wrote the code and rejoiced. After 15 minutes, the code lost three times its weight. Let it be so! And ran the tests again.

Andrew, 2016-11-29
@iCoderXXI

Sometimes you need to make it harder. Imagine that you are not a contractor, but a customer. Ask yourself a question - would you pay for this increased complexity, extended terms, etc.? Are they really needed, or can you do without them. At the end of the day, we all make products and tools that should make people's lives easier, preferably on the shortest possible time and budget with the highest possible quality and functionality. Finding a balance in this whole story is the goal.

FoxInSox, 2016-11-15
@FoxInSox

Do not complicate, everything is ok.

@coodan, 2017-01-10
_

I think study. In the sense that while there is time, try this way and that. Look at the pitfalls. Find the best solution for you. And then play it, without hesitation, on the machine.
There is such a thing here - an elegant solution may seem too complicated if you do not mature to it. And it seems simple to have such a rake that it will be easier to rewrite everything later than to fix it. If you don't try, you won't mature. Well, for example, with the same normalization of tables. Yes, there will be many. It seems to be difficult. But the data will be intact. Then it will be easier.
One thing is not worth doing - all the time rewriting the same thing when it is really urgently needed.

Dmitry, 2016-11-24
@deemytch

The magic word TDD.
Strength and cunning are spent on writing (and debugging!) tests. Exactly what is needed to write the code is left to green the tests.