Arkadir

6 ms·

1.
by Arkadir 12y ago
One of the rats achieved a 53.5% success rate (the author did not specify whether this was over the entire 800 data points or only the last 100). When tested on 800 data points, a purely random strategy would have a > 53.5% success rate
2.
by Arkadir 12y ago
Honest question: what are the benefits of using environment variables over having an actual configuration file (that is obviously not added to version control) ?
3.
by Arkadir 12y ago
> structure = json.loads(json_string) Not quite. Let's say your JSON data contains the following attribute: "access" : [ "view", "edit", "admin" ], This field should be represented
4.
by Arkadir 12y ago
Easy language interoperability as a reason to choose Protobuf over JSON ? Mainstream languages support both JSON and Protobuf equally well, and the others tend to support JSON more often than Protobuf. Free backwards compatibility ? No. Num
5.
by Arkadir 12y ago
https://kdp.amazon.com/help?topicId=A301WJ6XCJ8KW0 If your list price is above $9.99, you get 35% royalties instead of 70%.
6.
by Arkadir 12y ago
"... on GitHub."
7.
by Arkadir 12y ago
Many companies offer production-grade hosting for open source applications. The fact that you are keeping your source closed tells me that you are afraid a competitor (or your clients themselves) could achieve an equivalent quality of hosti
8.
by Arkadir 12y ago
I'm curious: with HTTPS, how does the firewall know that it's an OPTIONS request ?
9.
by Arkadir 12y ago
At RunOrg, we've encountered this a few times with our CORS-only API. It is against our philosophy to leave users behind only because they are locked in by outdated infrastructure. We still want to support them. It is against our philo
10.
by Arkadir 12y ago
This was just as easy in the previous generation :) OCaml has had this feature since 1996.
11.
by Arkadir 12y ago
I have a hard time thinking of a situation where proper objects-and-functions code becomes easier to understand by removing the functions. Do you have any examples ?
12.
by Arkadir 12y ago
The only difficulty is naming the abstraction :)
13.
by Arkadir 12y ago
I would argue that functions have no business performing global side-effects in the first place --- these things are better expressed as state encapsulators (such as objects) anyway.
14.
by Arkadir 12y ago
The Single Responsibility Principle is like Body Mass Index for code: it's easy to measure (humans have an innate sense of what "reponsibility" means) but outside of extreme situations it is not precise enough to base serious
15.
by Arkadir 12y ago
The most important rule about the future is that You Aren't Gonna Need It. If the future is known then it is called "requirements". Design is for protecting you from the unknown future: allowing code to be changed in arbitrar
16.
by Arkadir 12y ago
What situation would require to mock a function ?
17.
by Arkadir 12y ago
> Roll the mouse wheel inside of the tree view. If you are on a touchscreen device, pinch out. I have neither mouse wheel nor touchscreen device, only a touchpad.
18.
by Arkadir 12y ago
Look at Kent's eight bullet points: half of them are unrelated to the DD part of TDD. Coming from a man who should know the difference between having automated tests for your software and partaking in test-driven design, I must assume
19.
by Arkadir 12y ago
Your link mentions three servers with 384GB RAM and 16 RAID10, and 16 cores each. Not very far from my 128GB 32 core example :)
20.
by Arkadir 12y ago
A few years ago, I came up with a similar proposal, though more specifically aimed at making callbacks easier to manage. It was a simple syntax extension, as opposed to new semantics for the language. You would write this: var! x = ex
21.
by Arkadir 12y ago
From my understanding, it is not the evaluation of a "future" value that causes a context switch, but rather its use: - passing it as an argument to an operator or built-in function - accessing one of its its members - calling it
22.
by Arkadir 12y ago
The main reason why writing concurrent code in JavaScript is not completely insane (just moderately so) is because of the single-threaded sequential execution model (also known as cooperative threading). Asynchronous effects need to remain
23.
by Arkadir 12y ago
I certainly agree that most people who pick NoSQL solutions "for scalability" never add a third server to their cluster.
24.
by Arkadir 12y ago
You can check it here: https://github.com/RunOrg/RunOrg/tree/master/server/cqrsLib I'm sorry for the state of the official site, there will be one soon. A `Stream` corresponds to change events
25.
by Arkadir 12y ago
NoSQL discussions always seem to conflate three very different things: storage engines, APIs and architecture. Where do we store the data ? How do we access it ? How do we make sure it scales ? The "traditional" approach is to use
26.
by Arkadir 12y ago
The story happened in Belgium, and the specific duration in this case would be three months, unless there are some specific details that we are not aware of. I agree that it would have been different in another country.
27.
by Arkadir 12y ago
I would expect such an employee to be paid over €35k. This would place the minimum notice period at 3 months.
28.
by Arkadir 12y ago
Most of the reactions both here and on LinkedIn seem to miss a crucial fact: this story happened in Belgium. In Belgium, employees must be notified in advance before they are let go: you send them a letter stating "your contract will e