Skip to content

Instantly share code, notes, and snippets.

View blaxkmaze's full-sized avatar
😀

melodyxin blaxkmaze

😀
View GitHub Profile

Story (Need to update after Sonia finishes her backstory)

  • Jhin grown up from an orphanage in the Lower City of Baldur's Gate. And yes, Jhin is an orphan.
  • Due to the snake-like scales on Jhin's shoulders, she has been seen as a monster and often being ignored or bullied the other street kids.
  • CHARNAME_SONIA is the only one that was nice to Jhin and willing to protect/help whenever. Even if that means he/she will get beaten as well.
  • A group of street kids wants to cut Jhin's fingers off as a experiment since they think she can grow another one back.
    • CHARNAME_SONIA came to rescue again and taken down
    • Both characters are in danger.
    • A woman who was passing by saved both CHARNAME_SONIA and Jhin. (see candidates below)
  • This women says she saw talents to both CHARNAME_SONIA and Jhin and decided to train them.
  • After some years of training, the women disappeared(dead, or went on a trip or something), left CHARNAME_SONIA and Jhin the apartment.
@blaxkmaze
blaxkmaze / CleanArchitecture.md
Created July 30, 2018 04:40 — forked from ygrenzinger/CleanArchitecture.md
Summary of Clean Architecture by Robert C. Martin

Summary of book "Clean Architecture" by Robert C. Martin

Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.

Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.

Clean Architecture leaves me with the same feeling, even if it's pushing the development world to do better, has some good stories and present robust principles to build software.

The book is build around 34 chapters organised in chapters.

Best Practices for Azure Redis

Below are a set of best practices that I recommend for most customers. This information is based on my experience helping hundreds of Azure Redis customers investigate various issues.

Configuration and Concepts

  1. Use Standard or Premium Tier for Production systems. The Basic Tier is a single node system with no data replication and no SLA. Also, use at least a C1 cache. C0 caches are really meant for simple dev/test scenarios since they have a shared CPU core, very little memory, are prone to "noisy neighbor", etc.
  2. Remember that Redis is an In-Memory data store. Read this article so that you are aware of scenarios where data loss can occur.
  3. Configure your client library to use a "connect timeout" of at least 10 to 15 seconds, giving the system time to connect even under higher CPU conditions. If your client or server tend to be under high load
@blaxkmaze
blaxkmaze / reinvent-2017-youtube.md
Created March 9, 2018 15:51 — forked from stevenringo/reinvent-2017-youtube.md
Links to YouTube recordings of AWS re:Invent 2017 sessions

| Title | Description

@blaxkmaze
blaxkmaze / gitprint.js
Created March 7, 2018 02:03 — forked from beevelop/gitprint.js
Print GitHub markdown files
document.querySelector('#readme').setAttribute('style', 'position: absolute; top: 0; left: 0; right: 0; bottom: 0; z-index: 100; background-color: white')
document.querySelector('body').appendChild(document.querySelector('#readme'))
window.print()
@blaxkmaze
blaxkmaze / The Technical Interview Cheat Sheet.md
Last active March 5, 2018 15:29 — forked from tsiege/The Technical Interview Cheat Sheet.md
This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

Array

Definition:

  • Stores data elements based on an sequential, most commonly 0 based, index.
  • Based on tuples from set theory.
@blaxkmaze
blaxkmaze / System Design.md
Created March 5, 2018 00:40 — forked from vasanthk/System Design.md
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?
# Your init script
#
# Atom will evaluate this file each time a new window is opened. It is run
# after packages are loaded/activated and after the previous editor state
# has been restored.
#
# An example hack to log to the console when each text editor is saved.
#
# atom.workspace.observeTextEditors (editor) ->
# editor.onDidSave ->
class Solution {
public int repeatedStringMatch(String A, String B) {
if (A == null || B == null) return -1;
if (A.length() >= B.length() && A.indexOf(B) > -1) {
return 1;
}
if ((A + A).indexOf(B) > -1) {
return 2;
}