Skip to content

Instantly share code, notes, and snippets.

View leonardofed's full-sized avatar

@leonardofed leonardofed

View GitHub Profile
@leonardofed
leonardofed / README.md
Last active November 14, 2024 13:37
A curated list of AWS resources to prepare for the AWS Certifications


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.


@leonardofed
leonardofed / 0-README.md
Created September 7, 2016 16:52 — forked from alexcasalboni/0-README.md
AWS Lambda: Advanced Coding Session - clda.co/aws-lambda-webinar

AWS Lambda: Advanced Coding Session (slides)

Live demos:

  1. Amazon API Gateway Access Control
  2. Amazon Kinesis Streams processing
  3. Amazon Cognito Sync trigger
  4. AWS CloudFormation Custom Resources
### Keybase proof
I hereby claim:
* I am leonardofed on github.
* I am leonardofed (https://keybase.io/leonardofed) on keybase.
* I have a public key ASCx8GB9O93q2rLHtFHUGGabpeHvQFAbGFmXw2cfXVjGeAo
To claim this, I am signing this object:
@leonardofed
leonardofed / product-screen.md
Last active November 13, 2024 01:54
type12

Dashboard

Create, remove, edit interviews. alt dashboard

Environment

Select the environment stack that matches your company production environment (frameworks, languages, databases, utilities)

  • Backend frameworks: Django, Flask, Spring, SpringBoot, Play Framework, Ruby on Rails, NodeJS
  • Frontend frameworks: React, VueJS, Angular
  • languages: Python, JS, Ruby, Erlang, C, C++, Java, Scala
  • databases: MongoDB, PostgreSQL, MySQL, SQLite, Redis
@leonardofed
leonardofed / type12.md
Last active November 13, 2024 01:56
I built this thing to make coding interviews suck less

We built this thing to make coding interviews suck less

The traditional technical interview process is designed to ferret out a candidate's weaknesses whereas the process should be designed to find a candidate's strengths.

No one can possibly master all of the arcana of today's technology landscape, let alone bring that mastery to bear on a problem under pressure and with no tools other than a whiteboard.

Under those circumstances, everyone can make anyone look like an idiot.

The fundamental problem with the traditional technical interview process is that it is based on a chain of inference that seems reasonable but is in fact deeply flawed. That chain goes something like this: