Help needed!

Hey /prog/, I know you don't like this, and neither I do, but could you point me at some ENTERPRISE software engineering tutorials? You know, like, explaining how do I organise my thousands of classes, where do I put them, how do I name the folders, how do I use Ninject/Moq/NHibernate/EF/whatever etc.

Thanks :3

welcome to the world of java hell

In Java:

create a project with Maven, and 4 folders:

src/main/java
src/main/resources
src/test/java
src/test/resources

Inside src/main/java create your package structure. How your organize your packages is totally up to you, but most of the time there are packages for basic entities (POJO), another for DB access, and another for controllers.

src/test/java should have the same package structure than src/main/java

>>3
Thanks, but are there things like this for C#?

Well, even project names would be helpful! I'm completely out of ideas how to google this shit, and stackoverflow guys doesn't seem to like these questions.

>>5
s/doesn't/don't

>>4
What I do is to create a New Project that has a skeleton that works for me, and supports the main features of my app. Then i start working over there.

Just start creating New Projects until you have one that fits your needs. Those usually have a basic structure with the best practices.

>>7
A new project comes with App.config, App.xaml and a view. No folders at all, and nothing else. What I'm having now is:


EnterpriseApp.Domain
|
|--Abstract - DB interfaces
|--Concrete - DB interface implementations
|--Entities - POCO

EnterpriseApp.Tests
|
|--a bunch of test files

EnterpriseApp.GUI
|
|--Models
|--ViewModels
|--Views
|--Infrastructure - Ninject shit
|--App.xaml, App.xaml.cs - application entry points

I've stolen this tree from a book, but I'm not really sure how do I glue all this together, and how do I add something new to it.

I've read somewhere it's common to start building this crap without GUI, but I can't recall where. Maybe this could help me. Uh, I certainly haven't been born an ENTERPRISE software developer.

>>4
C# is surely good, but is it Java good?

>>8
you should not  need anything more. all is covered in that project skeleton.

start working in your POCOS, then define an API to store/read them from a database, then the implementation for each interface.

Now start working in the tests. Write a lot of them testing your POCOs and you implementation.

When you are satisfied with the quality of your basic classes, write some GUIs for them.

Write your GUIs late, in that way you won't succumb for the temptation of testing your prpgram yourself through the forms and webpages. That is pure mental masturbation.

>>10
you got something against mental masturbation, puritan?