Clojurians Log v2

https://drive.google.com/file/d/1ZL98EAJZVTZILz96em1PfhrvCWFFd8Yv/view?usp=sharing

I am currently trying to draw what I have in mind

s/independant/independent/

lol

okay boss

French slip

@viesti used to call me Master :-)

😂

I won’t go this road 😂

and for your information, I had 6/20 at the french exam (bac)

thank god science exist

In engineering prep school, you should have seen the face of the teacher melt down as I spoke. “From your written exam I thought you were bilingual.” (Said written exam was mostly a translation to French, exercise which was my forte.)

ahah, common problem indeed

anyway do you have any feedbacks on the “vision” that I shared ?

before I draw some stuff

I would add “leverage clojure way of things”

in which way ?

Spec to document shapes.

https://drive.google.com/file/d/1ZL98EAJZVTZILz96em1PfhrvCWFFd8Yv/view

what are the data ?

'hmm... Master' I think was the particular line I used (leaving out the actual circumstance for not spoiling it) :)

spoiling: if I recall, I was making a PR for a branch in powderkeg and sent the PR towards master and after realizing it, there was ‘hmm master’, which is a fine line to receive as slack notification 🙂

great statement of thoughts 👍

Thinking that this spec generation has similarity to F# type providers (https://docs.microsoft.com/en-us/dotnet/fsharp/tutorials/type-providers/, haven’t done F# but the type provider sounded like a neat idea when I heard about it some time ago). Generating parsers/serializers and clients/servers is I guess a thing; remembered wsdl, and IDL in general. Just that concretely, we’r doing this for AWS and for Clojure now, for a set of APIs that are built in the internet style, and not with a style in which one starts with IDL first.

random thoughts before going to bed 🙂

I’ll read it tomorrow

I am trying to step back right know by drawing the overall softare architecture of what we are trying to do

I think we are not far from finding a great path to success