This reminds me The Chemical Brothers’ Star Guitar.
Use codes.AlreadyExists correctly on Exec()
This issue shows one of the places Go’s error idiom doesn’t work. The shim should use gRPC’s errors when it is applicable, but the type signature doesn’t tell.
I like gofmt. I have fantasized that Go programmers won’t have style wars because of gofmt.
Sadly, it is not true.
The biggest reason today is golangci-lint. This lint is really configurable and that makes every Go project different. It won’t be 2-spaces vs. 4-spaces different, but some projects use scopelint because the lead developer has bitten by scoping, or some projects use prealloc since it may be faster.
Please note that golangci-lint is actually useful. It is better than checking pitfalls and style stuff manually. It is Go’s CheckStyle in a good way and a bad way.
Another reason is that programmers don’t appreciate gofmt much, and introduce arbitrary rules that cannot be enforced by the tool. I don’t think it is worth to do most of the time.
This blog right now has two-column layout which is like Edward Tufte and Ink & Switch. I like sidenotes.
But I don’t like to see source code in a narrow column. So I’ve figured out the way to make source code wider than the surrounding box. That involves CSS’ new additions: calc, var, and vw.
When I wonder about Lightweight Web, I’m unsure what would be “Lightweight CSS”. While I do agree CSS is really complex and the complexity makes developing new browsers harder, CSS’ new additions are actually good and useful, at least for me.
This week was busy. While I have written,
From now on, I’m going to turn-off my work laptop after work.
I didn’t. I have also enabled Chrome again on my phone, while I know it may not work for me. This has an explanation. The preschool my kid is in has introduced a QR code-based contact-less check-in. That being said, my wife usually drops off my kid.
I have also read Twitter more than what I like. My friend has been hosting a Japanese tech podcast and I was a guest a few weeks back. This might be a small nudge to check Twitter to see its feedback.
Those things are not really bad, but I do think they are like snacking. They are designed to give you relatively instant gratification. Nowadays I even think “work” is like that. Probably startups and/or super-senior developers’ work are different. But where I work and at my level, things are broken into achievable tasks.
Parenting in general, dealing with some “life” events or learning hard materials wouldn’t go that way. I could and should be able to broke them into achievable small tasks. But it is not happening by default. And I’ve been feeling that I didn’t make enough progress on these big problems.
So snacking is not bad, but snacking without having real meals is bad.
How about blogging? Derek Sivers has said “keep your goals to yourself” in his one of the TED talks.
Ideally you would not be satisfied until you’d actually done the work. But when you tell someone your goal and they acknowledge it, psychologists have found that it’s called a “social reality.” The mind is kind of tricked into feeling that it’s already done.
In this sense, sharing good goals here would give me some gratification, which is too early to enjoy.