ljmocic

# Read more about setting it up
# https://medium.com/@ljmocic/deploying-react-application-to-aws-s3-using-github-actions-85addacaeace

on:
  push:
    tags:
      - '*'

jobs:
  build:

motopig

package main

import (
	"crypto/ecdsa"
	"crypto/sha256"
	"encoding/hex"
	"fmt"
	"log"

	"github.com/mr-tron/base58"

xynova

Connecting Docker cli and Kubectl to Docker Desktop for Windows

Install Kubectl, Docker, Helm, etc

View details here: https://gist.github.com/xynova/87beae35688476efb2ee290d3926f5bb

Setup Docker

References:

miguelmota

package main

import (
	"fmt"
	"math/big"
)

func main() {
	s := "a"
	i := new(big.Int)

jonjack

Using an Access Token for the first time

Follow the instructions on Github to Create an Access Token in Github

Configure Git to use the osxkeychain

By default, git credentials are not cached so you need to tell Git if you want to avoid having to provide them each time Github requires you to authenticate. On Mac, Git comes with an “osxkeychain” mode, which caches credentials in the secure keychain that’s attached to your system account.

You can tell Git you want to store credentials in the osxkeychain by running the following:-

xtophs

Keep an Ubuntu container running in a Kubernetes cluster

Sometimes you just need a container that keeps shell running in a kubernetes cluster. It's very handy to debug or to open an ssh tunnel into the container network.

Unfortunately, the ubtuntu or busybox contianers from Docker Hub exit, but this little trick starts the container with a never-ending, ye low CPU consumption tail -f.

Now you can kubectl exec -it into the container, which always maintains context.

---

iamdtang

require('dotenv').config();
const request = require('request');

const credentials = `${process.env.CONSUMER_KEY}:${process.env.CONSUMER_SECRET}`;
const credentialsBase64Encoded = new Buffer(credentials).toString('base64');

request({
    url: 'https://api.twitter.com/oauth2/token',
    method:'POST',
    headers: {

MWins

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

edwardmp

package main

import (
	"io"
	"os"
	"strings"
)

type rot13Reader struct {
	r io.Reader