CamouflagedKiwi

22 ms·

361.
by CamouflagedKiwi 8y ago
But what's the incentive for a large number of Google engineers to surreptitiously ask questions of a style that's explicitly banned? I think there is incentive for failed interviewees to cook up stories - or at least to tell some
362.
by CamouflagedKiwi 8y ago
One other than my native tongue, but not nearly fluently. To clarify, I don't disagree with what you're saying; I'm not a linguist but from what I know there certainly seems to be some truth in the weaker forms of the Sapir-W
363.
by CamouflagedKiwi 8y ago
That's a softer form of it which is fairly obviously true; a language with no words for weather will obviously limit discussion of the weather forecast. That's a bit different to whether it limits your ability to think about those
364.
by CamouflagedKiwi 8y ago
You're using them wrong if you duplicate everything and maintain two copies. You should have one copy of the objects in the "neutral" language (protobuf or whatever) and compile the language-specific files out of that - but y
365.
by CamouflagedKiwi 8y ago
Agreed that the problem isn't directly Jira, but (anecdotally maybe) there seems a clear correlation between Jira and unhappy developers who feel their tracker has way too much process. Jira doesn't cause the root problem, but Atl
366.
by CamouflagedKiwi 8y ago
The GIL is not there because C. It's there because of refcounting and Python guaranteeing that many nontrivial operations are thread safe.
367.
by CamouflagedKiwi 8y ago
> So clearly there is some "huge" feature that is really holding things back from running on a resource-constrained microcontroller in a stripped-down runtime. What is it? Garbage collection and goroutines. You could probably s
368.
by CamouflagedKiwi 8y ago
Fair, but that misses a bunch of short-running simple operations where hg does badly; things like "print the repo root" or "print the current branch name" take several milliseconds in Git, but Mercurial needs an order of
369.
by CamouflagedKiwi 8y ago
No, as explained in the RFC (linked in the article) they're trying to get disk encryption on low-end devices that aren't capable of supporting AES. It's not an argument that AES is in any way incorrect. I suppose it could be
370.
by CamouflagedKiwi 8y ago
I'm impressed about how honest the author is about the shortcomings of Jenkins as it is now. Very appropriate that he mentions being in a local optimum - that is where most organisations end up with Jenkins. The server nearly immediate