4 ms·
When I'm engaged in rapid prototyping or testing an idea, I almost exclusively rely on the stack I'm familiar with that fits the problem domain. But I don't co
by fallous 11y ago
When I'm engaged in rapid prototyping or testing an idea, I almost exclusively rely on the stack I'm familiar with that fits the problem domain. But I don't consider that "real code" given the very nature of what I'm doing and the understanding that once the problem has a solution, that solution can be applied to whatever stack BEST fits the situation.
The author seems to engage in the same behavior, but conflates the "get things done fast" with the production solution.
If you're a good programmer and your preferred tool is PHP, then you're engaged in "real programming." If you insist on using PHP as a deployment solution because it's what you're familiar with rather than because it is an appropriate/optimal solution to the problem then you're engaged in laziness.
A good programmer can adapt their mental models and adopt the tools necessary for the problem domain. A bad one always has an excuse for why their comfort justifies tool choice.
- dietrichepp 11y agoI'd like to use a broad definition of "appropriate/optimal". I could imagine PHP being optimal only because you already have PHP talent in house.
- fallous 11y agoYes, if PHP is appropriate to the task at hand AND you have an existing set of PHP talent in-house then it would be hard to argue that isn't an optimal solution. However, if PHP is not appropriate, that in-house PHP talent does not change the fact that PHP is the wrong tool.
- ktRolster 11y agoIf your in house 'talent' can't learn a new web framework without too much trouble, then it's questionable to call it talent. I've never worked at a company that used Delphi, but I have complete confidence in my ability to use the language. If a person doesn't feel confident in their ability to pick up C, they are missing something from their toolkit.