karthiks

cheatsheet

• https://kubernetes.io/docs/user-guide/kubectl-cheatsheet/
• https://learnk8s.io/blog/kubectl-productivity/
• https://gist.github.com/so0k/42313dbb3b547a0f51a547bb968696ba
• https://speakerdeck.com/so0k/kubectl-tips-and-tricks
• https://github.com/dennyzhang/cheatsheet-kubernetes-A4
• https://medium.com/bitnami-perspectives/imperative-declarative-and-a-few-kubectl-tricks-9d6deabdde
• http://blog.kubernetes.io/2015/10/some-things-you-didnt-know-about-kubectl_28.html
• https://coreos.com/blog/kubectl-tips-and-tricks

karthiks

Stevey's Google Platforms Rant

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 real

karthiks

AWS Amplify and AppSync with Expo (React Native) cheat sheet and reference guide

[AWS Amplify] https://aws-amplify.github.io
[Expo] https://expo.io

// In order to run the Android emulator with Expo you will need Android Studio with Android Virtual Device Manager
// In order to run the iOS simulator with Expo you'll need Xcode  

INITIALIZE PROJECT

karthiks

	<script>
		function printDiv(divID){
			var printContents = document.getElementById(divID).innerHTML;
			var originalContents = document.body.innerHTML;

			document.body.innerHTML = printContents;

			window.print();

			document.body.innerHTML = originalContents;

karthiks

Bash

for file in prefix*; do mv "$file" "${file#prefix}"; done;

The for loop iterates over all files with the prefix. The do removes from all those files iterated over the prefix.

Here is an example to remove "bla_" form the following files:

bla_1.txt
bla_2.txt

karthiks

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.

For more about AWS and AWS Certifications and updates to this Gist you should follow me @leonardofed

---

karthiks

android.permission.ACCESS_ALL_DOWNLOADS
android.permission.ACCESS_BLUETOOTH_SHARE
android.permission.ACCESS_CACHE_FILESYSTEM
android.permission.ACCESS_CHECKIN_PROPERTIES
android.permission.ACCESS_CONTENT_PROVIDERS_EXTERNALLY
android.permission.ACCESS_DOWNLOAD_MANAGER
android.permission.ACCESS_DOWNLOAD_MANAGER_ADVANCED
android.permission.ACCESS_DRM_CERTIFICATES
android.permission.ACCESS_EPHEMERAL_APPS
android.permission.ACCESS_FM_RADIO

karthiks

"-------------------------------------------------------------------[Vundle]----
set nocompatible
filetype off
set rtp+=~/.vim/bundle/vundle/
call vundle#rc()

Bundle 'gmarik/vundle'

Bundle 'kien/ctrlp.vim'
Bundle 'mileszs/ack.vim'

karthiks

I'm puzzled by the behavior of take_while and drop_while when called without
a block. They return enumerators -- that part I understand -- but I'm not
understanding how those enumerators behave. 

Here's what I mean:

>> enum = [1,2,3,4,5].take_while
=> #<Enumerator: [1, 2, 3, 4, 5]:take_while>
>> enum.next
=> 1

karthiks

Once you have your own instance of copycopter-server running, you need to do the following:

1. Create a new project and take note of its hostname and api key

2. Make sure you are on the latest version of the copycopter_client gem, at the time of this writing it is 2.0.0

3. Export the latest version of your published drafts:

  $ RAILS_ENV=production bundle exec rake copycopter:export