128 karma · joined May 13, 2013
Huh?
You have to make time corrections when you program something related to astronomy. In most things we program, UT is an absolute on which we can rely, but when we go very far away in the past it's not that clear anymore.
I was going to say this is ironic but I will rather say I find this ironic
Granted one is more dangerous than the other, but to me it's no reason to give them access. It's still a headache.
If only the developers have access to modify the structure, the way it is done is not important (it can be done through a webform that alters a database, though the addition of a json definition, through coding, etc.) After all, you can modify the schema through PHPMyAdmin. It's some kind of admin interface. You just don't grant your users the right to do it. Just as you don't grant them the right to add custom fields, unless they know what they are doing, which is seldom the case :)
I think that EAV gives a false sense of security, in that it does not "break" much if done by a non-knowledgable user. But still, if it is done badly, good luck reconciling the data.
Now, this guy began learning code 6 months ago and is better than anyone else? Wow. Either a) he is much more intelligent and talented than I am (this is not sarcastic, it is entirely possible) or b) we have a case of the Dunning–Kruger effect.
I also did not know that there are different qualities of fog... I thought fog is fog, but it seems that some fog machines are really better than others. One of the aspects of fog quality is being able to breathe even when there's lot of it. One one occasion, we fogged a studio so much that I could not see my own hand 6inches from my eyes, and I was still breathing normally as if the air war pure. I couldn't say if it has long-terms effects if you breathe too much of it though, but I can say that not coughing with so much fog is quite impressive.
Also, don't get caught speaking of "smoke" to these people, who take a lot of pride in their product :) It's fog and haze... not smoke!
As soon as you get people working on a project that are too specialized, no matter the size of the team, you inevitably get conflicting concerns. I think it's very important for managers to understand what those concerns are to be able to take the right decision.
I also think that even specialized people should have some knowledge of other specializations (e.g. designers that understand programming, and vice versa). On very large projects, this is impossible as there are just too many fields, but still I value very much "general knowledge" for that reason.
Anyway, good luck Maxime in your endeavors.
You can read about it, if you haven't already, on http://lab.la-grange.ca/en/showing-an-apollo-mission-free-re...