william chaple wrote:Awesome thanks! What is SVN btw
and what about at a developers point of view? Like lets say I work for fiverr, or if anyone on here is a professional developer, do they use a basic ide simple as netbeans, or do you use a different ide
or some kind of company software
Didn't the tutorial explain what SVN is: a version control program called Subversion?william chaple wrote:Awesome thanks! What is SVN btw . . . do they use a basic ide simple as netbeans, or do you use a different ide
or some kind of company software
Tim Driven Development | Test until the fear goes away
Tim Cooke wrote:As Campbell says, the IDE you use is often down to your own preference however some IDE's are more suited to certain technologies and languages than others. For example, my company predominately develops Java based applications and the majority of folks use Eclipse as their IDE of choice, however there are a smaller group (including myself) that prefer IntelliJ IDEA instead. Both work just fine so it's personal choice. However, if you were a C# .NET developer then MicroSoft Visual Studio would probably suit better in that case.
The majority of companies I know use SVN as their source repository system but "git" is becoming quite popular these days and not just with the hipster startup companies.
Often even the environment in which the application you're developing will dictate the Operating System you would choose. For example, the Java application I'm working on deploys in production to a Solaris UNIX server inside the Servlet container Tomcat. So in order to closely replicate that environment in our local dev environment we use Mac OS X systems. Or in a previous company we used Linux systems for the same reason. If you were working on a .NET application then a Windows machine would probably make more sense to run whatever MS app server you'd need there. What I'm getting at here is a familiarity with the UNIX style file system would be beneficial. Get yourself a Linux system running in a Virtual Machine and play with it and become comfortable with using the Terminal. Lots of resources online for this.
I think what we're getting at with a "Large build system" is to encompass everything required to build a complete application. So we're not just talking the Java application, it could include a database, a User Interface, external API's, integration with other systems and services, your application build tools, source repository tools, among others.
Don't expect to become an expert in all of these things from the start, you'll learn each as you use them.
You use an IDE for a company you work for, such as microsoft
uses a "large build system"
I will still be coding on an ide just inside a large build system? and my ide will deploy to lets say "tomcat" as an example
Tim Driven Development | Test until the fear goes away
Tim Cooke wrote:
You use an IDE for a company you work for, such as microsoft
No, I would choose my IDE based on the type of application I'm developing, not on what company I'm working for. I was saying that if you are working on a C# .NET application then MS Visual Studio would probably be your best choice just based on its feature set for the language.
uses a "large build system"
I'm not 100% what Henry was referring to when he mentioned the large build system. But to me it sounds like the entire workflow from development (you and I) right the way through to production, which encompasses a whole lot in-between. Depending on your company size and setup you may have varying degrees of involvement with some or all of this process. I work for quite a large company so have different teams to manage different stages of the process. However, no matter what the setup is it is still down to the development team to dictate what needs to be done to get the application up and running. You won't be expected to know everything about this up front so just learn as you go. Your company will probably do it differently to mine so no point going into it (unless you happen to work for the same company... and that would be spooky!).
I will still be coding on an ide just inside a large build system? and my ide will deploy to lets say "tomcat" as an example
An IDE is just a tool to help you read, write, and edit your code faster. You could do it all in NotePad or VIM if you wanted, the result would be the same. Tomcat is a Servlet Container, which means that it is an application container that will deploy and run a certain type of application, in this case a Servlet based application.
william chaple wrote:
Awesome thank you so much. I guess the only thing I am still a little confused is the "large build system". I'm envisioning it as the whole company team; pretty much how you are describing it. So how is it like developing for your company? What are the steps they take to build what they build? I wish I can do an internship so I can learn, but I cant leave my bills behind =(
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
No more Blub for me, thank you, Vicar.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Humans and their filthy friendship brings nothing but trouble. My only solace is this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
|