staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

leonardofed

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.

---

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

isaacs

echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh

btoone

Introduction

An introduction to curl using GitHub's API.

The Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin

unclebob

Today I gave a keynote at ACCU in Oxford.  In the midst of it I made two (count them) two statements that I should have known better than to make.  I was describing the late '70s, and the way we felt about the C language at the time.  My slide said something like: "C was for real men."  Emily Bache, whom I know and hold in high regard, spoke up and said "What about women?".  And I said something like: "We didn't allow women in those days."  It was a dumb crack, and should either not have been said, or should have been followed up with a statement to the effect that that was wrong headed.  

The second mistake I made was while describing Cobol. I mentioned Adm. Grace Hopper.  I said something like "May she rest in peace."  I don't know that any of the words were actually demeaning, but the tone was not as respectful as it should have been to an Admiral in the United State Navy, and one who was so instrumental in our industry; despite what I feel about Cobol.  

I am a 59 year old programmer who was brought up 

bensheldon

# frozen_string_literal: true
require "fileutils"

# Helper for Git worktree-aware behavior
class GitWorktree
  PROJECT_ROOT = File.expand_path("..", __dir__)

  def self.instance = new

  def self.name = instance.name

riipandi

#Linux Cheat Sheet

##File Commands:

• ls – directory listing
• ls -al – formatted listing with hidden files
• cd dir - change directory to dir
• cd – change to home
• pwd – show current directory
• mkdir dir – create a directory dir
• rm file – delete file

jjb

For years, people have been using jemalloc with ruby. There were various benchmarks and discussions. Legend had it that Jemalloc 5 didn't work as well as Jemalloc 3.

Then, one day, hope appeared on the horizon. @wjordan offered a config for Jemalloc 5.

Ubuntu/Debian

FROM ruby:3.1.2-bullseye
RUN apt-get update ; \

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: