| | |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Technology & Technical Skills Computer skills, hardware, software, internet topics, gadgets, programming |
|
Welcome to the Personal Development for Smart People Forums, the place for lively, intelligent discussion of all personal growth issues -- physical, mental, financial, social, emotional, spiritual, and more. You're currently viewing as a guest, which gives you limited read-only access. By joining our free community, you'll be able to post your own messages, access many members-only features, see the new messages posted since your last visit, and of course remove this header message. Registration is fast, simple, and free, so please join today. If you arrived here from a search engine, you may want to explore the main site first, which includes hundreds of deep and insightful articles on a variety of personal development topics. |
| | Thread Tools | Display Modes |
| |||
| Hi there everyone, I hope there are a few programmers out there who can relate to this question and give some advise! I just got handed an application that is in the beginning stages of development. It is a php application based off the Zend Framework. I need to learn what is there so that I can start adding features based loosely off some design documents from a couple of years ago. What techniques would you use to quickly digest the basic workings of a large source code base?
__________________ ~Lauxa~ |
| |||
| If the code is documented or uses some auto documentation, that would be where I would start reading. I think I would try to read it in the order it executes. Start with the index.php, see what functions it calls and so on. I've set-up a webshop using Joomla and VirtueMart, where I had to modify a lot of code and add some of my own plug-ins, but I mostly did these one at a time. Figuring out where and how the part of the code that needed fixing/modifications worked, and fixed that. Then moved on to the next problem. Eventually I began getting a little familiar with the code, how they did things and where to find stuff, but I must admit it was a rather painful experience. |
| |||
| First figure out if it's object oriented or straight code. If it's OO, a sweet editor like intelliJ will help wonders. You'd need a PHP plugin for it. It looks like some are in development. Some kind of IDE/editor which helps you look through the code is best if you don't have a lot of time to inspect the code yourself.
__________________ --There's nowhere to go, nothing to do. My blog which I haven't updated in a long time. |
| |||
| I usually play around with the system to get a feel for it. Then I look for parts that are crucial that will help me understand how things are connected. When I'm ready to look in the code, I pick a specific major feature to look out for and try to think about how I would program it. Almost every time, the way it is programmed is similar to what I envision, and so it really helps me identify key code structures pretty fast. After that, it's a matter of bouncing around to whatever interests me. |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
| |
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| part of source or source itself? | wolfgang | Erin Pavlina | 1 | 03-27-2008 02:28 PM |
| The Genius Code | tbushmoney | Personal Effectiveness | 1 | 01-17-2008 09:29 PM |
| How to sell source code? | dci0705 | Technology & Technical Skills | 2 | 11-28-2007 06:58 AM |
| Is there a code of ethics for psychics? | Aphrodite | Erin Pavlina | 2 | 04-09-2007 07:32 PM |
| html help webpage code | MattUK | Technology & Technical Skills | 3 | 11-20-2006 01:18 PM |
All times are GMT. The time now is 11:33 PM.

