Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial


Chris Collier
Chris Collier
17,774 Points

How much of configuration files do you remember?

This is a general question for more experienced programmers: I'm noticing a recurring theme in learning programming, especially Java frameworks, that there is some configuring to be up front to reap the benefits. I get frustrated because the configurations don't stick with me the way other language concepts do, and I'm wondering if that's a problem?

A great example is the Hibernate course I'm taking now. The instructor goes into an aside about inner static builder classes, and I really got that concept as an abstract, and can see how it extends naturally from how classes are formed - I'd say a large portion of that stuck with me in the first go through. In contrast, I didn't retain any of the initial setup stuff for Hibernate itself. Is a SessionFactory built by initializing a ServiceRegistry and passing that to a MetadataSources object? Sure, I guess, but I don't know how you would know that besides memorizing it. Obviously you'll get it after 100 times, but as an experienced programmer, are you saving boiler plate files of configurations when you work with a new framework? Or do you pour over how the various objects chain together before moving on to the "fun" parts? Or is it somewhere in the middle?

Thanks in advance for your advice Chris

1 Answer

Chris Jones
.a{fill-rule:evenodd;}techdegree seal-36
Chris Jones
Java Web Development Techdegree Graduate 23,933 Points

This is actually something that a friend and I discuss in the Java web dev tech degree. We both dislike the configuration of projects and have come to the conclusion that you just have to memorize it - at least for now. We both look back on our previous projects to see how we did configured similar projects.

We've both agreed that while configuration is technically programming, configuration doesn't allow much creativity - there seems like there is mostly one or two ways to do something. After you've got the configuration set up, the fun, creative part begins :).

I'm definitely curious what Craig Dennis or another teacher thinks on the topic, though!

I hope that helps!