Skip to content

BlameTroi/Troyisms

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

			======================
			       Troyisms
			There's the right way,
			    the wrong way,
			   and the Troy Way
			======================

These are notes, tricks, code snippets, and things others might wish
I didn't do. I don't think in terms of gists, but that's where some
of these might belong. A repository works for me.

If I was still blogging, much of this would be in blog posts. I
stopped blogging because the available infrastructure is all about
getting clicks, generating revenue, engagement, influencing, and
other such things.

I blogged to write. Being read is nice, but the writing is essential
to being.

Regardless, there's nothing important to anyone else here. Likely
nothing too interesting either. I expect some of these things are
'bad ideas'.

Use at your own risk. It's all public domain as far as I'm concerned,
but you can use any code from this either as public domain under the
UNLICENSE or under the terms of the MIT license.


Troy Brumley, BlameTroi@gmail.com
July 2024
So let it be written,
So let it be done.

                               ========
                               Contents
                               ========

In alphabetic order, here are the file names and short descriptions.

LICENSE            -- The usual.

README.txt         -- This document.

brutalist.txt      -- The Brutalist Manifesto, an appeal for simplicity
                      and minimalism.

cmake.txt          -- A quick reference of what works for me with CMake
                      since it is needed to really use clangd.

csick.txt          -- A cross between a screed and a rant about
                      languages and what works (or doesn't) for me a
                      while back. Nothing is forever.

fortran90.org     -- My notes as I approached Modern Fortran. Out of
                     date and wrong pretty much from the get go, but
                     there are some bits in there worth keeping. Not
                     many, but a few.

fpc-command-line  -- A cheat sheet.

indianhill.txt    -- Revision 6.0 of the an early influential best
                     practices document for C.

schemes.scm       -- My notes on working with Scheme as I go through
                     three books on Lisp/Scheme programming. It's a
                     different way of seeing things.

Releases

No releases published

Packages

No packages published

Languages