kiitos

29 ms·

421.
by kiitos 2y ago
principal naivety here seems to be by the author
422.
by kiitos 2y ago
https://github.com/DiceDB/dice/pull/1588 This PR attempted to fix the memory model violation I mentioned in the parent comment, but also added in an extra change that swapped the sync.Mutex to a sync.RWMutex.
423.
by kiitos 2y ago
COMMAND OUTPUT WALLCLOCK_SEC USR_SEC SYS_SEC time find ~ -iregex '.*\.jpg$' | wc -l 14372 45.04 4.59 13.23 time find ~ -iregex '.*\.jpg$'
424.
by kiitos 2y ago
Nothing in Go is thread-safe, unless explicitly documented otherwise. Some examples of explicitly-documented-otherwise stuff are in package sync and package sync/atomic. cycleMap is definitely not thread-safe. The authors knew this, to
425.
by kiitos 2y ago
You give your server.exe away for free, and make all of your revenue in value-add hosting, and maybe professional services stuff to specific customers. You still have to maintain server.exe -- fix bugs, add features, etc. -- which requires
426.
by kiitos 2y ago
> However, they are saying the implementations has two options, either raise an error reporting the race (if the implementation is told to do so), or, because the value being read is not larger than a machine word, reply to the read with
427.
by kiitos 2y ago
Yep. And even if you were to lock down the implementation of the compiler, the version of Go you're using, the specific set of hardware and OS that you build on and deploy to, and so on -- that still doesn't indemnify you against
428.
by kiitos 2y ago
I think I'm not really communicating my point effectively. If you sell a lifetime license for your software, then the customer provides a single one-time payment (essentially CapEx) which obliges you to indefinite long-term work and su
429.
by kiitos 2y ago
How did the "server executable" get written in the first place, and how can it be maintained and enhanced over time, if the only revenue stream for the company is from (optional) hosting services? Especially when relevant data for
430.
by kiitos 2y ago
> Being able to run the server executable locally. This should allow you to simply open the workspace data and continue where you left off. The "server executable" is where basically all of the value provided by these kinds of
431.
by kiitos 2y ago
There are _so many_ bugs in this code. One example among many: https://github.com/DiceDB/dice/blob/0e241a9ca253f17b4d364cdf... defines func ExpandID, which reads from cycleMap without locking the package-glo
432.
by kiitos 2y ago
> the LLM generates the code, the agent scaffolding runs the code, the code generates errors, the agent feeds it back to the LLM, the process iterates wait what
433.
by kiitos 2y ago
I've yet to see any AI/LLM produce code that withstands even basic scrutiny.
434.
by kiitos 2y ago
JWT doesn't support revocation, which is a pretty fundamental flaw.
435.
by kiitos 2y ago
Ordinary configuration is updated via deployment. Feature flags are updated without deployment. This is the fundamental difference.
436.
by kiitos 2y ago
Hard-coded feature flags are more commonly referred to as configuration. The primary purpose of feature flags is to provide a way to change system behavior dynamically, without needing a deploy.
437.
by kiitos 2y ago
https://upload.wikimedia.org/wikipedia/en/5/56/%22The_Terrib...
438.
by kiitos 2y ago
It doesn't matter if the average developer has any say on how products get made. What matters is the salary that developers earn, in general, at a demographic level, is generally among the highest. And it's important that the high
439.
by kiitos 2y ago
That's a pretty bizarre take on this dialog. But, you do you.
440.
by kiitos 2y ago
The point I'm trying to make is that the details of any specific hiring process aren't really germane to the overall discussion. Hiring disparity is a metric that's measured at a much higher level than any individual organiza
441.
by kiitos 2y ago
I think you're missing the forest for the trees, here. The io.Reader/Writer interfaces, and their implementations, are meant to provide a streaming model for reading and writing bytes, which is as efficient as reasonably possible,
442.
by kiitos 2y ago
You're spawning a goroutine per Read call? This is pretty bonkers inefficient, to start, and a super weird approach in any case...
443.
by kiitos 2y ago
You are focusing on the specific details of the hiring process, and evaluating stuff like DEI in terms of a single hiring outcome. I'm trying to clarify that the relevant scope is actually much broader, for example it might be the demo
444.
by kiitos 2y ago
You continue to focus very narrowly on the specific details of the hiring process. I'm trying to make points about higher-level stuff, related to the intent and scope of DEI-type initiatives. From these few comments, I gather that you&
445.
by kiitos 2y ago
I think we're talking past each other. Tech hiring biases, implicitly, for stuff that's considered to be culturally normative. That's not just about gender labels or how someone looks. It's also about stuff like how the
446.
by kiitos 2y ago
It's not -- "why wouldn't we expect important career X to have way more men than women, given <whatever>" It's -- "if important career X has way more men than women, is this a good thing, at a net societa
447.
by kiitos 2y ago
The New York Times is probably the most trusted, and trustable, publication in all of journalism.
448.
by kiitos 2y ago
The New York Times is probably the most trusted, and trustable, publication in all of journalism.
449.
by kiitos 2y ago
Of course, because the problem that's trying to be solved is that the tech industry has default, implicit biases in its hiring processes, which tend to favor the majority. Anonymization acts as a force multiplier for those defaults&#x2
450.
by kiitos 2y ago
Rather than "desirable" I would maybe say something like "economically dominant". If the highest-paying and most-powerful careers in a society don't at least somewhat meaningfully reflect the demographics of that so

More ›