AJ ONeal coolaj86

How to install SSH and Load Public Keys

Install OpenSSH Server

Open Admin PowerShell
Run the following command

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

Enable the services

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

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.

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

What HTML Tags & Attributes Does Github Allow?

Re:

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

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.

Hey everyone - this is not just a one off thing, there are likely to be many other modules in your dependency trees that are now a burden to their authors. I didn't create this code for altruistic motivations, I created it for fun. I was learning, and learning is fun. I gave it away because it was easy to do so, and because sharing helps learning too. I think most of the small modules on npm were created for reasons like this. However, that was a long time ago. I've since moved on from this module and moved on from that thing too and in the process of moving on from that as well. I've written way better modules than this, the internet just hasn't fully caught up.

@broros

otherwise why would he hand over a popular package to a stranger?

If it's not fun anymore, you get literally nothing from maintaining a popular package.

One time, I was working as a dishwasher in a restu

	// 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))

	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

	/**
	* @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;
	}

	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