Skip to content

Instantly share code, notes, and snippets.

View mopp's full-sized avatar
💜
Power is power

mopp mopp

💜
Power is power
View GitHub Profile
@taiyow
taiyow / erlang-knowledge.md
Last active December 3, 2019 01:08
Erlang Knowledge

Erlang/OTP 関連で読んだ/観た資料のリスト

何を読んで何を知ってどう思ったかをすぐに忘れてしまうので、資料を書いていく場所。

方針は:

  • 読んだ/観た順番に先頭に追加していく
  • 一般に公開されていない資料については記載しない
  • どんな資料かを1行だけ書き、資料の目的/想定対象がわかれば記載
  • 自分が新しく知った点を書く
@wojteklu
wojteklu / clean_code.md
Last active May 10, 2024 06:50
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

@Nkzn
Nkzn / gist:3026624
Created July 1, 2012 03:00
if文の良くないネストとか
/*
* 例1
*/
if(hoge != null) {
hogeList.add(hoge);
}
// 例1の全然アリな例①
if(hoge != null)
hogeList.add(hoge);