Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
da39a3ee
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
80 ms
·
901.
▲
by
da39a3ee
5y ago
When a bug is found in production, it should usually be fixed by: 1. Make a commit supplying the test coverage that was evidently lacking. 2. Make a commit supplying the fix. Everything you say is valid. However, what I just described is th
902.
▲
by
da39a3ee
5y ago
Squashing PRs is mostly a good idea. However. When you fix a bug, you should nearly always: 1. Commit a failing test that reproduces the bug 2. Commit a fix And I tend to feel that this sort of informative history should be preserved in the
903.
▲
by
da39a3ee
5y ago
Are there any prominent category theorists who are not “characters” and present it in a humble / conventional style of mathematical exposition? A lot of the style of presentation of CT is off-putting.
904.
▲
by
da39a3ee
5y ago
Write little command line tools for yourself in it (it’s the same answer for most languages).
905.
▲
by
da39a3ee
5y ago
I thought I might see Luke Slater's name but no. If you don't know it try his 1997 album Freek Funk. It's a very beautiful album of techno.
906.
▲
by
da39a3ee
5y ago
One of the most depressing/irritating things in modern political and current affairs discourse is how standard it has become to say things like “X group is stopped more frequently by police” with the implication that the expectation is
907.
▲
by
da39a3ee
6y ago
Or slightly more comfortable —- create a temp branch before doing something. Of course that’s basically the same thing under the hood.
908.
▲
by
da39a3ee
6y ago
If you think the staging area is unintuitive you should see what emacs magit does( and I love emacs magit). You stage A, start typing a commit message, stage B, finish the commit message, commit, and lo and behold B isn’t in the commit. So
909.
▲
by
da39a3ee
6y ago
Nonsense. Google is very large and you'll find situations like this in any large sample size. There's really not much more to be said; on the whole google works great for most people. Maybe this particular case has a legitimate gr
910.
▲
by
da39a3ee
6y ago
Thank you!
911.
▲
by
da39a3ee
6y ago
Hang on, did you read the quote above from the guy that named it?! He says explicitly that he chose it not because it was accurate but because non-technical employers/funders would be unlikely to object since it sounds positive. Does t
912.
▲
by
da39a3ee
6y ago
Thank you. (I'd come across the first but not the second). It looks like there is nothing blocking me apart from the need to find a clear morning to which to devote myself to the task of doing error handling properly in my project.
913.
▲
by
da39a3ee
6y ago
Thanks, that's very helpful and may well be the encouragement I apparently needed! It is a standalone CLI application but it might want to offer a library in the future. And in any case I am attracted to following your suggestion regar
914.
▲
by
da39a3ee
6y ago
I think that's just playing with definitions. Correct me if you think this is wrong, but for most people in this thread: "debugger" := a thing that pauses and allows you to inspect the local stack frame, and step into/ov
915.
▲
by
da39a3ee
6y ago
Looks great, bookmarked. A big problem with explaining/learning this area is the name. Names are important but unfortunately the name "dynamic programming" is, according to the people responsible for choosing the name, just B
916.
▲
by
da39a3ee
6y ago
This is amazing! But there seems to be something missing: error handling. After using Rust on and off for a couple of years, a thing I still don’t understand is how to write idiomatic code which deals with multiple different error types.
917.
▲
by
da39a3ee
6y ago
This should be a non-debate. A debugger is for when you want to inspect local state in detail. That can indeed often be very useful, and they are sophisticated technology. However, the people who think that a debugger is the only way to deb
918.
▲
by
da39a3ee
6y ago
Isn't a problem here that, since there's no simple definition of what it's doing, there's no simple way to assess your false negative rate when searching for something? That is fine for many pragmatic informal uses but d
919.
▲
by
da39a3ee
6y ago
> The difference is that Gerrit tracks the evolution of, and reviews, each individual commit. What does it mean for an individual commit to evolve? I think of commits as being the atoms of the evolutionary process; i.e. evolution is a se
920.
▲
by
da39a3ee
6y ago
If you don't know what the parent is in Gerrit then how can you run CI on the patch? And if you do know what the parent is then how is it different from a "PR"?
921.
▲
by
da39a3ee
6y ago
Thanks. Can you explain why that might be a good thing? If I update the diff, does it become a new reviewable item, independent from the first version? I've never worked at a large tech company but my understanding is that at e.g. goog
922.
▲
by
da39a3ee
6y ago
> The patch workflow is smooth a Can you explain what a "patch workflow" is and in what sense Github is not a "patch workflow"? There's some confusion since some people associate "patch workflow" with a
923.
▲
by
da39a3ee
6y ago
Using email to review patches is completely absurd. The following is a contentious statement but there's no avoiding it: it's done nowadays by people who started doing it in the 80s and 90s and are being stubborn. Here are some r
924.
▲
by
da39a3ee
6y ago
It’s actually very convenient now to stack GitHub PRs; the target branch detector makes it easy to arrange a cascade, and the target branches update automatically as the earlier ones merge. Can you explain what a patch based workflow means?
925.
▲
by
da39a3ee
6y ago
Are you referring to the way VS Code is slow to display the syntax highlighting on file open sometimes? (Is that when it's getting highlighting via LSP?)
926.
▲
by
da39a3ee
6y ago
I guess you're right! I'd never noticed the laggy resizing (I use a laptop so nearly always have apps taking up the full screen). But I see that also (recent MBP w/ 32Gb RAM). I just did a comparison with slack running in chr
927.
▲
by
da39a3ee
6y ago
> And they tend to be slow electron stuff I've read this a couple of times on HN. Can someone fill me in here? Is the claim that electron apps are slow justified? If so why, technically, are they slow? The main one I use is Slack an
928.
▲
by
da39a3ee
6y ago
Ignore the upper caps thing. Have you not run into the problem that SQL cannot be written with reusable units of code? Do you not find reusable units of code to be the basis of programming?
929.
▲
by
da39a3ee
6y ago
I was surprised to find out that so many of the "software architecture" books are not about how to architect backend ecosystems comprising multiple communicating services, but instead are about patterns to use to organize large ja
930.
▲
by
da39a3ee
6y ago
I'm curious which editor/IDE you used while writing typescript? I've recently started writing typescript and I've been finding it more or less a mecca of good editor completions and LSP support, compared to what I was do
More ›