Hi Spidy,
I know people who earn their living using PHP/MySQL to build websites, and they too have the 'just because' reasoning behind their choice of languages. This is something I don't understand. I would like to think that when I make these sort of decisions, I am able to backup my decision based on facts and technical requirements, rather than just because I feel like implementing something using a particular language/technology. In my experience "the right tool for the right job" applys here, often various factors constrain the tools you can use in the work place. For example, some employers will stick to a tool/product set, be it ASP/MS SQL Server or PHP/MySQL, because their employees are skilled in these areas, or they have a lot of existing/legacy code in these languages which needs to be maintained.
Martin | [reply] |
That's fine by me. If they're making that sort of decision "just because" then I can expect them to be equally sloppy and slapdash in the other decisions they make and in the code they write. I don't want to work with such people. I'd be happy to be paid to clean up their mess afterwards though.
And you never know, I might clean up their mess using Java or C or PHP instead of perl, if I think that that is the right choice. | [reply] |