I hereby claim:
- I am mproffitt on github.
- I am mproffitt (https://keybase.io/mproffitt) on keybase.
- I have a public key whose fingerprint is B1A2 0E2A 8F77 8914 AEBC FB41 986B A4E9 3E9F 967C
To claim this, I am signing this object:
# test | |
unbind C-b | |
set -g prefix C-a | |
# use "v" and "s" to do vertical/horizontal splits, like vim | |
bind s split-window -v | |
bind v split-window -h | |
# use the vim motion keys to move between panes | |
bind h select-pane -L |
#!/bin/bash | |
# dtcp.bash | |
# | |
# darktable copy - workflow and image management script | |
# | |
# @author Martin Proffitt | |
# | |
# Script flags | |
# | |
# --install Install the script to /usr/local/bin, setup dependencies and systemd services |
I hereby claim:
To claim this, I am signing this object:
This talks through the process of setting up and starting kernel level debugging for dynamic modules.
There is an order to be preserved in this that's easy to forget but once the session starts, is a pain to get back to.
In this example, I'm using ubuntu:22.10
base image from osboxes
, running on virtualbox
.
It is up to you the virtualisation layer you choose, your instructions may differ.
Copilot. Love it or hate AI, copilot is a useful tool but after using it for a couple of weeks, with intense activity over the last few days I have to say I have mixed feelings about it as a tool.
I think like any other tool, or human for that matter, there are times copilot gets it right, and there are times it really gets it wrong.
To give an example of where it seems to consistently get it wrong, I want to look at testing.
Now when it comes to testing in golang
I am not at my finest. In previous roles I was almost pious about it. "You will write tests, you must cover every line and every branch" - but after an extended stint in a company where writing tests wasn't just frowned upon but was actively discouraged, I found my own attitude to writing them changed. Therefore, until recently I've had an extremely relaxed attitude towards them which has left me learning how to write them all over again.
As I have come to write more and more in golang
, I find myself in a position where I not only need to wr