Time |
S |
Nick |
Message |
11:13 |
|
|
pdurbin_m joined #sourcefu |
11:13 |
|
pdurbin_m |
It?s The Future - CircleCI: https://circleci.com/blog/its-the-future/ |
11:18 |
|
pdurbin |
bear: I assume you've seen that. Good stuff. :) |
13:47 |
|
|
John__ joined #sourcefu |
13:48 |
|
pdurbin |
John__: hi! So you're interested in design patterns and architecture? https://botbot.me/freenode/opensourcedesign/msg/71640981/ |
13:49 |
|
John__ |
Yeah, I'm looking for a few book recommendations on architecture/design patterns. Mostly related to "general" software design, rather than anything specific (yet). |
13:49 |
|
John__ |
Most of the books I came across discuss patterns on their own, rather than a whole project |
13:49 |
|
John__ |
or domains/components in a project. |
13:51 |
|
John__ |
I don't know what terms exactly to use to explain myself what I want, but if I were to use metaphors... the construction of a skyscrapper or a gym club is obviously a difference in architecture and purpose (same as software) |
13:52 |
|
John__ |
but the architecture of a house/building is still a house/building, so plumbing, electricity, foundation, etc are still integral things that all buildings share in common |
13:52 |
|
John__ |
I guess that's what I'm looking for. |
13:53 |
|
pdurbin |
John__: are you building a CRUD webapp? Or something more exotic like landing a rover on MARS? |
13:53 |
|
John__ |
Also, design decisions and style I suppose. |
13:54 |
|
John__ |
pdurbin, I'm not building anything at the moment. I'm just looking to explore what I have as options. |
13:54 |
|
John__ |
e.g What is out there? |
13:54 |
|
John__ |
What patterns/styles are at my disposal. |
13:54 |
|
pdurbin |
well, the architecture of a webapp is different than the architecture of a mobile game |
13:55 |
|
John__ |
pdurbin, indeed, yet they both will end up sharing common components, such as a database |
13:55 |
|
John__ |
or a service layer. |
13:55 |
|
pdurbin |
yeah, good point |
13:55 |
|
pdurbin |
point* |
13:57 |
|
pdurbin |
anyway, gotta drive to the airport. see what aditsu bear dotplus prologic semiosis and sivoais think |
14:02 |
|
John__ |
pdurbin, thank you. |
14:03 |
|
|
Boobie joined #sourcefu |
14:03 |
|
|
Boobie left #sourcefu |
14:04 |
|
aditsu |
I'm usually the wrong person to ask about books :p |
14:04 |
|
aditsu |
pdurbin: going on a trip? |
14:05 |
|
aditsu |
I've been back to Romania recently |
14:05 |
|
John__ |
aditsu, te salut :P |
14:05 |
|
aditsu |
John__: salutare :) |
14:07 |
|
aditsu |
I have a book called "head first design patterns" but I suspect it's not really what you're looking for |
14:08 |
|
John__ |
aditsu, yeah, I have that as a pdf. It will be something I'll look into though. |
14:08 |
|
John__ |
Unfortunatelly it only discusses patterns, in an isolated manner. |
14:09 |
|
John__ |
aditsu, if I were to throw out a few terms (since I am somewhat lost in the domain of architecture), I'm looking for..... |
14:10 |
|
aditsu |
...software engineering books? |
14:10 |
|
John__ |
service layers, models, DDD, middleware, crosscutters, business layers, N-tier architecture, layered architecture, principles of architecture, etc. |
14:10 |
|
John__ |
aditsu, yeah, lol :P |
14:11 |
|
John__ |
I guess.... but not one that discusses the SDLC :P |
14:11 |
|
John__ |
or Quality Control |
14:11 |
|
John__ |
or some ISO standard. |
14:11 |
|
John__ |
API construction is also something I'm interested in. |
14:14 |
|
aditsu |
I'd rather get my hands dirty coding stuff than spend time reading books, but some books are useful too |
14:15 |
|
aditsu |
also my general impression is that people still haven't figured out the best ways to build things, that's why there are so many competing frameworks and paradigms |
14:15 |
|
John__ |
aditsu, I think that'll only work if you're getting into something concrete. I doubt you can learn architecture by coding, because it's more "paper" kind of thing, you know? |
14:15 |
|
John__ |
yeah, I understand. |
14:15 |
|
aditsu |
you can learn some things from experience, and also from working and discussing with others |
14:17 |
|
John__ |
mmmm |
14:19 |
|
aditsu |
but I understand that a good book can potentially save you a lot of trouble |
14:20 |
|
John__ |
aditsu, it's more "discoverability" and "structural" issues that I hope it will solve. |
14:21 |
|
John__ |
aditsu, which is something code alone won't solve :) |
14:21 |
|
John__ |
unless code examples are given :D |
14:29 |
|
John__ |
aditsu, thanks by the way, I appreciate the help, I'm sorry if I'm taking your time or I'm just being very vague ;/ |
14:29 |
|
John__ |
I admit, I somewhat am not fully sure what I'm exactly looking for. |
14:31 |
|
aditsu |
no worries, sorry I probably can't help much :p |
15:33 |
|
|
pdurbin_m joined #sourcefu |
15:34 |
|
pdurbin_m |
aditsu: yeah, I'm bringing my kids to my parents' house then flying home. Kid free for over a week! |
15:34 |
|
aditsu |
sounds great :) |
15:34 |
|
pdurbin_m |
hope you had a good time in Romania. it's been a good summer for us |
15:35 |
|
pdurbin_m |
John__: you mentioned getting into something concrete. what would that be? what are you building? |
17:48 |
|
|
John__ joined #sourcefu |
22:18 |
|
|
bear joined #sourcefu |
22:37 |
|
sivoais |
you need to do the reading and coding in parallel. As you create, you come across the problems you need to solve and discover the terminology to solve those problems. |
22:37 |
|
sivoais |
trying to design everything up front leads to too many blindspots |
22:38 |
|
sivoais |
There is a series of books called Architecture of Open Source Applications. All available at <http://www.aosabook.org/> |
23:30 |
|
|
aditsu_ joined #sourcefu |