davidbgk
/
larlet-fr-david
ウォッチ 1
スター 0
フォーク 0
コード リリース 0 アクティビティ
Repository with sources and generator of https://larlet.fr/david/ https://larlet.fr/david/
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
898 コミット
1 ブランチ
ツリー: 934bbf3a61
ブランチ タグ
${ item.name }
ブランチ ${ searchTerm } を作成
'934bbf3a61' から
${ noResults }
larlet-fr-david/david/stream/2018/03/17/index.md

index.md 1.2KB
Raw 通常表示 履歴

Add initial content
4年前
​
​
​
​
​
​
​
​
​
​
​
 123456789101112 
  1. title: Solution vs. clue

  2. lang: en

  3. 

  4. > That's when you have to watch out and resist the temptation to take code that *works* for code that's *good*. What you've found on Stack Overflow is - in all but the rarest cases - not a *solution* but rather a *clue*. It can certainly make for a great pointer, but it was *not* written with your exact problem / requirements / constraints /code base / application in mind. And sometimes, it might simply be a dirty hack.

  5. >

  6. > Embrace Stack Overflow as a good source of guidance for certain problems. But also take the time to thoroughly and honestly evaluate if you've found a real, solid solution.

  7. > 

  8. > <cite>*[Our Development Philosophy (1): Architecture, Design Patterns and Programming Principles](https://www.git-tower.com/blog/dev-philosophy-1)* ([cache](/david/cache/2483b6184d1a2e7c96c298db4bdf163b/))</cite>

  9. 

  10. Pretty well stated by the Tower team. Stack Overflow makes you find *leads* faster, but the solution is up-to-you and that’s part of the beauty of that job :-).

  11. 

  12. Make sure to check out the [second part too](https://www.git-tower.com/blog/dev-philosophy-2) ([cache](/david/cache/03f7d88efe4db61d7007bcf736aa789f/)), as writing code is only the first step of a long path.