3 ms·
Why? Because I wouldn't want to join a team that makes decisions for no reason. > Presumably, the actual criteria was likely familiarity and fluency for their
by RandallBrown 7y ago
Why? Because I wouldn't want to join a team that makes decisions for no reason.
> Presumably, the actual criteria was likely familiarity and fluency for their tech founder or early developers.
That would be a completely valid answer to the question. The fact that they didn't answer the question at all is the problem here, not that they chose PHP.
- kortilla 7y agoOr maybe they didn’t want to waste time on a candidate with such superficial focuses? Next time ask them why they chose to paint the wall dark blue instead of navy blue.
- lowercased 7y agoIf they were hiring an interior designer or painter who asked why a specific color or paint type was chosen, but gave no answer... that might still be weird.
- hdfbdtbcdg 7y agoThis highlights something most devs don't understand. Product development is about developing a product not about writing code. All the choices we make should facilitate making a good product, writing good code is a side effect. In this metaphor the colour of the wall is equivalent to the product. The code is equivalent to whether the painters used brushes, pads or rollers or whether they used ladders or scaffolding - the customers do not care. By asking why choose php you are asking why use rollers to paint.
- vageli 7y ago> In this metaphor the colour of the wall is equivalent to the product. If that's the case, asking about the choice of implementation language sounds like asking about the spec.
- deleted 7y ago[deleted]
- hdfbdtbcdg 7y agoIt might be part of the technical spec but almost certainly not part of the product spec. The end user does not care about the programming language.