rowanseymour

7 ms·

31.
by rowanseymour 11mo ago
Exactly this. Disengaging from the injustices ongoing in this world will likely benefit your mental health but it's a choice and we don't need your essays justifying that choice, and you trying to convince yourself that it makes y
32.
by rowanseymour 1y ago
I can't think of good way to give programmers control over boxing without adding a bunch of complexity that nobody wants.. but it doesn't seem out of the realm of possibility that the linter could detect issues like this. It shoul
33.
by rowanseymour 1y ago
I don't know why every time people complain about this there is an assumption that we just don't understand why it is the way it is. I get that x can implement X and x can have methods that work with nil. I sometimes write methods
34.
by rowanseymour 1y ago
Yeah CI tests and local dev environments for code that runs against S3 in prod. Right now sifting through the alternatives for whatever is easiest to run as a container in Github actions or docker-compose...
35.
by rowanseymour 1y ago
Having pondered on a bit more.. I think it's the struct that would declare that it's not usable as nil, and that in turn would tell the runtime not to box it if it's nil. That would also help the compiler (and copilot etc) sp
36.
by rowanseymour 1y ago
Of all the things one might critique Go for as not being simple, I'm not sure this is it. I've never needed to serialize "-" as a key in JSON but `-,` makes some sense given the general pattern of field tags, e.g. `json:
37.
by rowanseymour 1y ago
That works until 1) you don't want to export the value types 2) the return values aren't simple structs but slices or maps because []x is not a []X even if x implements X.
38.
by rowanseymour 1y ago
Agree the ship has likely sailed, but if it could be addressed wouldn't it be nice to remove nil value interfaces altogether? Maybe start by letting new interface types declare/annotate that they don't box nil values? Then on
39.
by rowanseymour 1y ago
It's fantastic concise language and standard library steered by people who are determined to keep it simple and intuitive... which IMO makes it all the more odd that it has this obvious foot gun trap where `!= nil` doesn't always
40.
by rowanseymour 1y ago
Ah the old nil values boxed into non-nil interfaces. Even after 8 years writing go code almost every day this still bites me occasionally. I've never seen code that actually uses this. I understand why it is the way it is but I hate it
41.
by rowanseymour 1y ago
"moving people" is a horrific way to obscure what is happening in Gaza today
42.
by rowanseymour 1y ago
Raphael Lemkin, the guy who first coined the term "genocide", considered "cultural genocide" (the killing of a culture if you will), a central component of genocide. Also, I don't know if you've noticed, but pe
43.
by rowanseymour 1y ago
"Both the definition and charge of ethnic cleansing is often disputed, with some researchers including and others excluding coercive assimilation or mass killings as a means of depopulating an area of a particular group, or calling it
44.
by rowanseymour 1y ago
To be precise.. empty slices and maps sometimes behave like nil (len, range etc) and sometimes not (inserting into a nil map). The former is a neat convenience, and I think extending that to JSON marshaling makes sense.
45.
by rowanseymour 1y ago
I had a back and forth with someone who really didn't want to change that behavior and their reasoning was that since you can create and provide an empty map or slice.. having the marshaler do that for you, and then also needing a way
46.
by rowanseymour 1y ago
Same here. It's frustrating that it doesn't seem to have contextual awareness of who we are and the things we work on so things like names of our products, names of big clients, that we use repeatedly in meetings, are often butche
47.
by rowanseymour 1y ago
Ok but that's really not the cost for a company that's been using tool X for years, accumulated some expertise in that, built their own tooling on top of it etc.
48.
by rowanseymour 1y ago
I got excited about poetry a few years back because it seemed that the community might be finally able to rally around _one_ packaging solution. My favorite thing about Go is that there isn't a shiny new packaging tool every year.. jus
49.
by rowanseymour 1y ago
The WSJ article is paywalled
50.
by rowanseymour 1y ago
I have not had great experiences interacting directly with LLMs except when asking for a snippet of code that is generic and commonly done. Now with GitHub Copilot (you need a Pro Plus I think) I'm creating an issues, assigning to Copi
51.
by rowanseymour 1y ago
This was my experience until recently.. now I'm currently quite enjoying assigning small PRs to copilot and working through them via the GitHub PR interface. It's basically like managing a junior programmer but cheaper and faster.
52.
by rowanseymour 1y ago
One does wonder how much bad insecure code is out there now being fed into LLMs to generate.. more bad code. The more you lean on something else to write your code, the less you understand what you're shipping.
53.
by rowanseymour 1y ago
Every time something like this happens it seems clear the problem is changing the vision for a project - once you've gotten a community invested in a different vision. There are lots of great projects doing something in between fully c
54.
by rowanseymour 1y ago
I tried everything I could find on Amazon but obviously that crap doesn't work. I can believe something custom made could help but my orthodontist persuaded me the only really solution was surgery or CPAP.
55.
by rowanseymour 1y ago
I've had problems with obstructive sleep apnea for a couple of years. Tried CPAP/BPAP for a month and hated it so much I'm now trying to see what I can fix with surgery even though surgeries like maxilofacial sound horrific.
56.
by rowanseymour 1y ago
I like having copilot suggest things < ~500 chars. I've discovered new patterns of doing things in go and Python and I've saved on a bit of typing. It really is just a better auto-complete for me. But anything longer than that
57.
by rowanseymour 1y ago
> This is straight up Russian mentality. I don't know how you can look at nearly a century of US imperialism in Latin America and the Middle East and conclude that client states is a Russian thing.
58.
by rowanseymour 1y ago
You shouldn't be using BIGINT for random identifiers so collision isn't a concern - this is just to future proof against hitting the 2^31 limit on a regular INT primary key.
59.
by rowanseymour 1y ago
If it's the kind of project that is going to run against one PostgreSQL database then I'd probably start a new project with Django just for its database migration support. That doesn't mean everything in the project has to be
60.
by rowanseymour 1y ago
And assuming we're not talking v7 UUIDs.. your indexes are gonna have objects you might commonly fetch together randomly spread everywhere.

More ›