gaterush

joined 1 year ago
[–] gaterush 4 points 2 days ago (4 children)
  • Gateway: For some late payoff, hard sci-fi content, I like Frederik Pohl quite a lot. His stuff is between classic and contemporary, and balances technology with sophisticated plot and characters. I greatly enjoyed reading his Gateway series this year, could be one of my favorites.

  • Mass Effect: I was pleasantly surprised with Mass Effect: Andromeda Annihilation. I moderately enjoyed the Mass Effect video game series, and thought this companion novel could tank, but it was actually a really fun read, with great characters and immersion. The plot is orthogonal to the main plot points of the video games, rather than extensions of them, which I thought gave it breathing room for novel ideas.

[–] gaterush 7 points 1 week ago (2 children)

I was promised more moss

[–] gaterush 6 points 1 month ago

Hacker news still going strong, you get the drama stories here and there but the focus is on the technology

[–] gaterush 10 points 2 months ago

And B must be for Body of course

[–] gaterush 5 points 4 months ago

The water cooling system that only needs to be used once

[–] gaterush 18 points 4 months ago (1 children)

I just tried and got "about 40,000 billion kilometers". Also the references are completely different from the ones in the post, so I guess it was a ranking issue

AI is just too unpredictable, hard to know what's accurate and you end up doing the work yourself anyways

[–] gaterush 23 points 6 months ago (1 children)

A once in a lifetime experience!

[–] gaterush 3 points 9 months ago (1 children)

that's awesome, did not know about that handy operator!

[–] gaterush 9 points 9 months ago (6 children)

The other command could just be printf '' >> file to not overwrite it. Or even simpler >>file and then interrupt

[–] gaterush 10 points 10 months ago

I generally agree and like this strategy, but to add to the other comment about catching reimplemented code, there's just some code quality reviewing that cannot be done by automating tooling right now.

Some scenarios come to mind:

  • code is written in a brittle fashion, especially with external data, where it's difficult to unit test every type of input; generally you might catch improper assumptions about the data in the code
  • code reimplements a more battle tested functionality, or uses a library no longer maintained or is possibly unreliable
  • code that the test coverage unintentionally misses due to code being located outside of the test path
  • poor abstractions, shallow interfaces

It's hard to catch these without understanding context, so I agree a code review meets are helpful and establishing domain owners. But I think you still need PR reviews to document these potential problems

[–] gaterush 4 points 10 months ago

When your function literally returns the void

[–] gaterush 5 points 10 months ago (3 children)

It's under Profile > Saved , but you have to hit the filter button to select Show Comments

view more: next ›