Re: advise on best practices guides and projects
tom forsmo wrote:
But I feel those books in many respects are too high level for my
problems. They tend to aim for architectural issues instead of practical
OO programming. What I am looking for is on a lower level, i.e. more
conventional OO programming idioms and so on.
Huh. After reading through the Head First Design Patterns book, I got
the exact opposite impression. Design patterns are very small scale,
tactical bits of software. Sure, knowing about them influences your
overall design because you want to take advantage of handy bits, but
thats true of any design that reuses bits.
If you'd like to talk about one or two patterns from that book (because
I have the same book and I could refer to it) we could talk about, maybe
have some other folks chime it.
Oh, and don't mind Lew, he's like that to everyone.
I usually code store-and-retrieve servers connected to an sql database.
There usually isn't much domain logic, but there is some data model
conversions and all the stuff needed for technical reasons, such as
This I don't have much practical experience. Maybe if you described a
bit more though we could try to shed some insight. It sounds to me
though that you're working at a level where the actual design is
minimal, and you could (and probably should) be using as many automated
tools as possible.
I'm my limited experience, that's a big reason for those "extra" layers
to exist. They are understood by, and possibly generated by and
maintained by, automated code systems.