Verified Spec-Driven Development (VSDD) is a unified software engineering methodology that fuses three proven paradigms into a single AI-orchestrated pipeline:
| package main | |
| import ( | |
| "fmt" | |
| "os" | |
| "github.com/bytecodealliance/wasmtime-go/v31" | |
| ) | |
| // Default memory configuration (matching JavaScript defaults) |
| use std::collections::HashMap; | |
| use std::sync::Arc; | |
| use async_trait::async_trait; | |
| use pty_process::OwnedWritePty; | |
| use russh::server::{Auth, Msg, Session}; | |
| use russh::*; | |
| use russh_keys::*; | |
| use tokio::io::{AsyncReadExt, AsyncWriteExt}; | |
| use tokio::sync::Mutex; |
This document is targeted at those who seek to build reproducible dev environment across machines, OS, and time.
It maybe easier for remote teams to work together and not spending hours each person setting up asdf/pyenv/rbenv, LSP servers, linters, runtime/libs. Nix is probably the closest thing to Docker in terms of development environment.
Flake is used here because it provides hermetic build, with absolutely no reliance on system environment (be it Arch/Catalina/Mojave). Also it freezes dependencies in flake.lock so builds are reproducible.
This gist provides the setup to develop Java/Clojure/Python applications on Nix. But it can be easily adapted to ruby, nodejs, haskell.
| #!/bin/bash | |
| ### | |
| ### my-script — does one thing well | |
| ### | |
| ### Usage: | |
| ### my-script <input> <output> | |
| ### | |
| ### Options: | |
| ### <input> Input file to read. | |
| ### <output> Output file to write. Use '-' for stdout. |
| use std::sync::Arc; | |
| use futures_intrusive::sync::ManualResetEvent; | |
| use crate::wg::{WaitGroup, WaitGroupHandle}; | |
| pub struct Context { | |
| start: WaitGroup, | |
| done: WaitGroup, | |
| close: Arc<ManualResetEvent>, | |
| } |
Andy Thomason is a Senior Programmer at Genomics PLC. He has been witing graphics systems, games and compilers since the '70s and specialises in code performance.
For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.
After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft
| // ecdh implements a simple way to perform Diffie-Hellman Key Exchange using | |
| // Curve25519 on the command line. | |
| // | |
| // NOTE: this is a toy for fun. Don't use it. | |
| // | |
| // See https://godoc.org/golang.org/x/crypto/curve25519 and | |
| // https://cr.yp.to/ecdh.html for more info. | |
| // | |
| // The final shared secret given is the raw shared secret bytes from DH and is | |
| // not typically suitable for direct use as an encryption key as it can leak |
| import { createCipheriv, createDecipheriv, randomBytes } from "crypto"; | |
| const ENCRYPTION_KEY: string = process.env.ENCRYPTION_KEY || ""; // Must be 256 bits (32 characters) | |
| const IV_LENGTH: number = 16; // For AES, this is always 16 | |
| /** | |
| * Will generate valid encryption keys for use | |
| * Not used in the code below, but generate one and store it in ENV for your own purposes | |
| */ | |
| export function keyGen() { |
