Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

A Matter Of Experience

Status
Not open for further replies.

sabavno

Programmer
Jul 25, 2002
381
CA
Hi!

Question is totally out of this forum's coverage...

How long do you think it would (should) take a inexperienced programmer (a student) to develop a professional order/tracking system for a few asset kinds.

System would is not client/server, but it does deals with some of the SQL tables.


HOW LONG? REASONABLY?

Looking forward to hearing your opinions

Thanks a lot
 
Hmm... this is a tough one... I was put into an access programing developing position about 5 months ago, this is what i do for about 6 hours a day... and i would still have a hard time to get a good database up and running... i have had a mild programming back ground... so if your a student, you have more resources then i did... so i would have to say, it's taken me almost half a year to learn access enough to be able to do what you're asking...

Now, beond that, It realy depends on the person... I did alot of research on this forum, and in a few books, plus a friend of mine was a good vb programmer... So I was able to do what i needed to when i needed to...

I wish i could help more then this...

--James
junior1544@jmjpc.net
Life is change. To deny change is to deny life.
 
IMHO it shouldn't take any time at all, as an inexperienced programmer would not be able to develop a "professional" application. THat's like asking how long it would take a 2 year old to paint a self portrait! You would get some kind of return, but you would hardly call it professional.
Sorry if that sounds a bit harsh!
To develop a package of this type to any acceptable standard would probably take me a good couple of weeks to design it, build it from scratch, test & debug it properly. I've been building Access databases for 4 years now, so although I'm no Access guru I'm definately not inexperienced.

Good luck in what you are doing

Ben ----------------------------------------
Ben O'Hara
Home: bpo@SickOfSpam.RobotParade.co.uk
Work: bo104@SickOfSpam.westyorkshire.pnn.police.uk
(in case you've not worked it out get rid of Sick Of Spam to mail me!)
Web: ----------------------------------------
 
Hi!

I would agree with James adding one more caveat. It also depends on the persons grasp of the business world. Writing a professional program is translating business rules into Access tables, forms, SQL and VBA etc. If the person needs to do a lot of training in the business arena, then a good Db won't be forthcoming in even six months.

hth
Jeff Bridgham
bridgham@purdue.edu
 
Thanks a lot to all your responses!

It's not that I feel better now ( I have been developing the system I mentioned in the question for almost 2 months now and my manager starts pushing this project, wants to see it done in the next two weeks or so), but I definatelly don't feel stupid. It is my first big Access project, involves lots of vba coding and due to the business goals that have been changing all the time, I am kind of behind the due date.

So, anyways

Thanks for the opinions, and I am staying with you, guys, to push my project further and further.

Good luck to you all
 
One tip for you, guy! Make sure you get them to clearly :) spell out what they want each form/field/etc. to do. Interview the relevant persons and get their feedback as you develop. Ask them things like, "Is this doing what you want it to now? Is it behaving the way you want?" And hope they realise that you can't begin to implement a feature they haven't asked for yet. Maybe you couldn't just walk up and start to develop an order tracking system two minutes after shaking hands with your new boss. What would an order tracking system do, and how should we know? But you can ask them what they want theirs to do, a piece at a time, and develop the pieces. An overall cohesive plan is good to guide evelopment and some decisions as you go, but in the end, you're developing each piece of the whole.

Best of Luck! I've been there a number of times. One of the crucial skills is getting others to give you the knowledge you need. After that, you can get their needs translated into code and so forth.

-- C Vigil =)
(Before becoming a member, I also signed on several posts as
"JustPassingThru" and "QuickieBoy" -- as in "Giving Quick Answers")
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top