Skip to content

Instantly share code, notes, and snippets.

View KvRae's full-sized avatar
👀
Focusing

Karam Mannai KvRae

👀
Focusing
View GitHub Profile
ADB = YOUR_ADB_PATH
PACKAGE_NAME = YOUR_PACKAGE_NAME
MAIN_ACTIVITY = .entry.MainActivity
clean:
./gradlew clean
build:
./gradlew build
@antonarhipov
antonarhipov / gist:2e214d122147cfc24366f1bef666c500
Created October 24, 2024 11:37
Sonic Pi Dark House program
##| Generated Sonic Pi code for Dark House:
use_bpm 120
live_loop :atmos_pad do
use_synth :dark_ambience
play chord(:C3, :minor), release: 8, amp: 0.4
sleep 8
end

Kotlin clean code and best practices

Clean Code Rules

Our main aim is to have a clean code, avoid common silly mistakes and reduce the load on engineers during PR reviews. This is a team effort and If anyone has something that’s generally applicable, let’s talk and decide whether it should be baked into our style guide— so everyone can benefit from it

The bad code creates a lot of distractions. It causes developers to waste time and energy navigating through functions, classes, and files, and pouring over code trying to understand it.

Working on a project where developers care about clean code makes it easy to understand its virtues; the developer can read the code from top to bottom in one go and clearly understand what it does. It makes code manageable and maintainable in the long term, isolating changes and increasing the efficiency of the team.