jamstack update metadata

content/notes/2021/04/06h19m19s02.md

@@ -0,0 +1,8 @@
+---
+source: "https://chat.brainbaking.com/objects/55bf973b-9c38-4c10-aff6-fb587ea75a5d"
+context: ""
+title: "I spent the day pretending to attend a virtual Gop..."
+date: "2021-04-06T19:19:02"
+---
+
+I spent the day pretending to attend a virtual GopherCon thanks to the plethora of YouTube recordings. I promptly ordered two Go programming books after the first talk. Professionally, I was a Java/C#/JS dev, and I dabbled in C/C++/Python. This looks like a (relieving) breath of fresh air - and luckily, I'm very familiar with pass-by-value and pointers. <br><br>Things still bewilder me, of course. The books haven't arrived yet 😅 The presence of many Makefiles in GitHub Go projects - even though Go is explicitly designed to do without them - freaks me out. Devs saying "just place the _test.go files next to your implementation" freaks me out. (src/main/java, src/test/java...) The magic of "go build" without any verbosity freaks me out. The absence of "--save-dev" in "go get" freaks me out. I'm used to so many mundane complexity in development environments that encountering something touting simplicity is immediately marked as suspicious by my subconsciousness!

data/webmentions-since.json

@@ -1,3 +1,3 @@
 {
-  "since": "2021-04-06T18:02:27.925Z"
+  "since": "2021-04-06T18:57:10.610Z"
 }