Skip to content

Instantly share code, notes, and snippets.

View lalitkale's full-sized avatar
🏠

Lalit Kale lalitkale

🏠
  • ATechieThought Labs
  • Dublin, Ireland
View GitHub Profile
@lalitkale
lalitkale / reinvent-2018-session-videos.md
Created October 12, 2022 11:25 — forked from LukasMusebrink/reinvent-2018-session-videos.md
Links to YouTube videos of AWS re:Invent 2018 sessions

The current list contains 438 sessions. The list will be updated regularly, at least once a day during reinvent. Last update: 2018-12-02 06:58 +00:00

Title Description Video
[NEW LANUCH!] Building modern apps using Amazon DynamoDB transactions (DAT374) DynamoDB transactions enables developers to maintain correctness of their data at scale by adding atomicity and isolation guarantees for multi-item conditional ... IMAGE ALT TEXT{:target="_blank"}
[NEW LAUNCH!] AWS License Manager Deep Dive (CMP393) AWS License Manager is a new service that makes it easy to bring your existing licenses to the AWS cloud and reduce licensing costs. This service offers a ... [IMAGE ALT TEXT](http://www.youtube.com/watch?v=r7pdaM3OAAQ "AWS re:Invent 2018: [NEW LA
@lalitkale
lalitkale / steve-yegge-google-platform-rant.md
Created May 2, 2022 20:51 — forked from kislayverma/steve-yegge-google-platform-rant.md
A copy (for posterity) of Steve Yegge's internal memo in Google about what platforms are and how Amazon learnt to build them

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 really have SREs and they make engineers pretty much do everything,

@lalitkale
lalitkale / code_review.md
Created December 2, 2021 19:02 — forked from marionzualo/code_review.md
Code Reviews

Code Review

A guide for reviewing code and having your code reviewed.

Peer code reviews are the single biggest thing you can do to improve your code - Jeff Atwood

Purpose

Code review is an important part of a team's development process. It helps to:

  • disseminate knowledge about the codebase/technology/techniques across teams
  • increase awareness of the features being developed
@lalitkale
lalitkale / slack_history.py
Created October 3, 2021 15:25 — forked from Chandler/slack_history.py
Download Slack Channel/PrivateChannel/DirectMessage History
# MIT License
# Copyright (c) 2016 Chandler Abraham
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
@lalitkale
lalitkale / NewComputer.ps1
Created March 14, 2021 23:30 — forked from ernestohs/NewComputer.ps1
My computer setup
Update-ExecutionPolicy Unrestricted -Force
# Base
cinst BoxStarter.Chocolatey
cinst BoxStarter.WinConfig
# Chocolatey
cinst ChocolateyPackageUpdater
# Windows 8.1 Settings and Options
@lalitkale
lalitkale / list.txt
Created March 8, 2021 17:25 — forked from shortjared/list.txt
List of AWS Service Principals
a4b.amazonaws.com
acm-pca.amazonaws.com
acm.amazonaws.com
alexa-appkit.amazon.com
alexa-connectedhome.amazon.com
amazonmq.amazonaws.com
apigateway.amazonaws.com
application-autoscaling.amazonaws.com
appstream.application-autoscaling.amazonaws.com
appsync.amazonaws.com
@lalitkale
lalitkale / cbdd.awk
Created March 2, 2021 14:46 — forked from sach1t/cbdd.awk
Chrome Bookmark De-Duplicator
# 1. export bookmarks
# 2. awk -f cbdd.awk bookmarks_12_4_16.html > uniq.html
# 3. import uniq.html
BEGIN { FS = " " }
$2 ~ /^HREF/ {
if (!($2 in seen)) {
seen[$2]
print $0
@lalitkale
lalitkale / async_await_best_practices_cheatsheet.md
Last active January 18, 2021 06:20 — forked from jonlabelle/async_await_best_practices_cheatsheet.md
C# Asynchronous Programming Guideline Cheat Sheet

Async Await Best Practices Cheat Sheet

Summary of Asynchronous Programming Guidelines

Name Description Exceptions
Avoid async void Prefer async Task methods over async void methods Event handlers
Async all the way Don't mix blocking and async code Console main method
Configure context Use ConfigureAwait(false) when you can Methods that require con­text
I have run an nginx container...
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6d67de07731d nginx "nginx -g 'daemon ..." 40 minutes ago Up 40 minutes 80/tcp, 443/tcp epic_goldberg
I want to use Debian for debug:
docker run -it --pid=container:6d67de07731d --net=container:6d67de07731d --cap-add sys_admin debian
I can see the nginx process:
@lalitkale
lalitkale / gist:19ec673a063ed5a80831a867165691bd
Created August 18, 2020 05:26 — forked from anonymous/gist:9388472
Summing up contextual influence on systems architecture
1. Monolithic applications and architectures can vary in their monolithness. This is an under-specified description.
2. Microservice applications and architectures can vary in their microness. This is an under-specified description.
3. Microservices and monolithic architectures have both benefits and disadvantages.
4. Organizations will exploit those benefits while working around any weaknesses.
5. Success of the business is a large influence on the exploitation of benefits and implementation and costs of workarounds.
6. All benefits and work arounds are context-sensitive. Meaning that they are both technically and socially constructed by the organization that navigates them.
7. Path dependency is a thing. History matters and manifests in these architectural decisions and evolution in an organization.
8. Patterns exist to inform practice, not dictate it. Zealous adherence to an architectural pattern brings peril when it is to the exclusion of cultural context in actual practice.
9. Architectural patterns w