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 / gist:dc7f18489160327198a9c409ea4b8470
Created August 30, 2024 20:47 — forked from joshsmith/gist:2041454
Geoffrey Moore's positioning framework (for products)

Product Positioning Framework

  • For (target customers)
  • Who must (solve a specific problem)
  • Our product is a new (new product category)
  • That provides (key breakthrough benefit vs. current way of doing things – which solves dilemma)
  • Unlike (competitor in new category)
  • We have (whole product most relevant for you)
@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 / high-availability.md
Created March 8, 2021 13:54
Topic: High Availability

Availability Availability is the proportion of time that the system is functional and working. It is usually measured as a percentage of uptime. Application errors, infrastructure problems, and system load can all reduce availability.

A cloud application should have a service level objective (SLO) that clearly defines the expected availability, and how the availability is measured. When defining availability, look at the critical path. The web front-end might be able to service client requests, but if every transaction fails because it can't connect to the database, the application is not available to users.

Availability is often described in terms of "9s" — for example, "four 9s" means 99.99% uptime. The following table shows the potential cumulative downtime at different availability levels.

99% 1.68 hours 7.2 hours 3.65 days

@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