I saw how I did it, and I was wondering if other people work like this:
What I usually do when I run into a software development problem is that I write down the “perfect” solution without considering feasibility or any other consideration. Then I clean it from top to bottom until I find a solution.
Is this methodology popular and has a catchy name? If so, I would like to know so that I can learn more about this.
Building software in terms of experience is the best way to go.
, , , , , .
, , - , , , .
, .:)
/ ( , Google) "tech-no-filter", > , . , , . , , , , , , , . , , . , , . !
, , . , . - / , .
( ) . , - . , , ( , ), , , .
, , , , . , , , , . , (.. ), .
, , . , . . (, ). , .
/ - - , , .