These are chat archives for petabridge/akka-bootcamp

22nd
Feb 2015
Ralph Willgoss
@ralphwillgoss
Feb 22 2015 18:25
Thanks for the time you put into this, looking forward to getting started
Aaron Stannard
@Aaronontheweb
Feb 22 2015 18:26
glad to hear it!
please ask any questions you might have while doing it in here
:)
patrichua
@patrichua
Feb 22 2015 18:41
I started Unit 1 - lesson 1 last night. So far, so good. Thanks for putting this together.
Aaron Stannard
@Aaronontheweb
Feb 22 2015 19:15
@patrichua senor @skotzko and I are happy to do it - we figured that there are a lot of developers who could use something like this
and it was fun for us to make
Rob van der Linden Vooren
@robvdlv
Feb 22 2015 20:40
yeah thanks for putting it up
good kickstart to get a feel of the project
tchrikch
@tchrikch
Feb 22 2015 21:14
just finished 1st unit and it looked great ! Really amazing work to put it all together ,thanks guys !
Aaron Stannard
@Aaronontheweb
Feb 22 2015 21:15
@tchrikch :heart: thanks so much! We love to hear it!
and anytime @robvdlv - we're glad to do it
Steven Wilber
@stevenwilber
Feb 22 2015 21:51
Woohoo! Just started. I'm so excited to see so much help and documentation for an opensource project. "Props" (pun intended) to all you guys.
Andrew Skotzko
@skotzko
Feb 22 2015 22:08
Thanks! Any questions/anything we can help with?
Jorge Fioranelli
@jorgef
Feb 22 2015 22:09
Guys, the bootcamp looks great!!! Are you interested in having an F# version? I can create a branch and start working on that if you want...
Ralph Willgoss
@ralphwillgoss
Feb 22 2015 22:11
I like the approach where we have to copy and paste a line, after reading what that line does. The technique works well for learning as you go.
Aaron Stannard
@Aaronontheweb
Feb 22 2015 22:22
@jorgef absolutely - we'd love an F# version of bootcamp
only reason we didn't do one is just because neither @skotzko nor I are all that experienced with F# yet :\
Jorge Fioranelli
@jorgef
Feb 22 2015 22:25
@Aaronontheweb nice, I am happy to contribute! do you think the best way is to create a separate 'fsharp' branch with its own instructions and code? or do you prefer to have both languages in the same branch (with C# and F# snippets)?
Aaron Stannard
@Aaronontheweb
Feb 22 2015 22:26
what I would do is add a new layer of folders inside each unit
Unit-1/CSharp Unit-1/FSharp
all of the explanatory content in the READMEs should be nearly identical
just need to change the code parts
Jorge Fioranelli
@jorgef
Feb 22 2015 22:26
yep, agree
Aaron Stannard
@Aaronontheweb
Feb 22 2015 22:27
I can create a new FSharp branch
and we can send PRs for translating individual lessons to that
once we have Unit-1 ported I'd bring it into master
Jorge Fioranelli
@jorgef
Feb 22 2015 22:27
sounds like a plan
Aaron Stannard
@Aaronontheweb
Feb 22 2015 22:27
cool, I'll create that branch now
Jorge Fioranelli
@jorgef
Feb 22 2015 22:27
I will work on that during the following days
Bartosz Sypytkowski
@Horusiath
Feb 22 2015 22:28
@jorgef if you'll need some explanations according the F# API, I'll be happy to answer any questions
Steven Wilber
@stevenwilber
Feb 22 2015 22:36
I'm just finishing lesson 2 of unit 1 and I have a minor comment which is that it seems to be inconsistent where the writer is informed of what to write, which confused me initially. If there is an error, the reader tells itself via a message and it handles the message by telling the writer. However, if the input is valid, then the writer is told directly in the validation code. To me it feels a little inconsistent. Maybe this gets picked up down the line as I can imagine that I'll be drowning in messages in a larger project and knowing where and when one actor talks to another could make things easier. Anyway, just a thought.
Aaron Stannard
@Aaronontheweb
Feb 22 2015 22:38
@stevenwilber what we tried to do there is eventually set you up to decouple validation from reading and writing from the console
we always try to end the lesson with something that compiles and runs, so it can be a bit jarring to write things one way and immediately rewrite it in the next lesson
so that's a good point - I wonder how we can make that easier. Maybe just by providing an explanation like this? "We're going to have you rewrite some stuff so we can begin decoupling these actors"
would that help?
Jorge Fioranelli
@jorgef
Feb 22 2015 22:40
@Horusiath thanks, will look into that
Steven Wilber
@stevenwilber
Feb 22 2015 22:50
@Aaronontheweb - I personally wouldn't communicate with the writer in the validation code. The validation code was not there in lesson 1 and communication between the reader and writer was done in the receive method of the reader. This is still done in lesson 2 for invalid messages, but now a new communication between the reader and writer is done for valid messages within the validation code. I personally would let the validation only validate and let the reader know the results of the validation which it can then inform to the writer in the usual way. As I say, however, you may get to that later on. Don't take this as a big negative, it was just a thought and I really appreciate the work that you've put into this. I'm super impressed.
Aaron Stannard
@Aaronontheweb
Feb 22 2015 22:56
@stevenwilber it's great feedback Steve - I appreciate i
it*
Ralph Willgoss
@ralphwillgoss
Feb 22 2015 23:02
why the re-enforcement in unit1/lesson 3 on using Props.Create(typeof(ConsoleWriterActor)) when you said don't and then at the end of the lesson changing it?
Jorge Fioranelli
@jorgef
Feb 22 2015 23:49
@Horusiath I checked the F# API and it looks awesome. It is great you can spawn actors like that, but I was thinking to keep the project structure similar to the C# one (one actor per file), how would you suggest to do it? Do you have an example for that? Would you create a ConsoleWriterActor module with a 'receive' function on it?