corylanou1

4 ms·

1.
Detent: AI agent orchestration with worktrees and serialized merge train(github.com)
2 points by corylanou1 4mo ago|1 comments
2.
by corylanou1 4mo ago
Intro video here as well to explain what/why I wrote this: https://www.youtube.com/watch?v=SE_Noc3T_DY
3.
by corylanou1 6y ago
It might be a little premature to judge an entire language on an introduction article for beginners. This article isn't intended to show every possible way Go can solve a problem, but intended to show people new to Go different ways t
4.
by corylanou1 6y ago
That's a great point. Anyone who has spent significant time with Go knows how easy it is to do a large refactor (or even a minor one) due to it being a types language. And yes, you may not start with ints, but you could easily add cod
5.
by corylanou1 6y ago
You aren't wrong. I think it depends on what your needs are. As well as what the scenarios are. If you are serializing this data a lot, then having ints vs strings is a significant advantage. Again, it depends on your use case. If y
6.
by corylanou1 6y ago
Agreed. There are a couple of clever ways to handle iota, but as my next article suggests, in general, I steer away from them if you really just need constants. I didn't go into any of the Scan/Value/Marshal etc as it was a
7.
by corylanou1 6y ago
Well, we obviously have paid courses that cover all this, but if you want my personal opinion on package layout, Ben Johnson really has a great article on it here: https://www.gobeyond.dev/packages-as-layers/
8.
by corylanou1 6y ago
In a way, yes. Go doesn't have the concept of enums, so this is as close as it gets.
9.
What's in a Name? – Keynote by Dave Cheney at Go Get Community Conference(gopherguides.com)
1 points by corylanou1 6y ago|0 comments
10.
How I Use Sourcegraph, with Cory LaNou of InfluxDB(sourcegraph.com)
18 points by corylanou1 11y ago|0 comments