CodingClues - Latest Comments in Choosing the Right Infrastructure for your Project

Re: Choosing the Right Infrastructure for your Project

Mark — Tue, 01 Jul 2008 19:03:05 -0000

Why would you name the project 'movdb2' and NOT USE DB2 as the database? Plus, there's a product named 'move for db2' so, after I recovered from confusion induced epileptic seizure, I wrote this comment.

Re: Choosing the Right Infrastructure for your Project

Sebastian — Tue, 01 Jul 2008 14:02:39 -0000

Thanks for your comments, especially thanks to Rob!

Some quite insightful answers. Indeed, not too much thought has been put into the requirements, I usually do more for full-fledged company-stuff... :-D

Anyway, the "project database" thing sounds really interesting.
Especially considering that what formed the "Function Point" method of calculating project cost was based on such research.
It might be an interesting thing to do!

Re: Choosing the Right Infrastructure for your Project

Rob W — Tue, 01 Jul 2008 12:15:28 -0000

I think this is quite a common pathway to how project technologies are chosen... for better or for worse.

The strongest influence seemed to be what you've used before, as long as was relatively successful (i.e., the MySQL decision -- it worked for you before, so you don't really consider the other choices). Perl is ruled out because you've had negative experiences with it in the past... but Python could result in just as negative an experience -- you simply don't know because your experience is limited. Java seems to be ruled out for being "heavy machinery", though I'd say it very much depends on the approach you take -- a Tomcat installation and a few JSPs is pretty lightweight; a full JBoss installation, EJBs, all the extras would be much more heavyweight.

...but I'm biased because I have more experience in Java than probably anything else. so I can get a simple Java site up and running very quickly.

So I could have the exact same requirements, but come up with a completely different solution; though I've tinkered around a bit with Python/Django and RoR, so I might actually take one of those as a learning experience.

The funny thing about all this is that the only actual "requirements" for the webapp that you considered were size and the fact that it's a personal project. Was there any other consideration of what the site actually needs to do, and how that might affect technologies chosen? Maybe not, if it's simple enough....

I personally can imagine a huge database with detailed information on millions of projects that are embarked upon constantly -- with data on developer experience, technologies chosen, project complexity/size/scaling requirements, domain, project success & schedule, and developer & management comments... and before starting a project you could look up similar projects executed by similar developers and compare.

Wouldn't that be wonderful? But in my experience this is hardly even done *within* companies -- let alone in the wide world. I can dream, though....

PS: kompoZer isn't associated with Gnome, is it? It's just nVu with a few bugfixes.

Re: Choosing the Right Infrastructure for your Project

Anon — Tue, 01 Jul 2008 10:52:54 -0000

Java is too big! No PHP!, why do ppl keeping saying this. i doubt your language experience

Re: Choosing the Right Infrastructure for your Project

Andrey Larionov — Tue, 01 Jul 2008 07:06:05 -0000

Why not Smalltalk? When you choose Smalltalk you no need to worry about IDE, WebFramework, Template Language and so. Also it's very powerful and simply language for development projects like this.

Re: Choosing the Right Infrastructure for your Project

pcdinh — Sun, 29 Jun 2008 11:11:44 -0000

So you have never heard about PHP, right?