Search Results

For programs written in an imperative/procedural style, this is next to impossible because the separate threads may access shared data, and correct semantics for larger-grained parallelism can't be ea …

There's no "normally". Whichever of two options is cheaper to deploy, operate and scale depends on many factors. Often the deployment of a monolith is cheaper, but for example if you need changes in y …

values are part of the specification (as is often the case with network protocols) then perhaps using them in the implementation is a good idea, but if not, it looks like you don't have TDD but DDT, design …

That's what database transactions were invented for. All modifications during a transaction are either written to the database at once on commit, or none are written in case they would conflict with a …

Your examples are both in the area of interfaces to systems that are not under your control, which is different from the interfaces between components that you control and where you can ensure that th …

A significant factor is tooling used by the team and the proficiency with which developers use the tools. The concept of refactoring was originally developed in the Smalltalk context, and there were a …

"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 …

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 …

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): …

You need some form of memory on system-A about which records were changed but not yet synchronized, there's no way around it. Proposed solution: Let the triggers for database changes insert entries in …

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 …

This sounds like a better approach would be to implement a list of business rules with validity date limits, section applicability, ordering key. Then for every section, you execute the applicable rul …

You'd need to design the API such that it supports the management functions that you need on the Raspi, perhaps with additional authorization requirements. …

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 …