Works for Portugal since forever
Code is more flexible than text for drafting the idea. Later on it will expand into a fully working solution. Defining non functional interface definitions and data objects for "scribbling" the use case works best for…
catch them at the source and return sealed classes (used like sum types) instead
This makes a lot of sense since quite often many positive reviews are just fake and paid.
Lovely all these nonsense operators like ^. .~ just to save a few characters and make everything more magic than it is.
Why would I verify logging which itself is a verification instrument? And, seriously, how hard is it to emit a diagnostic message so I need a test for that to get it right?
the so called "purity" is achieved by using a higher kinded type and the cats IO monad. it's like adding "1+1" with a "mathematical-calculation-monoid-combine-factory-builder-singleton-locator-evaluator-pattern". I…
I don't get it: Why do we need category theory and monads for every little fart?
I can confirm that: cloud helps to evade the incompetent sales and infrastructure teams in many companies. Saving money never works once your product scales out.
How about adding custom additional yellow dots to render the hidden information useless?
Would it be possible to print out on a piece of yellow paper to make the yellow dots undetectable?
Works for Portugal since forever
Code is more flexible than text for drafting the idea. Later on it will expand into a fully working solution. Defining non functional interface definitions and data objects for "scribbling" the use case works best for…
catch them at the source and return sealed classes (used like sum types) instead
This makes a lot of sense since quite often many positive reviews are just fake and paid.
Lovely all these nonsense operators like ^. .~ just to save a few characters and make everything more magic than it is.
Why would I verify logging which itself is a verification instrument? And, seriously, how hard is it to emit a diagnostic message so I need a test for that to get it right?
the so called "purity" is achieved by using a higher kinded type and the cats IO monad. it's like adding "1+1" with a "mathematical-calculation-monoid-combine-factory-builder-singleton-locator-evaluator-pattern". I…
I don't get it: Why do we need category theory and monads for every little fart?
I can confirm that: cloud helps to evade the incompetent sales and infrastructure teams in many companies. Saving money never works once your product scales out.
How about adding custom additional yellow dots to render the hidden information useless?
Would it be possible to print out on a piece of yellow paper to make the yellow dots undetectable?