summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Remove Terraform infra entirelyOwen Jacobson2023-11-08
|
* Decommission S3 bucketOwen Jacobson2023-11-08
|
* Decommission ACM certOwen Jacobson2023-11-08
|
* Decommission CloudfrontOwen Jacobson2023-11-08
|
* Add _The Californian Ideology_; no idea how I missed this.Owen Jacobson2023-11-01
|
* Begin decommissioning cloudfront by removing DNS entriesOwen Jacobson2023-11-01
|
* Split publication into cloudfront and ec2 publish targetsOwen Jacobson2023-11-01
|
* Retire the Gossamer writeup.Owen Jacobson2023-10-25
| | | | Neat idea, but unsafe, and no longer even remotely relevant.
* Stop advertising a GPG key I no longer useOwen Jacobson2023-10-25
|
* It's time.Owen Jacobson2023-10-05
|
* Update to latest AWS providerOwen Jacobson2023-10-05
|
* Upgrade to Terraform 1.6Owen Jacobson2023-10-05
|
* Upgrade to Terraform 0.14Owen Jacobson2023-10-05
|
* Upgrade to Terraform 0.13.Owen Jacobson2023-10-05
|
* Migrate off of the outputs-based approach to finding zonesOwen Jacobson2023-10-05
|
* Check in resume sources (oops)Owen Jacobson2023-10-05
|
* Expand on tools/ convention a bit based on experiencesOwen Jacobson2023-02-07
|
* Add Ada to my resumeOwen Jacobson2023-02-07
|
* Moved to GitlabOwen Jacobson2023-02-07
|
* Add tools/ dir to path locallyOwen Jacobson2023-02-07
|
* RevisionsOwen Jacobson2022-05-02
|
* Wrote up my slow save.Owen Jacobson2022-04-03
|
* Correction: AWESOME Sinks were in U3Owen Jacobson2022-04-02
|
* A response, two years later, to _A Satisfactory Way of Building_.Owen Jacobson2022-03-30
|
* A brief writeup of tools/Owen Jacobson2022-03-04
|
* Some phrasing changes to better call out that my teams have been multinational.Owen Jacobson2022-02-26
|
* Reference 'main', not 'master', as the publication branch.Owen Jacobson2022-02-26
|
* Merge commit 'pull/3' to fix spelling mistakes.Owen Jacobson2022-02-26
|\
| * Fix spelling of 'detached'.Ashok Argent-Katwala2022-02-18
| |
* | Start using the tools/ convention for standard processesOwen Jacobson2022-02-26
| |
* | Track required tooling in BrewfileOwen Jacobson2022-02-26
| |
* | Stop tracking the built site!Owen Jacobson2022-02-26
|/
* Removed keybase proof.Owen Jacobson2020-05-08
|
* Merge branch 'pull/2'Owen Jacobson2020-04-20
|\
| * Add a banner to the MySQL Rant that helps set context.Owen Jacobson2020-04-20
| |
| * Enable admonition extension.Owen Jacobson2020-04-20
| |
| * Restore "mysql/choose-something-else" article.Alice Bevan-McGregor2020-04-14
| | | | | | | | Restore of the file dropped from 0d6f58c54a7af6c8b4e6cd98663eb36ec4e3accc to an assumed now-correct location to restore accessibility at the original URI. Additionally HTTPS'd many of the links, still requires verification pass for dead links.
* | Rebuilt site with git dicumentsOwen Jacobson2020-04-20
| |
* | Resurrected Git documentsOwen Jacobson2020-01-29
|/
* Switch to mkdocs.Owen Jacobson2020-01-28
|\
| * Add publish instructions.Owen Jacobson2020-01-28
| |
| * Editorial pass & migration to mkdocs.Owen Jacobson2020-01-28
| | | | | | | | There's a lot in grimoire.ca that I either no longer stand behind or feel pretty weird about having out there.
| * Remove accumulated deployment cruft.Owen Jacobson2020-01-28
|/ | | | | | | | | This covers: * Dokku on my own infra * Make-based use of Markdoc * The Heroku static buildpack This should clear the ground for a rework.
* A coda on accountabilityOwen Jacobson2020-01-27
|
* Upgrade to terraform 0.12Owen Jacobson2019-05-23
|
* Tag resources.Owen Jacobson2019-03-05
|
* Merge commit 'pull/1'Owen Jacobson2018-12-23
|\
| * Syntax highlightingRichard Metzler2018-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also I think Go has the better error handling. Because it is only one and it is supposed to be next to the fallible Operation. Last time I counted there were at least these methods to signal an error in JavaScript: - a return value indicating the error, sometimes as magic number (null or -1) - throw an Exception - an error callback function, which is totally dependent on the framework you use You didn't handle any errors in your JavaScript example, because you aren't forced to. In Java, there are Exceptions, but calling code isn't forced to handle unchecked RuntimeExceptions and Errors. And if you handle Exceptions wrong - and there are so many ways to do this, like swallowing or rethrowing without the root cause, you'll need much time to look into your production issues. Go code is explicit and requires the programmer of the calling code to recognize the possibility something might be slightly wrong in some computer sometime. You're still allowed to ignore this warning by using `_` in `a, _ := fallibleOperationA()`, but it is much better and also cheap if your editor has snippet support to just type `ife`and hit tab and atom is expanding it to: ```go if err != nil { return } ```
* | Enable pygments-based source code highlightingOwen Jacobson2018-12-23
| |
* | Add ip6 DNS for the blog.Owen Jacobson2018-12-23
| | | | | | | | Thanks to Raul Tambre for spotting this issue.
generated by cgit v1.2.3 (git 2.39.1) at 2026-01-02 06:46:24 +0000