ajss

no profile record

comments

·vor 8 Jahren·discuss

> The function `a -> Maybe a` is a different function than `a -> a`. Despite his intuition that the latter provides a stronger guarantee and shouldn't break code, callers may be expecting the Functor instance that the `Maybe` provides and therefore is a breaking change.

I don't really follow that. How can it be a breaking change? Can you give an example?

ajss

·vor 8 Jahren·discuss

I really dislike that.

The document is mutable and goes through a whole sequence of states that aren't what you want?

Constructing a body object with a document argument modifies the document?

ajss

·vor 8 Jahren·discuss

People were running a real money service that consumed JSON from another service and it didn't validate the incoming JSON? Wow.

ajss

·vor 8 Jahren·discuss

Along a similar line, I love Stuart Halloway's talk on Narcissistic Design - https://www.youtube.com/watch?v=LEZv-kQUSi4

Prefer APIs over data.

Start with DSLs.

Always connect (and never enqueue).

Create abstractions for information.

Use static typing across subsystem boundaries.

Put language semantics on the wire.

Write lots of unit tests.

Leverage context.

Update information in place.

ajss

·vor 8 Jahren·discuss

Specs are not scoped. There's a global registry. You may end up chasing other people's bugs.

ajss

·vor 8 Jahren·discuss

I think "late indexing" maybe referring to an implementation detail. The indexes aren't updated after each transaction. When you query the db, the result is a merge between the index and the transactions that haven't been indexed yet. The index is updated in batches.

ajss

·vor 9 Jahren·discuss

Look at the function doc string. Look at the function spec/fdef Look at the function comments.

OK, there aren't any. Pull requests accepted?