lalitkale

Git Hooks Template: ~/.git-templates
To create git-hook, create following python file to invoke githooks. Below is the script
commit-msg.py
---
#!/usr/bin/env python
import re, sys, os

def main():
    # example:
    # feat(apikey): added the ability to add api key to configuration

lalitkale

• aws networking fundamentals https://www.thedevcoach.co.uk/engineers-guide-aws-networking-fundamentals/
• aws load balancer docs https://docs.aws.amazon.com/elasticloadbalancing/
• api-gateway vs application load balancer differences: https://serverless-training.com/articles/api-gateway-vs-application-load-balancer-technical-details/
• aws load balancing demos from aws lb team : https://exampleloadbalancer.com/
• aws load balancers feature comparison https://aws.amazon.com/elasticloadbalancing/features/
• setup aws lambda with an ALB https://dev.to/loujaybee/set-up-aws-lambda-with-an-alb-load-balancer-2ibn
• authentication with ALB https://aws.amazon.com/blogs/aws/built-in-authentication-in-alb/
• load balancers tips and tricks https://aws.amazon.com/blogs/aws/from-our-support-team-elastic-load-balancing-tips-and-tricks/
• Best Practices in Evaluating Elastic Load Balancing (describes Architecture of the Elastic Load Balancing Service and How It Works) https://aws.amazon.com/articles/best-practices-in-evalua

lalitkale

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

• There are always 24 hours in a day.
• February is always 28 days long.
• Any 24-hour period will always begin and end in the same day (or week, or month).

lalitkale

#!/bin/bash
# Usage:
#   ./update_git_repos.sh [parent_directory] 
#   example usage:
#       ./update_git_repos.sh C:/GitProjects/ [MAKE SURE YOU USE / SLASHES]

updateRepo() {
    local dir="$1"
    local original_dir="$2"
    cd $dir # switch to the git repo

lalitkale

CI & CD:
========
2 core software development processes
CI process of automating regular code commits followed by an automated build and test process designed to highlight intergration issues early.
Additional tooling and functionality provided by Bamboo, CruiseControl, Jenkins, Go and TeamCity etc.
workflow based
CD takes the form of a workflow based process which accepts a tested software build payload from a CI server. Automates the deployment into a working QA, Pre-prod or Prod environment.
AWS CodeDeploy and CodePipeline provide CI/CD services
Elasticbeanstalk and CFN provide functionality which can be utilized by CI/CD servers.

lalitkale

/**
 * https://gist.github.com/LeverOne/1308368
 */
function uuid (a,b){for(b=a='';a++<36;b+=a*51&52?(a^15?8^Math.random()*(a^20?16:4):4).toString(16):'-');return b}

lalitkale

//https://mattwarren.org/2016/12/14/Why-is-Reflection-slow/
using BenchmarkDotNet.Attributes;
using BenchmarkDotNet.Configs;
using BenchmarkDotNet.Running;
using System;
using System.Reflection;
using BenchmarkDotNet.Diagnostics.Windows;
using FastMember;
using Sigil;

lalitkale

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

lalitkale

# N.B. The only tool missing here that is mentioned in the document is `zenmap`
# purely because this image is intended to be run via a CLI and `zenmap` is a GUI
# to `nmap` i.e. one can play around with the tools by running:
#
# $ docker build --name bite_size_networking:latest .
# $ docker run --rm -d --name bsn_test bite_size_networking:latest
# $ docker exec -it bsn_test bash
#
# Alternatively, one can change the `ENTRYPOINT` to `["bash"]` and run:
#

lalitkale

<#
.SYNOPSIS
    Using AppName the script will find all variables for that project.
    It will then look at EnvironmentToCheck for variables that have 
    been configured in other environments but not the one specified

    i.e. 

        A variable named "Test" under the scope of a "Test" environment
        will be reported if a "Test" variable under the "Prod" environment