StandardsI have long been an advocate of working to standards when coding for the web, these days that normally means XHTML, CSS, XML and SOAP or RPC standards that may be appropriate. OK sometimes in an Intranet or other local application environment there could be an argument to do something different however I think we should be assuming in favour of rigorously following standards and only deviate from them if we have a compelling reason to do so. Standards compliant code should be viewed as a way to save money, especially in the longer term, not an item that costs money. |
The core skills of a developer are to do with communication and problem solving together with an understanding of the overall IT environment and the principles of programming and relational databases rather than a tick list of languages we "know". However it is still worth knowing what languages and platforms an individual has worked with, so here is my list.
I have divided this list into two sections: Core - by which I mean I have used these skills intensively to produce real systems in a live commercial environment during the last two years and Others, areas I understand well and have used in anger at some point during my career but have not necessarily been at the forefront of my life in the last year or two. Just because I haven't used them so much recently doesn't mean I wouldn't want to pick them up again now though!
Core
- Classic ASP
- ASP.NET
- VB (Visual Basic) used for interface applications
- VBS (Visual Basic Scripting edition) used for interface applications
- Excel Visual Basic for Applications
- Access Visual Basic for Applications
- SQL Server 2000 and 2005
- HTML
- ADO
- Javascript
- DHTML
- AJAX
- XML
- Web services
- CSS
- Procurement Card Implementation
Non-Core
- mysql
- Java
- VB.NET
- Sharepoint including access to list data via XML/SOAP
- SAP Implementation
- Perl
- C#
