(adsbygoogle = window.adsbygoogle || []).push({});


We are TeamCS, basically you may presume us to be a hacking and a fail group, well we are opposites. We hope to gain members that have above average knowledge in Programming, coding and/or Web Developement. We hope to create applications, scripts, and softwares for the world to use. Free, and licensed.

What we are looking for:
- People that have general knowledge and skills in coding in various languages (Such as: C, C++, C#, VB.net, Java, Flash,PHP,HTML,SQL...)
- People who have fun with what they do (in this contex coding)

Now we do limit the use of hackers from joining our team. We do want hackers to be in our network, that do not only use the term hacking in a negative way but can also secure, patch and use the term in a positive aspect.
If you want to learn more be sure to visit: You must login or register to view this content.

So, I thought I might ask some evaluation questions of your group, as I think it would be interesting for myself and others to learn more about your group before diving right in.

What led you to start this group? What will distinguish this group from others? What do you expect out of the group? What can the group expect out of you? Where do you see this group going, and what do you plan on doing to get it there?

Now, as far as the software development goes...

What projects are you interested in developing? What "genre" or "type" of applications do you plan on developing (just as a general idea, as certain types of applications require certain skills, even outside of programming)? How large of projects are you planning on building? Do you foresee them being small tools and quick programs, or are you interested in deploying larger scale applications, that might take significantly longer to develop?

Will you be using source control, and if so, which system?

Will developers be able to make a build in one step?

Will there be a well-defined specification and potentially a requirements management system for your projects?

What type of testing methodologies do you plan on employing? Will you be making use of automated tests?

What license(s) will you primarily be releasing software under?

What languages or frameworks do you see working with (in most cases)?

What is the target demographic (of programmers) you're seeking on an unambiguous scale? What ages? What levels of skill (perhaps measured by how long they've programmed, or the types of projects that they have deployed)?

What led you to start this group? My interest in programming and coding. And as this is a group also team-working.

What will distinguish this group from others? It will distinguish us from others because we plan to not only develop and create stuff, but also help the community by providing help, sources and tutorials.

What do you expect out of the group? I personally expect, that our group gains some what a status of a development "company" e.g. Dragonbyte technologies. And that they have passion, interest and a good knowledge of what they are doing.

What can the group expect out of you? The group can rely me to support them in any way such as, purchase scripts, software's, programs etc.

Where do you see this group going, and what do you plan on doing to get it there? In about over a years time I see the group at a status of growth and receiving, projects, customers and gaining more recognition.

Now, as far as the software development goes... We want to be building small and useful tools for any type of people, in different areas. We also want to be creating plugin's for online forum software's such as: vBulletin and other forum software's.

What projects are you interested in developing? What "genre" or "type" of applications do you plan on developing (just as a general idea, as certain types of applications require certain skills, even outside of programming)? How large of projects are you planning on building? Do you foresee them being small tools and quick programs, or are you interested in deploying larger scale applications, that might take significantly longer to develop?

For a start we want to be creating small and quick tools and plugins. In genre types it can be type of program; We mostly want to develope plugins for online software's, as i said before vBullein etc. The reason for this is, that this type of genre is rapidly growing and it would be a chance for us to be known and popular.

Will you be using source control, and if so, which system? Not at the moment we do not not plan to use any version control.

Will there be a well-defined specification and potentially a requirements management system for your projects? No, not really.

What type of testing methodologies do you plan on employing? Will you be making use of automated tests? Manual tests are a more innovational and accurate way of debugging and testing.

What license(s) will you primarily be releasing software under? As a primary license, Royalty free and re-distributable licencing.

What languages or frameworks do you see working with (in most cases)? Primarily we want to be working with; C based languages, VB.NET/VBScripts. Delphi, Java... And in terms of web development some more complex languages. HTML, PHP, SQL, XML, CGI, and we also want to cover alot of scripting languages.

What is the target demographic (of programmers) you're seeking on an unambiguous scale? What ages? What levels of skill (perhaps measured by how long they've programmed, or the types of projects that they have deployed)?

This is a very big question :p. Personally I am 16 years old in learning stages, and have little experience and average knowledge. I want to be working with programmers that have more than just basic knowledge in more than one area. (Not just developing in one Genre). As far as age goes, its just a number it would be stupid for me to say that the founder of facebook does not deserve to be the youngest billionaire. Experience is a key but not a vital aspect of programming, i believe the more you develop,(practice) the better you will get.

I hope this answers all your quesions and if you have anymore please just re-quote me .

.//Starz

I do have a few follow up questions, based on your answers.

1. Why do you not support TDD, a style that is growing in popularity, and gradually becoming something of a de facto industry standard? Why do you think unit tests are inaccurate? Why is manual testing, a method that has existed for perhaps hundreds, if not thousands, of years, more "innovational" than automated tests?
   
2. Why do you plan on not making use of any sort of revision control system? How will you organize projects, especially larger ones, where there are multiple contributors?
   
3. How will projects be organized? Who will organize them? Who will be welcomed to contribute on any given project?
   
4. Do you plan on developing open-source software (not just free)? If you do not plan on releasing projects as open-source, why?
   

Now, I also have a question regarding your personal ability. I've known people aged sixteen who are skilled programmers and computer scientists, some who know more than your average college graduate. I've also seen people who think they know quite a bit about programming, but really know very little.

It would be really helpful if you went to You must login or register to view this content. ([url]www.indiangeek.net/wp-content/uploads/Programmer%20competency%20matrix.htm[/url]) and went through the entire matrix. Read the instructions, go through each section honestly (don't look up answers or anything, it's based on your own personal, current knowledge), and come back with the average level you're at. It's perfectly acceptable if you find yourself at 2[SUP]n[/SUP], but it'll help you find programmers who are also around your level, and it will ultimately help some people decide if they really want to join your team.

I do have a few follow up questions, based on your answers.
Why do you not support TDD, a style that is growing in popularity, and gradually becoming something of a de facto industry standard? Why do you think unit tests are inaccurate? Why is manual testing, a method that has existed for perhaps hundreds, if not thousands, of years, more "innovational" than automated tests?

Okay why I would prefer manual testing:
-It's useful in both small and large projects.
-The test cases can be added or removed according to the movement of the project.
-It's more reliable.
-Tester can execute additional ad-hoc. You will find that more bugs and errors are found with adhoc than the automation.

Why do you plan on not making use of any sort of revision control system? How will you organize projects, especially larger ones, where there are multiple contributors?
How will projects be organized? Who will organize them? Who will be welcomed to contribute on any given project?
Do you plan on developing open-source software (not just free)? If you do not plan on releasing projects as open-source, why?

I think you are going in too much detail, the reason i say this is, because we have not yet started and can not really predict alot of further movements. For the time being we would want to distribute out work as open source and free. But this probably will change in the future to licencing, and time periods.

I would describe my self to be an intermediate programmer as I have little experience and average knowledge in some areas.
Thank you for your help.

Could I ask how much; Skill, Knowledge and experience you have in programming youself.?

According to the programmer competency matrix I'd end up ranked somewhere between levels 2 and 3. I've taken, and will continue to take, a few college courses for computer science and mathematics; though I find that experience is the key to being a good programmer, without the ability to harness one's "raw knowledge", one cannot expect to be a good programmer.

True saying and you look like a good programmer. Would you be willing to help me grow my forum and provide help to other programmers.
You must login or register to view this content.