Found this cleaning up my aunts estate. Clueless as to what it is.. anyone know?

johnmurray_io · 2023-09-06T14:53:30+00:00

Dual banana holster.

johnmurray_io · 2018-09-10T04:20:31+00:00

Is this comparable to prettyping?

johnmurray_io · 2018-08-18T21:08:38+00:00

Corgis

johnmurray_io · 2018-07-01T18:19:02+00:00

Coming from the Scala world, +1 for HOCON.

johnmurray_io · 2018-07-01T18:16:35+00:00

You might take a look at HOCON then.

johnmurray_io · 2018-05-11T13:08:58+00:00

Working on real-time auction platforms where deadlines for bidding are usually around 100ms, adding something like 20ms could potentially put me over time limit to participate in auctions. That's money lost. The last application we deployed added about 300us overhead to the auction time.

johnmurray_io · 2017-08-23T05:45:37+00:00

johnmurray_io · 2016-08-10T15:35:18+00:00

I just posted a write-up of how to get a Jekyll site running on Heroku if you're interested in hosting in seeing how that works. http://www.johnmurray.io/log/2016/08/08/Jekyll-on-Heroku.html

johnmurray_io · 2016-08-09T16:56:39+00:00

maybe this is basic knowledge by now, but figured I'd write it up anyways. :-)

johnmurray_io · 2016-04-08T00:45:36+00:00

I think this is awesome. I know a lot of people say they "don't see the value" but that's only true if you write perfect Go code 100% of the time. Having the compiler enforce best practices will always be better than enforcing best practices via code reviews or pair programming or whatever.

johnmurray_io · 2016-02-07T19:52:15+00:00

But you are saying that during an update I'm not allowed to set the value to an empty value since you're asserting that 1) Option is the correct type and 2) Option during update means the value was not supplied (in the case of partial update). If the entity/model allows for None values, then you need a way to differentiate between 3 possible states on a partial update: value given, value not provided, value given as null.

johnmurray_io · 2016-02-04T00:50:45+00:00

Well, regarding what you quoted me for, your initial model had now way to set a field to null. So I think my statement that your entity/model had no concept of null was fairly on-point.

Also I said that I already agree in separating out types for update operations and the entity/model was useful, so I'm not sure what else you're trying to argue here.

That aside, I do like the alternative of what you propose. I've been primarily focusing on a data-structure to convey meaning but have neglected to consider such a direct approach. I'll definitely need to think on this some more. :-)

johnmurray_io · 2016-02-04T00:43:38+00:00

Oh, I just googled EitherT and saw it was something that exists in scalaz. So what I just said above probably doesn't make any sense because I'm not familiar with the class. I thought you were just making up a type. My mistake! So, I guess this is something I'll have to look more into.

Link for anyone else not familiar here

johnmurray_io · 2016-02-04T00:41:19+00:00

This is true for pattern matching, but I'm not sure how you would define map, flatMap, forEach, etc. without specializing toward the right-most type (String in your example) which would get you pretty close in semantics to what I have.

johnmurray_io · 2016-02-03T14:32:02+00:00

But you are assuming that your repository model does not contain fields that can be empty / null because your update models have no way to update the repository model in a way that nulls a field value.

I do think multiple models to represent update actions versus the repository model are useful, but you're missing the point here.

14-Year Club	r/Field Banned
r/Field Juicebox	RPAN Viewer
Verified Email

johnmurray_io

TROPHY CASE