Diary of a Developer: To Script or Not to Script

The enduring question for those first learning the ropes of software development on the Web is: What's the best technology to learn?

provided by: 
Originally published at Internet.com


A majority of the e-mails I receive ask the question "What should I focus on, technology-wise, to learn/master?" This is a very good question, however complicated the answer. The simplest answer is "It depends" (the mantra of good consultants everywhere). The more complicated answer is one that I'm still struggling with.

Jason Purdy

Recently a renowned Perl developer gave a really good answer in an interview, saying that the key is focusing on the practice of programming, rather than a specific technology.

Unfortunately, there's no real book out there that will tackle this, outside of the course books from high school or college Computer Sciences courses. The best way to learn programming is to start with CS classes of some sort (so you understand the fundamentals of memory, processing, etc), but it doesn't stop there. You will be forever honing your craft by practicing, researching, and collaborating. Do not let the hype and marketing machinery lead you away from your comfort zone, just because it's the latest or coolest or "popular" choice.

It also helps to understand the system that you have to work on. When it comes to Web development, there are usually three different areas where you can program to create interactive Web applications, and with them, a spectrum of difficulty: ...

Read article at Internet.com site
Related Articles
- A Java Card Primer, Part 2
We wrap up our tutorial on working with Java Card technology to program smart cards by taking you step by step through the process of getting an applet to run on a card simulator. Follow the instructions to create your first smart wallet app.
- User Code: Java Applet and JavaScript Communications
- Code Work with Java Annotations
- Building with Ant: Directory Structure
- So, You Want A Java Clock, Huh?
- Views from Abroad: Really Running Anywhere
- Server-Side Development on Mac OS X: Launching Tomcat
- Enterprise Deployment Environment with Java Spring
- Using PHP with Forms
- Views from Abroad: Simkin, A New Breed of Scripting Language
Regional Articles
- Diary of a Developer: To Script or Not to Script Alabama
- Diary of a Developer: To Script or Not to Script Alaska
- Diary of a Developer: To Script or Not to Script Arizona
- Diary of a Developer: To Script or Not to Script Arkansas
- Diary of a Developer: To Script or Not to Script California
- Diary of a Developer: To Script or Not to Script Colorado
- Diary of a Developer: To Script or Not to Script Connecticut
- Diary of a Developer: To Script or Not to Script DC
- Diary of a Developer: To Script or Not to Script Delaware
- Diary of a Developer: To Script or Not to Script Florida
- Diary of a Developer: To Script or Not to Script Georgia
- Diary of a Developer: To Script or Not to Script Hawaii
- Diary of a Developer: To Script or Not to Script Idaho
- Diary of a Developer: To Script or Not to Script Illinois
- Diary of a Developer: To Script or Not to Script Indiana
- Diary of a Developer: To Script or Not to Script Iowa
- Diary of a Developer: To Script or Not to Script Kansas
- Diary of a Developer: To Script or Not to Script Kentucky
- Diary of a Developer: To Script or Not to Script Louisiana
- Diary of a Developer: To Script or Not to Script Maine
- Diary of a Developer: To Script or Not to Script Maryland
- Diary of a Developer: To Script or Not to Script Massachusetts
- Diary of a Developer: To Script or Not to Script Michigan
- Diary of a Developer: To Script or Not to Script Minnesota
- Diary of a Developer: To Script or Not to Script Mississippi
- Diary of a Developer: To Script or Not to Script Missouri
- Diary of a Developer: To Script or Not to Script Montana
- Diary of a Developer: To Script or Not to Script Nebraska
- Diary of a Developer: To Script or Not to Script Nevada
- Diary of a Developer: To Script or Not to Script New Hampshire
- Diary of a Developer: To Script or Not to Script New Jersey
- Diary of a Developer: To Script or Not to Script New Mexico
- Diary of a Developer: To Script or Not to Script New York
- Diary of a Developer: To Script or Not to Script North Carolina
- Diary of a Developer: To Script or Not to Script North Dakota
- Diary of a Developer: To Script or Not to Script Ohio
- Diary of a Developer: To Script or Not to Script Oklahoma
- Diary of a Developer: To Script or Not to Script Oregon
- Diary of a Developer: To Script or Not to Script Pennsylvania
- Diary of a Developer: To Script or Not to Script Rhode Island
- Diary of a Developer: To Script or Not to Script South Carolina
- Diary of a Developer: To Script or Not to Script South Dakota
- Diary of a Developer: To Script or Not to Script Tennessee
- Diary of a Developer: To Script or Not to Script Texas
- Diary of a Developer: To Script or Not to Script Utah
- Diary of a Developer: To Script or Not to Script Vermont
- Diary of a Developer: To Script or Not to Script Virginia
- Diary of a Developer: To Script or Not to Script Washington
- Diary of a Developer: To Script or Not to Script West Virginia
- Diary of a Developer: To Script or Not to Script Wisconsin
- Diary of a Developer: To Script or Not to Script Wyoming

Rss   Delicious   Digg   Add To My Yahoo   Add To My Google   Bookmark   Search Plugin

Topics:
Architecture & Design Languages & Tools Project Management Web Services
Database Microsoft & .NET Security Wireless
Java Open Source Techniques XML