Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.
![Screenshot 2023-12-18 at 10 40 27 PM](https://private-user-images.githubusercontent.com/3837836/291468646-4c30ad72-76ee-4939-a5fb-16b570d38cf2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE2OTUxOTYsIm5iZiI6MTcyMTY5NDg5NiwicGF0aCI6Ii8zODM3ODM2LzI5MTQ2ODY0Ni00YzMwYWQ3Mi03NmVlLTQ5MzktYTVmYi0xNmI1NzBkMzhjZjIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcyMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MjNUMDAzNDU2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NGVhOGY5YmIwMDg4NTgyMzFiZDE3MDNmZDIzYWE0MmJkZWQ4NWZiZWU5N2EzMWZmZDU0NDRiMWZiNGQ5ZjNiZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Avzs0DN9a74XQzfWzba0fXuPGjWPUyif1vNudAo-YbY)
apiVersion: v1 | |
kind: Pod | |
metadata: | |
creationTimestamp: null | |
labels: | |
run: cpu-hungry | |
name: cpu-hungry | |
spec: | |
containers: | |
- image: ubuntu |
#!/usr/bin/env bash | |
set -Eeu | |
set -x | |
# You need to use a session ticket (https://about.sourcegraph.com/handbook/support/p4-enablement#generate-a-session-ticket) | |
# in order to avoid password prompts | |
# TO edit this file, you must run `p4 edit create-revision.sh` first |
{ | |
// Place your snippets for shellscript here. Each snippet is defined under a snippet name and has a prefix, body and | |
// description. The prefix is what is used to trigger the snippet and the body will be expanded and inserted. Possible variables are: | |
// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders. Placeholders with the | |
// same ids are connected. | |
// Example: | |
// "Print to console": { | |
// "prefix": "log", | |
// "body": [ | |
// "console.log('$1');", |
-- CREATE read-only user when the user was created via the Google Cloud API (ie terraform) | |
-- GOOGLE CLOUD by default give fairly broad permissions | |
-- Prior reading https://stackoverflow.com/questions/13497352/error-permission-denied-for-relation-tablename-on-postgres-while-trying-a-selec | |
-- https://www.digitalocean.com/docs/databases/postgresql/how-to/modify-user-privileges/ | |
REVOKE ALL ON DATABASE db FROM "dev-readonly"; | |
-- This next line is important | |
REVOKE cloudsqlsuperuser FROM "dev-readonly"; | |
GRANT USAGE ON SCHEMA public TO "dev-readonly"; | |
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO "dev-readonly"; |
[alias] | |
co = checkout | |
cob = checkout -b | |
coo = !git fetch && git checkout | |
br = branch | |
brd = branch -d | |
brD = branch -D | |
merged = branch --merged | |
st = status | |
aa = add -A . |
Due to some issues with shipping at the moment my Macbook is delayed in getting to me and I will using Windows as my dev machine. These are the steps I took to set it up
Enable WSL 2 (basically required for good performance in most dev work)
Decide between Scoop & Chocolately
Install Ubuntu 20.04
Enable VS Code remote work
Per https://blog.golang.org/debugging-what-you-deploy
Make sure to compile your Go program with inlining and optimizations disabled
Also this is targetted towards delve
go build -gcflags "all=-N -l" /my/go/program
(delve on the commandline does this automatically, not sure if Goland does)