Skip to content

Instantly share code, notes, and snippets.

View anirban99's full-sized avatar

Anirban anirban99

View GitHub Profile
@cnicodeme
cnicodeme / fixes.md
Last active May 6, 2026 07:14
List of 5,000 Most Frequently Used Domain Name Prefixes and Suffixes - Ordered By Length
@tykurtz
tykurtz / grokking_to_leetcode.md
Last active May 13, 2026 14:48
Grokking the coding interview equivalent leetcode problems

GROKKING NOTES

I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.

So below I made a list of leetcode problems that are as close to grokking problems as possible.

Pattern: Sliding Window

Interview Questions

Kotlin

Q1: What is a primary constructor in Kotlin? ☆☆

Answer: The primary constructor is part of the class header. Unlike Java, you don't need to declare a constructor in the body of the class. Here's an example:

/*
* This snippet is DEPRECATED.
*
* To check the updated version, open the following project:
*
* https://github.com/hexagontk/kotlin_walk_through
*/
#!/usr/bin/env kotlin
@ahmedhamdy2121
ahmedhamdy2121 / GIT simple commands
Last active November 25, 2022 11:47
GIT simple commands
Copyrights (c) 2014 - 2019 Ahmed Hamdy
To pull before push:
> git fetch
> git stash # NOTE: This will backup your local changes
> git pull # git pull origin master
> git stash apply # NOTE: This will restore your local changes
If the remote branch has many changes, or have been deleted and recreated:
> git pull --rebase
@chitchcock
chitchcock / 20111011_SteveYeggeGooglePlatformRant.md
Created October 12, 2011 15:53
Stevey's Google Platforms Rant

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real