Skip to content

Instantly share code, notes, and snippets.

View aydinugur's full-sized avatar
🏋️‍♂️
Trying

aydinugur

🏋️‍♂️
Trying
View GitHub Profile
@cekici
cekici / yuksel.js
Last active August 5, 2022 12:36
Yüksel'in buluşma algoritması
function getYukselsResponse(statics, bulusmaAyarlayan, bulusmaYeri, event, cokIsrar) {
return isBulusmayiAyarlayanYuksel(statics, bulusmayiAyarlayan) ||
isBulusmaYeriYukseleUyuyor(statics, bulusmaYeri) ||
isEventYukseleUyuyor(statics, event) ||
cokIsrar;
}
function isBulusmayiAyarlayanYuksel(statics, bulusmayiAyarlayan) {
return bulusmayiAyarlayan === statics.people.YUKSEL;
@wojteklu
wojteklu / clean_code.md
Last active November 17, 2024 20:34
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