Regarding MH's Auction System

Replies to this thread go here.

I want you to have some context.

This system is pretty complicated. It is important to know, it has TONS of code that is necessary, but you won't need to worry about until after you are comfortable finding your way around the app in the browser and where the controllers and views are for all the screens you see.

Controllers and Views?
This system is an MVC system. That means it is built with "models", "controllers," and "views."

One of the good things about this is that for programming, you can do everything you need by working only with the controllers, models and views. For now, you can forget about models. That leaves controllers and views. Most of what we do for MH is in the auctions controller. Controllers do all the work of gathering and organizing data so it can be displayed on a web page. Then, the controllers send that data to views, which are where this system's templates are.




What Are All Those Other Files For?
The rest of the files provides the architecture that makes it possible to simplify programming to the point where all you have to work with is in the MVCs.

This is an Example of Part of the Secret Sauce
I am sure I have tried writing about this part of the secret sauce before, but now I think it might mean more. Part of the secret sauce is to use application architecture that makes programmers jobs easier and uniform. The MH auction system could be cloned and then by working only with the MVCs, you can build any other website possible. If you did not have the architecture, you would have to find ways for connecting the to the database, sending email, uploading files, to parse urls that have been made search engine friendly. You would need to organize your own way of using templates.

What Is This Architecure? Is it just the idea of MVC?
This architecture is provided by an open source system called CodeIgnitor. This is basically a codeignitor system.

As you find yourself curious, you will be looking through all the directories to see what is going. Overall, it is pretty complicated. The secret sauce says, "You cannot spend time to understand all of it, because it is not economical to put that much time into understanding CodeIgnitor. CodeIgnitor is an architecture we inherited with MH auction, it is a good system have experience with. However, OUR architecture, the one we are going to need for software we make, will not be this one. It might be an MVC system. It might even end up being based on CodeIgnitor, because CI is a generic MVC architecture with the object-oriented approach I am now nearly sure we should adopt. Our architecture will have a level of detail CI does not have and it will have innovations that only we will have. As it develops, our architecture is one we all will need to master in all the detail possible.

At The Core of the Secret Sauce
Bad metephor, because sauce does not exactly have a core, but ....

As you familiarize yourself with this system, the main thing for you to know is there is a lot of stuff we need that programmers have the luxury of not having to worry about, and cannot afford to learn. That works only when there is a tech person taking care of that stuff, which now is me and in time will become you and after that, others will replace you. This march of "programmer only" simplified by programmer graduated to tech, who makes the simple words for programmers, and then graduates to project management is the narrow path to success we must take. Your job now is to program. Program. Program, program, program.

My job is to make it possible for you to do that, so you can deliver finished products to our clients, with minimal experience. High value products from beginning programmers. That is our leverage we must develop ruthlessly.

 

I want you to have some context.

This system is pretty complicated. It is important to know, it has TONS of code that is necessary, but you won't need to worry about until after you are comfortable finding your way around the app in the browser and where the controllers and views are for all the screens you see.

Controllers and Views?
This system is an MVC system. That means it is built with "models", "controllers," and "views."

One of the good things about this is that for programming, you can do everything you need by working only with the controllers, models and views. For now, you can forget about models. That leaves controllers and views. Most of what we do for MH is in the auctions controller. Controllers do all the work of gathering and organizing data so it can be displayed on a web page. Then, the controllers send that data to views, which are where this system's templates are.




What Are All Those Other Files For?
The rest of the files provides the architecture that makes it possible to simplify programming to the point where all you have to work with is in the MVCs.

This is an Example of Part of the Secret Sauce
I am sure I have tried writing about this part of the secret sauce before, but now I think it might mean more. Part of the secret sauce is to use application architecture that makes programmers jobs easier and uniform. The MH auction system could be cloned and then by working only with the MVCs, you can build any other website possible. If you did not have the architecture, you would have to find ways for connecting the to the database, sending email, uploading files, to parse urls that have been made search engine friendly. You would need to organize your own way of using templates.

What Is This Architecure? Is it just the idea of MVC?
This architecture is provided by an open source system called CodeIgnitor. This is basically a codeignitor system.

As you find yourself curious, you will be looking through all the directories to see what is going. Overall, it is pretty complicated. The secret sauce says, "You cannot spend time to understand all of it, because it is not economical to put that much time into understanding CodeIgnitor. CodeIgnitor is an architecture we inherited with MH auction, it is a good system have experience with. However, OUR architecture, the one we are going to need for software we make, will not be this one. It might be an MVC system. It might even end up being based on CodeIgnitor, because CI is a generic MVC architecture with the object-oriented approach I am now nearly sure we should adopt. Our architecture will have a level of detail CI does not have and it will have innovations that only we will have. As it develops, our architecture is one we all will need to master in all the detail possible.

At The Core of the Secret Sauce
Bad metephor, because sauce does not exactly have a core, but ....

As you familiarize yourself with this system, the main thing for you to know is there is a lot of stuff we need that programmers have the luxury of not having to worry about, and cannot afford to learn. That works only when there is a tech person taking care of that stuff, which now is me and in time will become you and after that, others will replace you. This march of "programmer only" simplified by programmer graduated to tech, who makes the simple words for programmers, and then graduates to project management is the narrow path to success we must take. Your job now is to program. Program. Program, program, program.

My job is to make it possible for you to do that, so you can deliver finished products to our clients, with minimal experience. High value products from beginning programmers. That is our leverage we must develop ruthlessly.