Choosing a technology / programming language (for a client)
I’m often asked what web technology would I use for a client (or new project). While I have my personal choice on a technology this is not an easy to answer question.
The “technology” should be based on the client’s needs, future plans (for technology), and most importantly budget. Choosing the technology should NEVER… I repeat should NEVER be what you personally think is “cool” and hip. Beware of anyone that gives an answer before understanding the client’s needs and detailed requirements.
Example: I love pizza… no seriously I lo-lo-love pizza. Now if someone asks me “what should I eat for lunch”… I would ask (or take into consideration) if they are a vegetarian, what do they usually like, are they on a diet, what is their budget, etc.
Here’s a quick breakdown of some of the popular programming languages (excluding front-end languages i.e. html, css, javascript, etc)
PHP (an open-source language)
- PRO: Free free free.
- PRO: Tons of open-source applications and platforms that can easily be used for rapid application development
- CON: Not really an enterprise scale language though does have the ability with minor/major tweeks to the core PHP processor.
- CON: Most PHP “developers” are script developers rather than high end application developers
- CON: Knowing from personal experience as a hiring manager… San Diego is VERY dry for finding good PHP developers.
.NET / ASP (a Microsoft language)
- PRO: Easily integration into corporate/enterprise systems
- PRO: Can scale (if developed correctly)
- PRO: Lots of development tools, QA tools, and replication systems
- PRO: Can easily integrate with SQL Server (both were made hand-in-hand)
- CON: Costly (money and software/hardware resources)
- CON: Most “.Net Developers” are pre-madonna’s as most top talent .Net developers have been doing .Net for many years (ASP, ASP.NET, .NET) and feel entitled to a high salary.
- CON: Most (if not all) .Net Developers are so consumed with everything being Microsoft Microsoft Microsoft and the discussion of anything else if usually meet with closed ears and closed minds.
JAVA / J2EE (not “JavaScript”)
- PRO: One of the most widely used enterprise languages
- PRO: Most Java Developers are good with quality code
- PRO: There’s just about nothing you can’t build with Java (now read next bullet point)
- CON: The front-end of Java is very archaic and hard to really produce good design’s (UX) in a Java environment
Other Notes
- Ruby (ruby on rails) is NOT a programming language… it’s a subset “scripting” language that really needs to run in parallel with another language (of your choice)
- “Java” is NOT “JavaScript”… they are TWO completely different languages
- “jQuery” is NOT a language… it’s a library of reusable JavaScript code (nothing more)
- Do NOT use CSS style sheets that “reset” HTML (li, tables, etc…)
- CSS should ONLY be used to format (design and layout) and NOT a replacement of HTML
- XHTML is NOT a replacement for HTML… it’s simply just recommendation on how to write HTML. It’s like walking at a crosswalk (crosswalk = XHTML)… most people jaywalk (use of various HTML standards).
- Don’t believe everything you read in programming books. For example… this one JavaScript book says you have to have your <script> block above the <head> tag… soooooo not true. You could have a <script> block ANYWHERE.
Ok ok I think I covered enough for now. Still so much more to dig into… like databases, servers, source control, how to write good code, seo myths… etc. I’ll save those for late posts.
