SleekoNiko

I think it's also important to disclose how rigorously you tested your changes, too. I would hate to spend my time looking at a change that was never even tested by a human.

It sounds like you do both of these. Judging by the other replies, it seems that other reviewers may take a harsher stance, given the heavily polarized nature of LLMs. Still, if you made the changes and you're up front about your methodology, why not? In the worst case, your PR gets closed and everybody moves on.

Comment · 1 year ago

My non-expert advice is to kindly communicate this early, before it becomes a deeper problem that blows up suddenly one day. If money isn't a concern, it at least opens up a wider selection of options for how you two can share duties. Best of luck to you both.

Comment · 2 years ago

I've tried going down this route myself by using libraries like fp-go[1]. I think this particular project has done a great job, but I ultimately opted not to pursue functional programming in Go for a few reasons:

- Ergonomics weren't the greatest when working with monads such as options and results. I think pattern matching is needed here, but concepts like those go against Go's core design philosophy.

- I suspect there are several cases where runtime performance is an issue, but admittedly did not investigate this.

- Perhaps most importantly, it deviates from the way most people read and write Go, and less importantly, LLMs struggle too.

Because of these reasons, I came to the conclusion that the advantages were not worth the trade-offs.

Perhaps somebody will create a garbage-collected Rust-like language in the future and bridge the gap between the two languages.

[1] - https://github.com/IBM/fp-go

Comment · 2 years ago

Forgive me as I'm not experienced in Go. I had a look at the API reference for encoding/json[1] and performed a (very hasty) search on the source code[2].

The API reference doesn't state that panics are a part of the expected error interface, and the source code references seem to be using panics as a way to validate invariants. Is that what you're referring to?

I'm not entirely sure if the panics are _just_ for sanity, or if input truly can cause a panic. If it's the latter, then I agree - yikes.

[1] - https://pkg.go.dev/encoding/json

[2] - https://cs.opensource.google/search?q=panic&sq=&ss=go%2Fgo:s...

Comment · 3 years ago

A good, existing example I'd like to show you is Screeps: https://screeps.com/

Personally, when I'm in the mindset of playing that game, I can't help but come back to my bot every 30 minutes to see if it's performing well. When I see that it's doing something strange, I take notes and can't stop thinking about possible solutions.

When I'm not in the mood to play (i.e. analyze the bot or program more functionality), it does indeed sit there, but to me, that's no different than any other multiplayer game. :)

I do think that it takes a certain kind of leaderboard-chasing person to stay glued to it, though.

Comment · 3 years ago

I think you've just described all social media. :)

Comment · 3 years ago

> When Spotify was young they were extremely developer and ecosystem friendly. It gets progressively worse and worse over time.

This is somewhat tangential, but I feel like this happens often, as internal power and culture shifts away from being developer-driven to consumer- or manager-driven.

This doesn't happen for every company, thankfully.

Comment · 4 years ago

Does publicly correcting your boss count as "dunking on" them? I didn't see the employee calling Elon a moron or anything like that.

Elon made a statement, Eric told Elon was wrong based on his experience, Elon asked for him to elaborate, Eric did so, and Elon didn't like that.

If I'm working for you, and you don't have the humility to be wrong about a relatively small detail in public, I don't think I want to work for you anymore.

Comment · 13 years ago

No, that's Javascript that handles the user interface.

Comment · 13 years ago

I thought I was going crazy.