The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Truth. I get the 1000 yard stare when I tell them development will be managing the VMs.
The local IT is all goodness. I've worked with them long enough that they understand what
I'm trying to do. It's the corporate IT Borg that give me trouble.
me: "I'm sorry, 2 of the virtual machines will need Windows Xp."
IT: "Sorry, we don't use that anymore. We don't support it."
me: "Well the development tools for the product that our biggest customer uses needs Xp."
IT: "Can't you try Windows 10?"
me: "No, the tools don't work."
IT: "But we don't know how to support Xp anymore. It's a security risk."
me: "It's okay, development will manage it. Besides, we're not surfing the web here. Honest."
me: "I'll have my director call your director... What we've got here is failure to communicate."
3 months later....
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
This. Admittedly I'm late to the Docker party but it really has a ton of advantages. No need to ensure consistency between environments for the product across the organization since that's handled by using a consistent image; it makes IT's life easier because as far as they're concerned they've just got a bunch of containers; etc.
It is a significant workflow overhaul and requires some training on use though, so that's a pretty big hurdle to overcome to get approval unfortunately.
So, let's say you have N products you need to do regular builds for. I'm of the opinion that unless the products are very close in their nature and build tools, they each get their own VM. In my mind, it limits the coupling between products and build requirements. I'm sure I'm going to have to explain this approach.
this, plus Matthew Dennis's comment - Docker/Containers .. if you dont go Docker/containers for the builds, at least use Docker/containers for the testing so you get a clean test environment every time, unless you keep a 'gold' image for the combinations and clone it when needed, then destroy the clone at the end of the run (we did this on a particular cloud test system).
As to 'very close in their nature and build tools', we had separate build machine(s) for language basically, C++, C# etc - even then, our C++ product had a large dependency on a third party GUI library that occasionally gave us issues, more with the paths and such
Correct me if I'm wrong, but my reading of the license suggests this is OK as long as:
- None of the article itself is used, only the source code linked to the article
- The source code repository contains a prominent URL of the CodeProject license (a copy of the license file would be a good idea too).
- "You insert a prominent notice in each changed file stating how, when and where You changed that file." though this could lead to some pretty ugly commenting if there are lots of changes. Git commit comments are a more usable way of conveying this information
- "You agree not to advertise or in any way imply that this Work is a product of Your own." Presumably adding clear links back to original CodeProject URLs would achieve this.
- "You agree not to remove any of the original copyright, patent, trademark, and attribution notices and associated disclaimers that may appear in the Source Code" - none to remove in this case AFAICT
If you aren't sure - and the comments bit is part of the licence so it's pretty much mandatory - then talk to the author: there is a forum at the bottom of each article which lets you do that.
Ask them, if they say "yes" then you are OK.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
near field communications usage (definition)
unsubtle swindle = CON
<something> = TACTLESS?
money for = PAYMENT
I'm curious to see how you get the rest of it, but of course this presumes that even you know.
Canada has had "tap to pay" credit cards for many years now, whereas they only got rolled out in the U.S. recently. When we were living in the U.S. and were up here visiting, I used a Canadian card and my wife was like ?
Sharing a screen is already enough of a hassle (I use a 4K monitor at its native resolution, a coworker uses 1080p with large fonts), I would NOT want to have to put up with other people's fonts in code...
It's bad enough already to get everyone to agree on tabs vs spaces...