This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-16
Channels
- # admin-announcements (27)
- # beginners (17)
- # boot (216)
- # cider (13)
- # cljs-dev (4)
- # clojure (103)
- # clojure-berlin (2)
- # clojure-dev (18)
- # clojure-italy (14)
- # clojure-japan (1)
- # clojure-nl (4)
- # clojure-norway (1)
- # clojure-russia (8)
- # clojurescript (291)
- # clojurex (12)
- # datomic (31)
- # editors (1)
- # events (16)
- # hoplon (60)
- # jobs (1)
- # ldnclj (85)
- # luminus (15)
- # onyx (2)
- # re-frame (18)
- # reagent (36)
- # remote-jobs (3)
- # yada (3)
..and in that spirit, Good Morning UGT…and DST 😄
Hello.
so, these Dojos. What's the dealio. Everybody just gets together and bashes out code with beer and pizza?
Exploring running NodeJS from Clojure: http://stackoverflow.com/questions/32607089/how-should-i-run-nodejs-from-a-java-application
xlevus: people tend to work on one or two different problems, dividing into groups and several groups working on the same problem. (this is an aspect of dojos that I’m not a fan of)
xlevus: you only need one laptop per group, plenty of people don’t bring a laptop or don’t have a Clojure environment ready.
Oh, groups tend to be three or four people.
I’d love to have a dojo-like environment but to pair on whatever you want to work instead of the two problems of the day.
I’m always working on one lib or another I could use help with, or I’m happy to help someone else with their thing and learn something new in the process.
well, you still can no? if 2 persons want to work on something together you’re free to do so
quentin: that goes against the spirit of the dojo and my proposal to do that were frowned upon. I did it once but just because the three people that randomly ended in my group didn’t feel like working on the main problem and liked an alternative one. It was a lot of fun, but just chance.
And it was also productive, as it ended up being pull requests for Luminus and Korma.
mayhaps I will come to the next one then. I had been meaning to, however many months ago, then I moved, and then my laptop died.
quentin: I’d be happy to attend that one, but I don’t have a space to host.
if I find a solution I will let you know I like having different practicing contexts, especially since I don’t have the opportunity to do clojure at work
xlevus: that one is working on one and only one practical problem over a long period of time, building something.
I enjoy the fact that we are building a real application so it’s not just a toy problem, but we are thinking of deployment, maintainability, usability, etc. At the first one, I decided to tackle server side pre-rendering of single page applications which resulted in this: https://carouselapps.com/2015/09/11/isomorphic-clojurescriptjavascript-for-pre-rendering-single-page-applications-part-1/
Ok, gym time. BBL.
@pupeno @quentin I don’t see you bringing you’re own problems to Dojo’s being frowned upon. I suggest you do that at next USwitch/Thoughtworks dojo and I’ll work with you 😉
and i think that could help reduce the issue of “starting from nothing on a new lib that nobody knows” since you could have the project initiator able to “drive” the project
@quentin: lets do it (as long as you port it to cljs!)
@agile_geek: to be fair, doing this is not very dojoist, so, I understand.
I’d like to keep the ProCloDo (at Salesforce towers) working on the Event Management project for now but can definitely do it in other Dojo’s.
@quentin: what’s your music tool?
@pupeno we just need to vote for it in enough numbers!
@agile_geek: what do you mean?
@pupeno ppl suggest experimenting with libraries etc. in Dojo’s all the time. We could suggest working on your projects and see who votes for it
@quentin: I haven’t worked on anything music related since I built this http://scret.sourceforge.net/ so, it could be fun.
@quentin: I reckon loads of ppl would vote to work on your music project
@agile_geek: but that’s the problem, what I want doesn’t to go well with the voting system. Let’s say I want to pair with something in making Nashorn-based server side rendering into a library. Most likely nobody will vote it, because most of the information for that is in my brain so other people won’t find it as interesting/productive, but if they do, then we’ll end up with three groups of three people of which only one contains me and the other two will be at a serious disadvantage by not having this information on their head. This would be the same for @quentin, only him knows what “@quentin’s music project” is, so other groups would be wasting their time.
@pupeno: I see your point, it works if the group is 3-4. Could use a big screen and ‘mob’ on it but I think that would dissolve into chaos.
Hmmm…thinks
This is what I would like:
You write what you want to work on and your name on the board and then people can propose working with you if they are excited about the project. Otherwise, you work on your own or you join someone else’s project.
There’s a risk of everybody working individually or not having enough projects, but there are a few generic projects that can be thrown in to solve the latter (pick a bug from a library and solve it… hey, even clojure and clojurescript have bugs that can be tackled).
It could even be run parallel to a dojo.
And I’m happy to stand up and manage the board for this, I just can’t organize a dedicated event.
maybe we should put it on the google group as a more persistent discussion. Could help to find place to host this (parallel to a dojo or dedicated event if someone can organize)
Why not talk to organisers of two current dojo’s about doing this every 2 or 3 dojo?
I’m happy to do it in gaps between projects in ProCloDo 😉
i cleaned up the code of the space invaders project started at the dojo. Feel free to suggest improvements etc, I am really interested to get feedback https://github.com/qleonetti/clojure-dojo-invaders
Anyone here any luck with Yada @jonpither @malcolmsparks maybe?
@thomas i'm using yada
hi @mccraigmccraig any luck with it? I tried the example... but getting errors
Weee! I got nodejs to run.
yeah, it's mostly working great, though cors & auth are a wip
@thomas i remember the routing was a bit difficult to get right... i'll have a look at your example in the morning and compare to my working code