On Thu, Oct 12, 2017 at 3:29 PM, Ted Roche tedroche@gmail.com wrote:
On Thu, Oct 12, 2017 at 4:00 PM, Charlie-gm ccbibleman@gmail.com wrote:
On 10/12/2017 11:06 AM, Stephen Russell wrote:
I wonder why they want VFP peeps to do this? "The role will mainly be
in
conversions from Visual Foxpro to C#."
Because only a Foxer could understand what had been done, with what implications and side effects?
At my current job we will always ask for the business story on why we do "business" with these peculair rules. After you hear the "why" you can duplicate the outcome. Today we have the great idea to tak all of our finished goods produced at all of our plants and make the SKUs identical across the enterprise. Yes, today each plant has their own item number for the same generic carton and bottle that we make in 80% of our plants. The story is "We have done it this way since before computers".
Or because if you've already done VFP, you can come onboard as the junior dev and do support and deferred maintenance while learning the new stuff?
There's lots of good reasons to hire a veteran :)
If your finished product is in a different language hire a vet in that NEW language is what I would do and recommend. Use agile methodoliges and don't be afraid to deploy often if your build conforms to your rules.