Closed ryanguill closed 9 years ago
Def the sort of feedback I want, Ryan. Nice one.
I'm in the middle of something right now, but will get back to you on these... food for thought, def.
Closing this one out.
I think the lifecycle stuff is covered in "Request/response process & scopes" & "Application framework" ?
Specifically not covering install. This is well documented already, elsewhere
Added email to the "MIA" section of the chapters page (others already added via other issues).
What do you think about moving TDD up to after "Components cont'ed"? Or maybe just after error handling (which is now chapter 8)
Have reordered chapters a bit: have a look.
Just some opinions - if this isn't the kind of feedback you're looking for let me know.
I would talk about scopes pretty early on - I definitely think you need to understand at least the broad strokes of scopes before talking about components.
I see advanced DB, is there a DB basics? Or are you intending to cover that at the same time as ORM?
Wouldn't you want to talk about TDD earlier? I would think its more important to talk about TDD than websockets or java interop.
websocket is one word.
Error handling should move up I think - perhaps after application framework? It might be a good chance to introduce it with DB concepts?
I'm not sure that it needs its own chapter and you may already have this covered, but thinking about my experience training people, one of the first things we talk about is validating data. Perhaps talking about that with the built-in types would be good.
Potentially missing items: email, cfhttp, debugging, downloading / installing / setup, discussion about lifecycle of webserver vs application server