Viewing profile — xoudini
xoudini
HN member- Joined
- Sun, Jul 31, 2016, 7:07 PM UTC
- HN karma
- 22
- Public activity
- 15 items
- HN profile
- View on Hacker News ↗
About xoudini
Recent public activity
-
comment
Comment #32800686
> without any external dependencies (i.e. no Redis/RabbitMQ) You still depend on a database with the `Task` model. This would be a no-go for that reason, since there's no reasonabl…
-
comment
Comment #30281198
I won't comment on whether it's a solved problem in general, as I don't actively follow the area very closely, but that particular QRNG has been shown to be more biased than /dev/u…
-
comment
Comment #30267689
Link to anchor: https://www.spacex.com/updates/index.html#sl-geostrom (sic)
-
comment
Comment #30263529
Well, just letting it expire would certainly halt local development at until renewing. The primary reason for this is that some integrations require TLS for callbacks, so we have a…
-
comment
Comment #30262779
That would be my exact use-case for a service like this: monitoring a domain I have pointing at localhost (and not only for expiry, but also for revocation). At least currently the…
-
comment
Comment #27737013
Well, to be fair, the `len` operation on lists in Python is a constant time operation. What makes the example particularly bad is using a cast on the result of a floating-point div…
-
comment
Comment #26903693
I'm not familiar with the software in question, but I'm quite sure it'd still be possible to have someone else to sit your exam. For instance, you could have an external webcam poi…
-
comment
Comment #26769898
Here's a (perhaps "unnecessarily clever") Python 3 version I wrote a while back, for some reason: import functools def fizzbuzz(n): if not n % 3: yield (r := "fizz") if not n % 5: …
-
comment
Comment #26748726
I can see this happening, but with a reasonable bug-tracking solution in place and enforcing `fix/...` branches for fixes, these situations could mostly be avoided.
-
comment
Comment #26743729
Hm, you're right. The simplest example I could think of right now is the upstream having renamed/deleted something that the dev branch depends on, but didn't directly touch. That w…
-
comment
Comment #26743114
In some cases I agree, but squashes can end up so large that doing a `git bisect` (which is quite useful in finding the comparatively small commit which introduced a bug) becomes u…
-
comment
Comment #26743060
When you rebase, you basically replay the history of your branch since it diverged from the branch you're rebasing onto. Thus, the branch is always in a consistent state (or equall…
-
comment
Comment #26742844
There shouldn't be an issue in doing so. During a rebase you'll either have no conflicts — in which case there isn't an issue — or you'll have to stop to resolve conflicts, and you…
-
comment
Comment #26594366
In Swift 3 (and probably previous versions as well), `String.count` defaulted to the count of the Unicode scalar representation. In this version, iterating over a string would oper…
-
comment
Comment #26411549
I had a similar thought: git init -q && git commit -q --allow-empty -m "Hello, World\!" && git show --format=%B | head -1