Clojurians Log v2
Clojure programming
Channels
Apps
ldnproclodo
https://github.com/ldnclj/meetdown & https://trello.com/b/AQfoh73C/proclodo-progressive-based-clojure-dojo
agile_geek 2016-04-19T16:28:55.000002Z
ProCloDo at CodeNode, SkillsMatter, starts at 6:30pm tonight.
2016-04-19T17:21:22.000004Z
👋
agile_geek 2016-04-19T17:41:56.000005Z
👋
agile_geek 2016-04-19T17:42:06.000006Z
Hi @otfrom
agile_geek 2016-04-19T17:42:21.000007Z
Just gathering..]
agile_geek 2016-04-19T17:42:35.000008Z
haven't done silly question yet!
agile_geek 2016-04-19T17:49:08.000009Z
Silly question is: Microservice or Monolyth?
2016-04-19T17:50:43.000010Z
that's a good one
2016-04-19T17:50:56.000011Z
or microlyth or monoservice
2016-04-19T17:51:08.000012Z
micormono or servicelift?
2016-04-19T17:51:24.000013Z
majordomo or service lift
agile_geek 2016-04-19T18:04:49.000014Z
No - Microservice or Monolyth!
agile_geek 2016-04-19T18:04:55.000015Z
You can't dodge it
agile_geek 2016-04-19T18:05:49.000016Z
Just talking about the format for the meeting.
agile_geek 2016-04-19T18:06:39.000017Z
I think the consensus is around deciding on discrete problems/issues to take away and tackle then coming back next month with a PR
agile_geek 2016-04-19T18:54:59.000018Z
Just demo'ing the app and walking thru structure atm
2016-04-19T19:58:14.000020Z
microservice
agile_geek 2016-04-19T21:00:59.000021Z
So I will write up my interpretation of the new format of ProCloDo and post it here and also add it to either the readme or the wiki in github when I get a chance
agile_geek 2016-04-19T21:04:02.000022Z
In the meantime here is a summary of the design decisions taken in this meeting:
agile_geek 2016-04-19T21:06:01.000023Z
1. Leave petrol as the cljs approach for now to maintain some stability in the codebase for a few months - to review at later date
agile_geek 2016-04-19T21:07:14.000024Z
2. Stick with the current 'post a map to a single uri' approach to server requests rather than REST for now. Again to maintain some stability in the code base.
agile_geek 2016-04-19T21:07:45.000025Z
3. Look to implement a few of the trello cards around functionality over next month.
agile_geek 2016-04-19T21:08:30.000026Z
4. implement authorisation and authentication over next month or so.