4 ms·
welcome to IT :-). I usually wait for something to be asked for twice before doing, cause the first time is often just noise (oh you really want that). Somethin
by chadcmulligan 8y ago
welcome to IT :-). I usually wait for something to be asked for twice before doing, cause the first time is often just noise (oh you really want that). Something that takes a bit of work like this I'd usually confirm in an email asking if you really want this, and are happy if I do it this way. Rule of thumb when dealing with management: if its not written down it didn't happen.
Most places have a set of languages / tools they use because everyone knows them, unless there's an extraordinary reason usually stick to these even if there are better tools around. If you want everyone to start using a new tool, then one way is to get some buy in by others, then have a pilot project to evaluate the new tool, weigh the pros and cons etc.
- blackflame7002 8y agoYea it's best to ask design questions over email because then you have a record for both parties to refer back to if either forgets. But in general, you have to understand that solving a problem...is only half of the problem. The other half is keeping that problem solved which means the code needs to be maintainable.