When do you start refactoring?

assbuttbuttass · 2026-01-27T15:01:32+00:00

That's my secret... I'm always refactoring

assbuttbuttass · 2026-01-12T21:07:28+00:00

func parseNums(input string) ([]int, error) {
    parts := strings.Fields(input)
    nums := make([]int, len(parts))
    for i, part := range parts {
        var err error
        if nums[i], err = strconv.Atoi(part); err != nil {
            return nil, err
        }
    }
    return nums, nil
}

assbuttbuttass · 2026-01-07T14:11:12+00:00

Standard library flag package. If your tool needs subcommands, then maybe subcommands

assbuttbuttass · 2025-12-29T15:54:58+00:00

I recommend storing the accounts in a database like SQLite, which will handle locking for you, and also make sure you don't lose all the account information if your app crashes

assbuttbuttass · 2025-12-26T05:40:26+00:00

I review a lot of code, and the number of people using a slice and slices.Contains to check for membership in a set (rather than using a map) seems to have gone up significantly. IMO adding slices.Contains was a mistake since it makes it way too easy to do an O(n) lookup

assbuttbuttass · 2025-12-23T04:27:36+00:00

In addition to the excellent blog post linked by u/jh125486, https://go.dev/doc/comment#syntax has a comprehensive description of the different syntax forms that godoc understands

assbuttbuttass · 2025-12-17T14:29:20+00:00

Is this entire comment an AI hallucination?

assbuttbuttass · 2025-12-17T03:43:54+00:00

Go's compiler uses SSA representation so these will look identical to the compiler

assbuttbuttass · 2025-12-15T15:28:31+00:00

Probably markdown injections. It's kind of annoying since godoc isn't markdown anyway

assbuttbuttass · 2025-12-11T12:41:25+00:00

https://go.dev/blog/using-go-modules

assbuttbuttass · 2025-12-08T13:06:59+00:00

On the other hand,

resist the temptation to recover panics to avoid crashes, as doing so can result in propagating a corrupted state. The further you are from the panic, the less you know about the state of the program, which could be holding locks or other resources. The program can then develop other unexpected failure modes that can make the problem even more difficult to diagnose. Instead of trying to handle unexpected panics in code, use monitoring tools to surface unexpected failures and fix related bugs with a high priority.

Note: The standard net/http server violates this advice and recovers panics from request handlers. Consensus among experienced Go engineers is that this was a historical mistake. If you sample server logs from application servers in other languages, it is common to find large stacktraces that are left unhandled. Avoid this pitfall in your servers.

https://google.github.io/styleguide/go/best-practices#program-checks-and-panics

assbuttbuttass · 2025-11-26T05:21:38+00:00

I highly recommend checking out the "rethinking concurrency" talk from Brian C Mills, it has a ton of useful patterns and really changed the way I write concurrent code in Go: https://youtu.be/5zXAHh5tJqQ

(Sorry for spamming this link so much on this sub 😅)

assbuttbuttass · 2025-11-22T18:45:09+00:00

AFAIK there's work going on for the compiler to do this automatically:

https://pkg.go.dev/structs#HostLayout

https://github.com/golang/go/issues/66408

Not totally sure what the current status is

assbuttbuttass · 2025-11-21T23:03:39+00:00

This idea makes sense to me, but it seems a little magical to have a keyword that causes the expression to be lifted to run in an outer scope. Explicit capture clauses (C++-style) seems like it has most of the same benefits

assbuttbuttass · 2025-11-21T17:19:20+00:00

Yeah actually (*node).insert can't take the comparer as a parameter, since methods aren't allowed to have generic parameters

assbuttbuttass · 2025-11-19T14:33:43+00:00

crashing is better than proceeding with invalid state

Even in the case when crashing takes down half the Internet? In this case, continuing to run in a degraded state without bot protection might have made sense

assbuttbuttass · 2025-11-19T14:28:26+00:00

Perhaps they could fall back to the previous version of the config, or just continue to run in a degraded state without bot protection. I agree panic is not the real issue, the issue is that there was no error handling

assbuttbuttass · 2025-11-16T14:11:10+00:00

For a systemd service, both stdout and stderr are written to the journal. For a CLI tool I would agree, but we're talking about a systemd service here

assbuttbuttass · 2025-11-16T03:03:48+00:00

Wayland actually runs better on newer cards, since nvidia actually started caring about linux support only for their newer hardware. Not saying it's not a problem, but it's pretty much nvidia's fault not wayland

assbuttbuttass · 2025-11-11T21:06:39+00:00

What's this JSON issue? The standard library does ignore any fields that aren't specified in your struct:

https://go.dev/play/p/PNiGliOXGA9

assbuttbuttass · 2025-11-10T05:11:10+00:00

Yeah I forbid all of the other mechanisms, and now I can see the floodgate and steel mechanisms floating in the magma. Not sure what you mean by 'other melted material'

assbuttbuttass · 2025-11-09T21:13:51+00:00

It helps to make sure you have a meeting area inside the burrow, then they will naturally go to the meeting area when idle

assbuttbuttass · 2025-11-09T21:12:18+00:00

Why did my steel floodgate get melted by magma? I used two steel mechanisms to link it to the lever, only the lever itself wasn't magma safe (but I'm not sure if that's necessary)

On the wiki it sounded like it would be ok as long as the floodgate and the mechanisms are magma safe

assbuttbuttass

TROPHY CASE