-
Rubber-ducking: On Context
I’m torn between extracting auth credentials in the handler from a Go Context and passing them as arguments to service methods, or just passing the context and having the service methods get it from the Context themselves. Previously, when the auth credentials just had a user ID, we were doing the former. But we’re now using more information about what the user has access to and if we were to continue doing this, we’ll need to pass more parameters through to the service layer. Continue reading →
-
Had a rubber-ducking session with myself between passing auth info within the Go Context through to the service methods, or passing them as explicit parameters.
I decided to go with passing it as explicit parameters. It’s kinda painful to see both the auth info passed through in both the Go context and a parameter. But it will result in more readable code, and it does make it clear that this information is needed. Plus, we’re already doing this already in the codebase I’m working on already (previously it was just the user ID, but we’re going to be including some additional auth info alongside it).
I am kinda glad that this tension has been resolved. It’s been weighing on me a little.
Also, for a bit of fun, I wrote this rubber-ducking session in a post. Well, it’s not entirely for fun: that’s how I was able to work through the problem. But writing it as a dialogue and posting it online was fun.
-
Rubberducking: On Context
I’m torn between extracting auth credentials in the handler from a Go Context and passing them as arguments to service methods, or just passing the context and having the service methods get it from the Context themselves. Previously, when the auth credentials just had a user ID, we were doing the former. But we’re now using more information about what the user has access to and if we were to continue doing this, we’ll need to pass more parameters through to the service layer. Continue reading →
-
It would be nice if the CSV diff in Gitlab had a “row order not important” mode, in that any changes in row order are treated almost like whitespace changes. It won’t be something that’ll apply to all CSV files. But more often that not, the CSV files I deal with are not dependent on any row order.
-
Oof, turns out you can’t trust a browser to tell you the right MIME type for a file upload. I expected some logic involving magic numbers, but it just looks like a mixture of guessing based on file extension, deferring to the OS, and giving up and sending you
application/octet-stream. -
Spent the last few days building a small site which will convert an OPML file of RSS subscriptions into an HTML list of links to their respective websites. I needed it for a blogroll I’m planning to add, but I figured this might be something others may find useful.
-
Goland Debugger Not Working? Try Upgrading All The Things
I’ve been having occasional trouble with the debugger in Goland. Every attempt to debug a test would just fail with the following error: /usr/local/go/bin/go tool test2json -t /Applications/GoLand.app/… API server listening at: 127.0.0.1:60732 could not launch process: EOF Debugger finished with the exit code 1 My previous attempts at fixing this — upgrading Go and Goland — did get it working for a while, but recently it’s been happening to me again. Continue reading →
-
I’m a bit surprised that Jira doesn’t have a notion of drafts. You start writing a task, then you think that it might be best to know whether it’s worth doing. What do you do with this half written task? Do you create it? At the moment I just keep them in an open browser tab, which is… not ideal.
-
Need to find a way to represent a collection of IDs in Go, all representable in different ways, with each one having a different type. Kinda wish Go had algebraic data type like Elm or Haskell, or even just enums with associated data like Java or Swift. Would be so useful for this.
-
Discovered a new artist through a YouTube channel I watch. They make some pretty good chill-out music. I can recommend Synths Working Overtime and Music For Podcasts 6, particularly “Cloudloop” (track 6) and “Systematic” (track 7). 🎵
-
Falling into the trap of not using a particular mug because it’s “special”. I bought the mug to be used, I should actually use it. As the appraisers on Antiques Roadshow are wont to say, it’s a real shame that such a special thing never leaves the cupboard.
-
It’s about time I started seriously using the clipboard support that comes with Keyboard Maestro. I think the first step is making it easier to show the history. I’ve remapped the history picker to ^ ⌥ ⌘ ⇧ which feels easier to invoke, and probably easier to remember. We’ll see how it goes.
-
So after logging in this morning, I had to:
- Enter my 1Password master password,
- so I can get to my laptop password to log into the VPN,
- so I can enter my admin passwords in Settings,
- so that MacOS knows I have admin rights,
- so I can enter my admin password again to upgrade Slack.
Yep, we truly live in a golden age. 😒
-
People Are More Interested In What You're Working On Than You Think
If anyone else is weary about posting about what projects they’re working on, fearing that others would think they’re showing off or something, here’s two bits of evidence that I hope would allay these fears: Exhibit 1: I’m a bit of a fan of the GMTK YouTube channel. Lots of good videos there about game development that, despite not being a game developer myself, I find facinating. But the playlist I enjoy the most is the one where Mark Brown, the series creator, actually goes through the process of building a game himself. Continue reading →
-
Well, it’s around 4:15 on a Friday and the last code change I pushed didn’t fix the bug I was working on. Looks like that’s something to look at again on Monday.
Now to clock off and put on my Friday after-work music. Oh, wait! That’s an opportunity for a new Album Whale list.
-
Posted my first “real” list on Album Whale: my list of new and rediscovered albums of 2023. It’s a little on the small side, but that’s because I tend to listen to familiar stuff most of the time. I do have plans to post those as well, but we’ll start with something small.
-
🔗 Pika
Seeing this makes me want to try it. I think I have a problem: I want to try all of the blogging CMSes. But I have no need for it now, so I’ll just keep a link to it here for later.
-
Github Actions, Default Token Permissions, And Publishing Binaries
Looks like Github’s locked down the access rights of the GITHUB_TOKEN recently. This is the token that’s available to all Github actions by default. After taking a GoReleaser config file from an old project and using it in a new one, I encountered this error when GoReleaser tried to publish the binaries as part of a Github Release: failed to publish artifacts: could not release: PATCH https://api.github.com/repos/lmika/<project>/releases/139475588: 403 Resource not accessible by integration [] After a quick search, I found this Github issue which seemed to cover the same problem. Continue reading →
-
In lieu of sharing my Vision Pro review, let me share with you my Visual Ear Worms list.
-
So apparently I can’t even look at the album cover of “Tubular Bells 2” without having it play in my head.
-
Defense contractors should lean in to what they do in their recruitment ads. None of this “explore growth opportunities” fluff. Go with something like “Love blowing stuff up? We’ve got the job for you!”
-
It takes me longer to come up with half-baked tools for writing Jira tickets than to just write the Jira tickets. I still think of making them though. Because I just can’t stand writing Jira tickets in Jira.
-
Learnt two things about the Vision Pro buying experience from a colleague today:
- You’ll need an iPhone. Guess that rules me out (well, that plus I’m not in the US)
- The thing that scans your face is actually an App Clip, which is the only case I’ve heard of one being used in a non-demo way.
-
Thoughts on The Failure of Microsoft Bob
Watching a YouTube video about Microsoft Bob left me wondering if one of the reasons why Bob failed was that it assumed that users, who may have been intimidated by a GUI when they first encountered one, would be intimidated for ever. That their level of skill will always remain one in which the GUI was scary and unusable, and their only success in using a computer is through applications like Bob. Continue reading →