Skip to content

Instantly share code, notes, and snippets.

🎯
Focusing

Utkarsh Mani Tripathi utkarshmani1997

🎯
Focusing
Block or report user

Report or block utkarshmani1997

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View print_error.go
package main
import (
"encoding/json"
"fmt"
"log"
"github.com/pkg/errors"
)
@akutz
akutz / semaphore.go
Created Apr 25, 2016
Golang Semaphores
View semaphore.go
package semaphore
import (
"time"
)
// Semaphore enables processes and threads to synchronize their actions.
type Semaphore interface {
// Close closes the semaphore.
@christopher-hopper
christopher-hopper / vm-resize-hard-disk.md
Last active Jul 30, 2019
Resize a Hard Disk for a Virtual Machine provisioned using Vagrant from a Linux base box to run using VirutalBox.
View vm-resize-hard-disk.md

Resize a Hard Disk for a Virtual Machine

Our Virtual Machines are provisioned using Vagrant from a Linux base box to run using VirutalBox. If the Hard Disk space runs out and you cannot remove files to free-up space, you can resize the Hard Disk using some VirtualBox and Linux commands.

Some assumptions

The following steps assume you've got a set-up like mine, where:

@jvns
jvns / interview-questions.md
Last active Aug 22, 2019
A list of questions you could ask while interviewing
View interview-questions.md

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

@bsiegert
bsiegert / unixtest.go
Created Nov 18, 2013
Test unix domain sockets in Go.
View unixtest.go
package main
import (
"fmt"
"io"
"log"
"net"
"os"
"time"
)
You can’t perform that action at this time.