Search Results

TBH this is just awful. The additional slots are used as a kind of context-specific cache, but this cache is not invalidated when another context is used. Unsetting the rules slot is not really necess …

You've already mentioned the options and their pros/cons. You might also want to look at commercially available options for comparison. In any case, the decision should likely be one of economy - how …

"Sketching" and "Upfront Design" don't necessarily contradict but complement each other. They are somewhat related to bottom-up and top-down approaches. …

In strongly/statically typed languages, this is generally discouraged, as the static type information is used to determine the legal operations on the results, with opportunities to do type inference …

Config, or maybe Configuration or Settings. A name doesn't need to convey everything about its functionality and intended usage. The documentation should state that it's mutable and that the program …

Some people will cheat when the reward is high enough in comparison to the effort and the risk/consequences of getting caught. You've described some ways of cheating, now think like your users and try …

I would favor a PUT verb on the transaction endpoint to manually set the transaction category, as @keelerjr12 suggests.. However, you need to have a clear understanding about the transaction categoriz …

You already listed two solutions - removing luxon, and removing date-fns - which are unacceptable to you. The simplest remaining option, as ugly as it is, would be to use both libraries side by side a …

The Parking Space Auction Auctions are often used to regulate access to scarce resources, and they are considered a fair mechanism by many people. I'll try to separate mechanism (which is relatively …

There are two aspects: how to handle device access in a RESTful environment, and how to deal with internal versus public services. I don't see any big issues with the first aspect, of course you can …

would work for a knowledgeable client even though it is not really HATEOAS (note I'm not a true believer or proponent of HATEOAS, it's just a mental model that allows me to think clearer about RESTful design …

A simple approach is to embed a unique token in the form which gets sent back with the PUT request, and refuse to process a second PUT with the same token. Of course, nothing prevents the user from l …

You just define hash() and equals() for Match such that it is independent of the ordering of thingA and thingB. This can be done like so (pseudo-python): class Match: def hash(self, other): …

First of all, what you're writing in your examples are not methods but standalone functions. You can write them with any parameters of your choice, although the clarity arguments in Killian's answer s …

To expand on my comment: Likes are weighted by an exponential function of t_like - t_ref. To achieve a half-life of one week, you multiply this difference by weight_factor = LN(2)/d_week where d_week …