Skip to content

Instantly share code, notes, and snippets.

View avgspacelover's full-sized avatar
💭
evolving

Siddharth avgspacelover

💭
evolving
View GitHub Profile
@avgspacelover
avgspacelover / weekend-dev-puzzles-list.md
Created September 10, 2022 17:16 — forked from amodm/weekend-dev-puzzles-list.md
List of all #WeekendDevPuzzles

Weekend Dev Puzzle

List

  • 2022-02-12: Limiting factor in playing an arcade style space shooter via sensors and a hooked up keyboard.
  • 2022-02-05: Does the time taken to count integers (that are less than a threshold) in an unordered array, remain the same, or vary?
  • 2022-01-29: Does splitting a service into microservices help or hurt the availability?
  • 2022-01-22: Can closures+lambdas be implemented irrespective of whether the language is garbage collected?
  • 2022-01-15: Debugger crashed before a breakpoint was hit. What happens to the program being debugged?
  • 2022-01-08: No puzzle on account of my travels
  • 2022-01-01: Relative CPU performance of a process b/w native vs
@amodm
amodm / weekend-dev-puzzles-list.md
Last active February 29, 2024 14:14
List of all #WeekendDevPuzzles

Weekend Dev Puzzle

Some time between 2021-22, I ran a list of puzzles designed to push developers into developing a better understanding of the technologies they use on a day to day basis. Each puzzle is designed to be fun, provocative, and short.

This is a complete list of those puzzles. Each link takes you to the tweet where I first posed the problem. If you like any of them, please feel free to share with others.

Edit (2024-01-27): Adding other puzzles to this 2024 onwards. Criteria:

  1. Problem statement should be understandable by most in s/w tech, even if the ability to figure it out may not be.
  2. Thinking about the problem should lead to clearer understanding of some foundational concept.
  3. Should be short.
  4. Should be fun to ponder over.
@tykurtz
tykurtz / grokking_to_leetcode.md
Last active June 1, 2024 04:52
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

/*
* =======================================
* C++ cheat sheet
* =======================================
* 01- string
* 02- vector
* 03- pair
* 04- set
* 05- map
*
@vasanthk
vasanthk / System Design.md
Last active May 31, 2024 01:39
System Design Cheatsheet

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

  1. Clarify and agree on the scope of the system
  • User cases (description of sequences of events that, taken together, lead to a system doing something useful)
    • Who is going to use it?
    • How are they going to use it?
@deanrather
deanrather / JSON-Encoding
Created July 28, 2015 09:45
JSON-encoding / decoding objects with circular references
/*
cycle.js
2015-02-25
Public Domain.
NO WARRANTY EXPRESSED OR IMPLIED. USE AT YOUR OWN RISK.
This code should be minified before deployment.
See http://javascript.crockford.com/jsmin.html