zeroxsys

We wanted to build a flying sphere also, but different from this one.

Video here: http://www.reuters.com/video/2011/07/14/flying-sphere-goes-w...

We are a Web development service provider. We design and develop our own website, as a proof to clients what we can do. But sometimes, when it comes to your own website, you tend to put everything you know in there - make it the best one you did. As a result, you take too much time doing it, instead of others doing it for you. So if you have a specific launch date, develop your own website within that period only. Otherwise, hire someone to deliver your website at your desired deadline.

Found a YouTube channel where all the videos were uploaded, at http://www.youtube.com/user/djs61257.

It is also not a "document" for me, a "form" (that a non-programmer may use to build their own custom online forms). So I guess, providing a map of flow of operations/commands will be helpful to tell the clients where Dokuments will play in their business/personal workflow. Good luck!

I would say, it depends on the app you'd build and the toolkit you'd need. For your web-based app for a financial enterprise, you’d only need knowledge/skills on database/SQL, HTML+CSS, and front/back-end programming (i.e., JavaScript, PHP, VB.NET). Here you’d only need reference materials, as you can easily find how to develop the modules you’d need.

However, imagine what you could miss? During the design phase, diagrams, (R)DBMS, OOP, algorithms and software engineering skills are some of the vital CS fundamentals that will eventualy result to the overall quality of your app. You may be able to develop a complete app, but you may not be able to know if it’s the best implementation. While testing your app, you might find some CS concepts (i.e., data structures, searching, Big Oh) relevant along the way, to enhance the processes maybe. Yes you could study these topics by your self, but you might be more effective if these are already in your armory before jumping to the job. Like when you’re programming, an OOP approach might be a better approach as early as the initial coding, rather than convert to it after launch. Or you might learn that you could offer real-time collaboration using other networking/Internet technologies.

Yes you don’t need a CS degree, but let me suggest that you scan the CS topics before you start designing your app. Someone who has a CS background may be able to forsee all posible problems and solutions to its system right after the inception of the idea, while someone who’s not, must explore all possibilities and validate them in each step he/she would take. I’m not saying that you cannot build a good app, I just hope that you won’t miss something. Good luck Sir!