Benutzer:Andreas Plank/Design-Types: Unterschied zwischen den Versionen

Aus Open Source Ecology - Germany
Zur Navigation springen Zur Suche springen
(translate)
(Diese Seite wurde zum Übersetzen freigegeben)
Zeile 1: Zeile 1:
 
<languages/>
 
<languages/>
== <translate>Explaining the dimensions</translate> ==
+
== <translate><!--T:1--> Explaining the dimensions</translate> ==
  
 
{| class="vertical-align-top" style="border-collapse: collapse;"
 
{| class="vertical-align-top" style="border-collapse: collapse;"
|+ <translate>Software Design-Types after http://design-types.net</translate>
+
|+ <translate><!--T:2--> Software Design-Types after http://design-types.net</translate>
 
|-
 
|-
| style="background-color:#d1fedd;width:350px;" | <translate>'''Simple''' means:
+
| style="background-color:#d1fedd;width:350px;" | <translate><!--T:3-->
 +
'''Simple''' means:
 
* to keep code simple for better understandability
 
* to keep code simple for better understandability
 
* to omit unnecessary things (lower risk; fewer bugs)
 
* to omit unnecessary things (lower risk; fewer bugs)
Zeile 12: Zeile 13:
 
* etc.
 
* etc.
 
</translate>
 
</translate>
| <br/><br/><br/><big><translate>VS.</translate></big>  
+
| <br/><br/><br/><big><translate><!--T:4--> VS.</translate></big>  
| style="background-color:#d1fedd;width:350px;" | <translate>'''Powerful''' means:
+
| style="background-color:#d1fedd;width:350px;" | <translate><!--T:5-->
 +
'''Powerful''' means:
 
* to build powerful and generalized solutions
 
* to build powerful and generalized solutions
 
* to have flexibility/extensibility by foresighted design
 
* to have flexibility/extensibility by foresighted design
Zeile 21: Zeile 23:
 
</translate>
 
</translate>
 
|-
 
|-
| style="background-color:#dce3f3;width:350px;" | <translate>'''Abstract''' means:
+
| style="background-color:#dce3f3;width:350px;" | <translate><!--T:6-->
 +
'''Abstract''' means:
 
* to think in concepts and abstractions
 
* to think in concepts and abstractions
 
* to locus on the big picture and component interactions
 
* to locus on the big picture and component interactions
Zeile 28: Zeile 31:
 
* etc.
 
* etc.
 
</translate>
 
</translate>
| <br/><br/><br/><big><translate>VS.</translate></big>
+
| <br/><br/><br/><big><translate><!--T:7--> VS.</translate></big>
| style="background-color:#dce3f3;width:350px;" | <translate>'''Concrete''' means:
+
| style="background-color:#dce3f3;width:350px;" | <translate><!--T:8-->
 +
'''Concrete''' means:
 
* to think in code or simultaneously transfer ideas into code immediately
 
* to think in code or simultaneously transfer ideas into code immediately
 
* to optimize algorithms for better performance
 
* to optimize algorithms for better performance
Zeile 36: Zeile 40:
 
</translate>
 
</translate>
 
|-
 
|-
| style="background-color:#fee6da;width:350px;" | <translate>'''Pragmatic''' means:
+
| style="background-color:#fee6da;width:350px;" | <translate><!--T:9-->
 +
'''Pragmatic''' means:
 
* to fulfill requirements asap
 
* to fulfill requirements asap
 
* to focus on customer needs to guarantee a value
 
* to focus on customer needs to guarantee a value
Zeile 43: Zeile 48:
 
* etc.
 
* etc.
 
</translate>
 
</translate>
| <br/><br/><br/><big><translate>VS.</translate></big>
+
| <br/><br/><br/><big><translate><!--T:10--> VS.</translate></big>
| style="background-color:#fee6da;width:350px;" | <translate>'''Idealistic''' means:
+
| style="background-color:#fee6da;width:350px;" | <translate><!--T:11-->
 +
'''Idealistic''' means:
 
* to make things right—not only 80%
 
* to make things right—not only 80%
 
* to consider all aspects not only functional ones
 
* to consider all aspects not only functional ones
Zeile 52: Zeile 58:
 
</translate>
 
</translate>
 
|-
 
|-
| style="background-color:#fefacd;width:350px;" | <translate>'''Robust''' means:
+
| style="background-color:#fefacd;width:350px;" | <translate><!--T:12-->
 +
'''Robust''' means:
 
* to protect applications against risks and potential bugs
 
* to protect applications against risks and potential bugs
 
* to define and adhere to standards
 
* to define and adhere to standards
Zeile 59: Zeile 66:
 
* etc.
 
* etc.
 
</translate>
 
</translate>
| <br/><br/><br/><big><translate>VS.</translate></big>
+
| <br/><br/><br/><big><translate><!--T:13--> VS.</translate></big>
| style="background-color:#fefacd;width:350px;" | <translate>'''Technologic''' means:
+
| style="background-color:#fefacd;width:350px;" | <translate><!--T:14-->
 +
'''Technologic''' means:
 
* to use new. modern and more productive technologies and to get rid or legacy
 
* to use new. modern and more productive technologies and to get rid or legacy
 
* to evolve with technology to be more competitive
 
* to evolve with technology to be more competitive

Version vom 10. September 2018, 11:10 Uhr

Sprachen:
Deutsch • ‎English

Explaining the dimensions

Software Design-Types after http://design-types.net
Simple means:
  • to keep code simple for better understandability
  • to omit unnecessary things (lower risk; fewer bugs)
  • to reduce complexity
  • to prefer explicit solutions instead of implicit ones
  • etc.



VS.
Powerful means:
  • to build powerful and generalized solutions
  • to have flexibility/extensibility by foresighted design
  • to have configurable solutions
  • to master complexity
  • etc.
Abstract means:
  • to think in concepts and abstractions
  • to locus on the big picture and component interactions
  • to know all potential consequences ol a change -
  • to build models otttie real world
  • etc.



VS.
Concrete means:
  • to think in code or simultaneously transfer ideas into code immediately
  • to optimize algorithms for better performance
  • to understand systems by reading the code
  • etc.
Pragmatic means:
  • to fulfill requirements asap
  • to focus on customer needs to guarantee a value
  • to omit unnecessary things
  • to bring others down to earth
  • etc.



VS.
Idealistic means:
  • to make things right—not only 80%
  • to consider all aspects not only functional ones
  • to know that everything has its right place
  • not to misuse existing concepts, APls, etc.
  • etc.
Robust means:
  • to protect applications against risks and potential bugs
  • to define and adhere to standards
  • to avoid too much magic and complexity to reduce risks
  • to use proven solutions which stood the test of time
  • etc.



VS.
Technologic means:
  • to use new. modern and more productive technologies and to get rid or legacy
  • to evolve with technology to be more competitive
  • to broaden your personal horizon
  • etc.