Member Avatar for samaru
samaru 145 a.k.a inscissor

Builder.com made a survey about web technologies. Which are used the most/least. Very interesting. It's based out of 557 people. Here's what it covers:

General Technology Skills covered things not necessarily tied to a particular technology or vendor: e.g., XML, database design, and Web services.

Programming Languages included a collection of 13 programming languages and technologies like Java, Visual Basic, and COM.

Web Development covered languages associated with Web application development: e.g., ASP, Flash, and PHP.

Databases included the results for each of the different database systems we asked you to rate yourself on.


http://builder.com.com/article.jhtml?id=u00320021009adm01.htm&page=1

  • 1 Contributor
  • 0 Replies
  • 131 Views

Dani AI

Generated

Good find, . Old site surveys are useful as historical snapshots, but they need context before being used for hiring, training, or migration decisions.

Key methodological points that are often missing and should be checked before trusting headline numbers: how respondents were recruited, whether answers are self‑reported or tested, the mix of roles (developers vs. managers), regional or industry skew, and precise wording of questions (for example, “have used” vs. “use regularly”). Self‑selected audiences tend to overrepresent whatever is popular with that site's readers, so treat raw percentages as directional rather than definitive.

For the thread tags here (classic-asp, database-design, web-design), a few practical interpretations and actions follow. High historical usage of a legacy technology usually signals a large installed base, not long‑term viability. When maintaining or migrating legacy ASP apps, first produce an inventory (pages, COM components, DB drivers), run a security audit for input handling and session management, remove inline SQL where feasible, and plan staged migrations with clear rollback points. For database design, popularity counts less than schema quality: prioritize constraints, indexing strategy, backups, and a tested migration path. For web design, popularity doesn’t equal suitability — prioritize accessibility, performance, and maintainability over chasing fads reflected in older surveys.

Suggested next steps that convert the survey into useful evidence: cross‑check survey signals against current job listings and open‑source activity, run small prototypes to measure developer velocity and performance, and measure operational costs (hosting, support, security fixes). Treat the Builder.com results as context for where the industry was at a moment in time. Combine that context with hands‑on tests and current market data before making long‑term technical choices.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.