4 ms·
It's hard to judge this objectively, since you seem to be painting your differences from Mr. X in a particularly "new v. old" light. A few examples: X says th
by jmduke 13y ago
It's hard to judge this objectively, since you seem to be painting your differences from Mr. X in a particularly "new v. old" light.
A few examples:
X says that we should be using "special character" separated strings - without using a lib/wrapper that hides the underlying implementation.
Why does he think that way? Has he tried going down a JSON route before, only to be confronted with an edge case or peculiarity that makes his method simpler?
And this part jumped out to me:
For example, I say - Let's put in 10 more days and make a generic solution to create similar forms for 30 db-tables ... (time is not a problem)
Ten days is a lot of time. Can you put together an argument that the generic solution is worth that time even in the very long run? You say time is not a problem, but how is that possibly the case?
- pmelendez 13y ago>"Why does he think that way? Has he tried going down a JSON route before, only to be confronted with an edge case or peculiarity that makes his method simpler?" I was actually about to comment on the same thing. Depending on the case a simple solution would be faster to implement and potentially easier to maintain, but as always it will depend on the requirements