Impact123

Proxmox VE tips

Just some tips I gathered over time. All in one easily reachable place so I can share it wherever I want.

Please note that unless you see a shebang (#!/...) these code blocks are usually meant to be copy & pasted directly into the shell. Some of the steps will not work if you run part of them in a script and copy paste other ones as they rely on variables set before.
The { and } surrounding some scripts are meant to avoid poisoning your bash history with individual commands, etc. You can ignore them if you manually copy paste the individual commands.
I chose to write things "in the open" that way so there's still some control and things don't become a black box.

Table of contents

HacDan

How to install SSH and Load Public Keys

Install OpenSSH Server

1. Open Admin PowerShell
2. Run the following command

Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

3. Enable the services

Set-Service -Name ssh-agent -StartupType `Automatic`

gsinclair

Karabiner layouts for symbols and navigation

Gavin Sinclair, January 2022

Introduction

I use Karabiner (configured with Gosu) to make advanced key mappings on my Apple computer. Karabiner allows you to create “layers”, perhaps simulating those on a programmable mechanical keyboard. I make good use of these layers to give me easy access (home-row or nearby) to all symbols and navigational controls, and even a numpad.

The motivation is to keep hand movement to a minimum. Decades of coding on standard keyboards has unfortunately left me with hand and wrist pain. I will soon enough own a small split keyboard which will force me to use layers to access symbols etc., so this Karabiner solution, which has evolved over months, is a training run for that.

coolaj86

Moved to https://github.com/therootcompany/software-development/wiki/Go-Cheatsheet

coolaj86

What HTML Tags & Attributes Does Github Allow?

Re:

• github/markup#245
• https://github.com/gjtorikian/html-pipeline/blob/11cec3d43cab9f6beddd95bda40ad6ac654fe2f8/lib/html/pipeline/sanitization_filter.rb#L44-L95

      WHITELIST = {
        :elements => %w(
          h1 h2 h3 h4 h5 h6 h7 h8 br b i strong em a pre code img tt

getify

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

chriseidhof

// Run any SwiftUI view as a Mac app.

import Cocoa
import SwiftUI

NSApplication.shared.run {
    VStack {
        Text("Hello, World")
        	.padding()
            .background(Capsule().fill(Color.blue))

whiteinge

Default compiler settings used, unless noted otherwise. Host system is Fedora
x86_64. Linked libs produced via `ldd`.

Linked libs common to all below: linux-vdso libc ld-linux

Size    Lang                Specific libs       Common libs

 18K    c                   -                   - 
 20K    luastatic           liblua              libm libdl
 22K    vala                libgobject libglib  libffi libpcre libpthread

BeauBouchard

/**
 * @return {boolean} true whether inside a node application or not.
 **/
function isNode () {
  try {
    return "object" === typeof process && Object.prototype.toString.call(process) === "[object process]";
  } catch(e) {}
  return false;
}

mvndaai

package tabletest

import "errors"

//ForceError will return an error if the boolean is true
func ForceError(force bool) error {
	if force {
		return errors.New("forced error")
	}
	return nil