Question for all coders - Where to start

Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy.
This forum is not for asking programming related questions.

Moderator: General Moderators

Post Reply
anand
Forum Commoner
Posts: 80
Joined: Fri May 22, 2009 11:07 am
Location: India
Contact:

Question for all coders - Where to start

Post by anand »

hello guys, I am planning to work on my own .com startup. I know PHP, MySQL, JavaScript and HTML (little bit of CSS as well). Till now the only thing I have ever done is helping my friends in modifying their PHP code and modifying/making version 2 of many sites

But now I want to code my own website. The problem I am facing now is, Where to start? What should I do first? HTML? PHP? Database Schema design? I am confused on where to start the thing?

One more problem I am facing is lack of confidence. I have done a lot of work on PHP for almost 6 months but still I feel like i know nothing and its impossible for me to code an entire website.

need advice from all you senior coders on how to tackle this problem.
User avatar
Weirdan
Moderator
Posts: 5978
Joined: Mon Nov 03, 2003 6:13 pm
Location: Odessa, Ukraine

Re: Question for all coders - Where to start

Post by Weirdan »

anand wrote:But now I want to code my own website. The problem I am facing now is, Where to start? What should I do first? HTML? PHP? Database Schema design? I am confused on where to start the thing
I'd suggest starting with a list of features you want to implement - so you would know what you aim is. Then I'd go with a semi-detailed interface mockup - it helps to evaluate features and see how it looks like from the user's point of view. Once you have the interface you may start writing acceptance tests for it and detailing the requirements (writing user stories). I guess you will know what to do next when you reached this stage. At least you will know what you want to build exactly which is huge bonus by itself.
anand
Forum Commoner
Posts: 80
Joined: Fri May 22, 2009 11:07 am
Location: India
Contact:

Re: Question for all coders - Where to start

Post by anand »

Weirdan wrote:I'd suggest starting with a list of features you want to implement - so you would know what you aim is. Then I'd go with a semi-detailed interface mockup - it helps to evaluate features and see how it looks like from the user's point of view. Once you have the interface you may start writing acceptance tests for it and detailing the requirements (writing user stories). I guess you will know what to do next when you reached this stage. At least you will know what you want to build exactly which is huge bonus by itself.
Good Point. So, you are advising me to first make a list of all the feature and also make a list of all the resources I need to build those features.

right?

Thanks for your reply though.
User avatar
jayshields
DevNet Resident
Posts: 1912
Joined: Mon Aug 22, 2005 12:11 pm
Location: Leeds/Manchester, England

Re: Question for all coders - Where to start

Post by jayshields »

You might want to look into the software development life cycle for the basics. Weirdan was describing some aspects of a software development methodology know as an Agile method (user stories, etc.).

I usually start with a features list. Then jump right into some basic HTML/CSS for the interface. Then the database schema. Then the PHP coding. Then spruce up the interface with some JavaScript and what-not.
l.francis30
Forum Newbie
Posts: 12
Joined: Tue May 19, 2009 11:27 am

Re: Question for all coders - Where to start

Post by l.francis30 »

Weirdan wrote:
anand wrote:But now I want to code my own website. The problem I am facing now is, Where to start? What should I do first? HTML? PHP? Database Schema design? I am confused on where to start the thing
I'd suggest starting with a list of features you want to implement - so you would know what you aim is. Then I'd go with a semi-detailed interface mockup - it helps to evaluate features and see how it looks like from the user's point of view. Once you have the interface you may start writing acceptance tests for it and detailing the requirements (writing user stories). I guess you will know what to do next when you reached this stage. At least you will know what you want to build exactly which is huge bonus by itself.
I like your suggestion.. List all features and then create a storyboard for your website..
Post Reply