Skip to main content
Commonmark migration
Source Link

###Too complex.

Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

###Let's take the most easy and still effective step (pareto principle).

Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.

###Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

###Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.

Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

###Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

###Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementationsimple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.

###Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

###Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.

###Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

###Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.

Source Link
miroxlav
  • 513
  • 3
  • 10

###Too complex.

Most of suggestions like this one are easy to reject because overly complex implementation was proposed for them.

###Let's take the most easy and still effective step (pareto principle).

There is still suggestion of simple implementation where 20% effort can solve 80% of cases.

Instead of all-purpose suggestion system we actually badly need to stop the Stack Overflow from drawing energy from its own technology-oriented children and help them to stand on their own legs. The complete list as of Jan 2015: raspberry-pi, drupal, joomla, windows phone, blender, magento, emacs, wordpress, tex. Nothing more.