Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
0x696C6961
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
0x696C6961
2mo ago
This is anecdotal, but I know that a lot of my coworkers and coasting and putting up one AI generated PR per day which they've hardly even self reviewed.
32.
▲
by
0x696C6961
2mo ago
You can also make breaking changes to internal APIs without versioning or release coordination. Just update all the call sites.
33.
▲
by
0x696C6961
2mo ago
I've dreamt about pernosco (rr) style traces being available for tests in PRs. Imagine a DST setup where the PR shows diffs of deterministic test execution traces (I have no idea what these diffs would look like)
34.
▲
by
0x696C6961
2mo ago
Well either way, these things usually land in golangci-lint first and get promoted if they're deemed useful enough.
35.
▲
by
0x696C6961
2mo ago
I think that's a no-go because vet checks have no-false-positive policy. Ie, when go vet flags something, its a bug.
36.
▲
by
0x696C6961
2mo ago
Mhm, probably worth a golang-ci check for duplicate field names which are accessed by methods on the embedded type.
37.
▲
by
0x696C6961
2mo ago
random() return 4; // chosen with dice roll
38.
▲
by
0x696C6961
2mo ago
The survey started in 2016. But even if it didn't, that still wouldn't make a difference. You're clearly not a serious person, so I think I'm done responding.
39.
▲
by
0x696C6961
2mo ago
If they didn't want to add generics, why were they actively working on generics proposals and designs since the inception of the language? Was it a hedge against the potential of being pressured into adding them in the future?
40.
▲
by
0x696C6961
2mo ago
This idea that they just caved and added them due to pressure is a false narrative invented by detractors like yourself. Here is a timeline if you're interested: 2009 Go released. June 2010 https://github.com/golang
41.
▲
by
0x696C6961
2mo ago
The generics implementation is perfectly fine. The fact that you completely dodged my question is telling. But please, keep living in your alternate reality.
42.
▲
by
0x696C6961
2mo ago
If this was true, why did they add generics?
43.
▲
by
0x696C6961
2mo ago
https://github.com/golang/go/issues/70811 Go moves slowly
44.
▲
by
0x696C6961
2mo ago
This is exactly what I do. I don't get why everyone is trying to reinvent the whole development workflow/lifecycle. Our existing tools and processes are pretty good.
45.
▲
by
0x696C6961
2mo ago
Ikr, at that point the code itself is a better way of encoding the information.
46.
▲
by
0x696C6961
2mo ago
There's a big difference between understanding the underlying concepts vs being proficient with a tool.
47.
▲
by
0x696C6961
2mo ago
That's like asking how to keep up with your Instagram feed. Framing it as a goal is strange.
48.
▲
by
0x696C6961
2mo ago
Again, it happens, but the impact is wildly overstated. I get so confused with people saying "once it compiles, it probably works" (regardless of language). The problems I struggle with need invariants that can't be expressed
49.
▲
by
0x696C6961
2mo ago
If you're not sitting in a group of 5 watching one guy code, then you're not a team player.
50.
▲
by
0x696C6961
2mo ago
You're painting a picture where people writing Go are constantly drowning in nil pointer panics. This is not reality. You hit them occasionally and they're trivial to understand and fix.
51.
▲
by
0x696C6961
2mo ago
Lol "I swear have a girlfriend, she just goes to a different school"
52.
▲
by
0x696C6961
2mo ago
I like to rephrase things in my own words when I read new concepts. The LLM can tell me if my version is totally off.
53.
▲
by
0x696C6961
2mo ago
This just looks like obsidian's markdown flavour.
54.
▲
by
0x696C6961
2mo ago
The design in the shoppify post already had a background process for the item replenishment.
55.
▲
by
0x696C6961
2mo ago
Some people use it to think less, some people use it to learn more.
56.
▲
by
0x696C6961
3mo ago
This is scary though too. If the gov managed a key server like this, almost all companies would start requiring it. But this effectively gives the gov a very easy way to lock you out of everything.
57.
▲
by
0x696C6961
3mo ago
Don't trust anyone who tells you event sourcing is simple to implement.
58.
▲
by
0x696C6961
3mo ago
You inject the pool itself.
59.
▲
by
0x696C6961
3mo ago
Using event sourcing instead of basic crud should go on a startup suicide guide ...
60.
▲
by
0x696C6961
3mo ago
Your definition is diluted to the point of being worthless.
More ›