Discover gists

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

The link in the table of content jumps at the copy of the answer on this page.
The link on the answer itself points back at the original post.

Table of Content

Ultimate Beginner's Guide to Proxmox GPU Passthrough

mirror of The Ultimate Beginner's Guide to GPU Passthrough (Proxmox, Windows 10) by /u/cjalas

>Welcome all, to the first installment of my Idiot Friendly tutorial series! I'll be guiding you through the process of configuring GPU Passthrough for your Proxmox Virtual Machine Guests. This guide is aimed at beginners to virtualization, particularly for Proxmox users. It is intended as an overall guide for passing through a GPU (or multiple GPUs) to your Virtual Machine(s). It is not intended as an all-exhaustive how-to guide; however, I will do my best to provide you with all the necessary resources and sources for the passthrough process, from start to finish. If something doesn't work properly, please check /r/Proxmox, /r/Homelab, /r/VFIO, or

	#include <Windows.h>

	// Global variables
	HBITMAP hBitmapTopLeftCorner;
	HBITMAP hBitmapTopEdge;
	// Define other bitmaps for other parts of the frame...

	// Function to load bitmaps
	void LoadBitmaps() {
	// Load bitmaps from files or resources

	stages:
	- build
	- deploy

	before_script:
	- \|
	# docker variables for name and tag of new image
	export DOCKER_TAG="${CI_COMMIT_SHA:0:8}"
	export DOCKER_REPO="$CI_REGISTRY_IMAGE"
	export DOCKER_IMAGE="${DOCKER_REPO}:${DOCKER_TAG}"

	#include <Windows.h>

	// Global variables
	HBITMAP hBitmapTopLeftCorner;
	HBITMAP hBitmapTopRightCorner;
	HBITMAP hBitmapTopEdge;
	HBITMAP hBitmapBottomLeftCorner;
	HBITMAP hBitmapBottomRightCorner;
	HBITMAP hBitmapBottomEdge;
	HBITMAP hBitmapCenter;

	#include <Windows.h>

	// Global variables for bitmaps
	HBITMAP hBitmapTopLeftCorner;
	HBITMAP hBitmapTopRightCorner;
	HBITMAP hBitmapTopEdge;
	HBITMAP hBitmapBottomLeftCorner;
	HBITMAP hBitmapBottomRightCorner;
	HBITMAP hBitmapBottomEdge;
	HBITMAP hBitmapCenter;

	#include <Windows.h>

	class CustomWindow {
	public:
	CustomWindow(HINSTANCE hInstance) : hInstance(hInstance) {}

	void Create(const char* title, int width, int height) {
	WNDCLASS wc = { 0 };
	wc.lpfnWndProc = WindowProc;
	wc.hInstance = hInstance;