How can I learn practical applications of software engineering principles?

Question

I'm having problems bringing the software engineering I learned in school into my projects at my job.

The patterns are all easy enough to apply, but coming up with architectures and general class structures is tough for me. It's so open ended and I never know how to approach my projects, with the exception of any project that cleanly fits the MVC architecture.

I've been working on some increasingly larger projects. The end product works because I know testing well, but getting there is hell and going back to add features is worse. My work usually degrades into planning from the applications entry point and thinking through the use cases. This works eventually, but I end up with low cohesion and tightly coupled code. I had enough experience coming out of school to start in a job with more responsibilities than entry level programmers, so I don't have the benefits of learning from a more experienced team.

The problem is I'm very inefficient. My boss said once that if I get these projects out faster and with the same level of testing I can make more.

So I have to teach myself software engineering. I've read a lot of books, but they are a little too abstract; I need something concrete. Where should I go to learn real project software engineering?

EDIT: It may help to know that I sometimes end up with clean code. It either just takes me a really long time to get there, or I give up and hack it cause I know it will work. Most people will say this comes with experience, but there must be some place I can go that says: if your project is like this this and this, try these architectures.

Answer 1

Buy a book.

Patterns of Enterprise Application Architecture.

You might also want to start using the Seperated Interface Pattern together with an inversion of control container since it forces you to decouple your code.

Working against interfaces also makes unit tests a lot easier and to refactor parts of your code.

Answer 2

I had enough experience coming out of school to start as a Sr. level programmer (after all, a lot of older sr. level programmers don't know this stuff), so I don't have the benefits of learning from a more experienced team.

I completely and wholeheartedly disagree with what's being said here. The exact problem you're describing is one in which you just need experience. You may be a talented developer, you may have a lot of modern and updated skills, but "senior level" is a measure of experience.

The problem is I'm very inefficient.

This is because you're relatively new to the trade. Nobody comes out of school as an expert. There are things you can't learn in school and can learn only from years of experience. You're going to write some bad code along the way. We all do. You're going to learn those lessons. This is fine. Having learned those lessons is what makes a developer "senior level."

For example, take a look at the industry-accepted design patterns in the gang of four book. These weren't written as an academic exercise. They weren't written because the people who wrote them were smarter than other developers. They were written because people spent years in the industry solving problems and improving their craft, eventually arriving at re-usable patterns.

You have to go through the same thing. There's a lot of industry knowledge already laid out that you can learn, but don't expect to be an expert right away. Skill takes time.

Answer 3

I had enough experience coming out of school to start as a Sr. level programmer

I am not sure if this is your ego running away with your common sense or if you are just being naive? Maybe both. Learning academic principles is completely different than actually living through a situation where a good process clearly helped you or the team or an anti-pattern cost you dearly. You realistically don't know and can't claim to be an expert at anything.

My boss, being pretty savvy, knew this and hired me in between entry level and sr level pay

This sounds terribly conceited... please consider revising this.

Where should I go to learn real project software engineering?

Your there. Real software engineering isn't anything like what you experienced in Academia, it is the process of engineering software in conformance with good practices, standards and quality to solve real world problems.

This does not include pontification on the pro's and con's of Djikstras algorithm for a few milliseconds of performance, nor other various academic forms of mental masturbation. You need to learn through direct experience what things work, what things don't work, and what can be done with limited resources and time.