For anyone interested:
https://www.jobserve.com/gb/en/search-jobs-in-Solihull,-West-Midlands,-Unite...
or
Dave
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
I wonder why they want VFP peeps to do this? "The role will mainly be in conversions from Visual Foxpro to C#."
Why not get C# peeps who can do in C# the intended functionality that is happening in VFP? I have to say that this is why projects are on a DOOMED plan from day one. YMMV
On Thu, Oct 12, 2017 at 9:08 AM, Dave Crozier edleafe@gmail.com wrote:
For anyone interested:
https://www.jobserve.com/gb/en/search-jobs-in-Solihull,- West-Midlands,-United-Kingdom/VISUAL-FOXPRO-DEVELOPER- SOLIHULL-59A76E7DEB6D910B/
or
Dave
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
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#."
Dunno. Maybe similar reasons as why people who show no interest in VFP solutions and exhibit limited knowledge of VFP still hang around a VFP list....?
-Charlie
[snip]
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?
Dunno. Maybe similar reasons as why people who show no interest in VFP solutions and exhibit limited knowledge of VFP still hang around a VFP list....?
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 :)
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.
I've seen it fail both ways. In fact, I've seen projects fail all 3 ways. With VFP devs only, with New language devs only and with a mix of devs from both sides. Some failures have been more spectacular than others. And more expensive.
I've only been involved with 1 project like that, That was with the mix of developers. The "new" guys couldn't get all the functionality of the Fox apps implemented, even when they decided that some of that functionality was not needed anymore.
Fred
On Thu, Oct 12, 2017 at 2:30 PM, Stephen Russell srussell705@gmail.com wrote:
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.
-- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN
901.246-0159 cell
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
Charlie - R U saying that YOU have no knowledge of VFP??
:-)
Just curious. I suppose you meant part of your comment as "tongue in cheek". As for Stephen - yeah - he was a Big time VFP guy - but, sure - he has moved on to other greener pastures. But, HELL - a LOT of the folks here have. And, yet - MANY Still stay here - participate and all - partially because its a community - that has gone beyond just VFP. Heck - that is Exactly the Case with our Fearless leader Ed! Just sayin'...
-K-
On 10/12/2017 4:00 PM, Charlie-gm 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#."
Dunno. Maybe similar reasons as why people who show no interest in VFP solutions and exhibit limited knowledge of VFP still hang around a VFP list....?
-Charlie
[snip]
[excessive quoting removed by server]
On 10/12/2017 9:20 PM, Kurt at VR-FX wrote:
Charlie - R U saying that YOU have no knowledge of VFP??
:-)
Judge for yourself of course. But I do not propagate incorrect claims about how VFP "copies down the whole table across the network whenever you open it" and things like that.
And I certainly do not remember Stephen (Bad Steve?) to have ever been a "big VFP guy". As I recall he generally put down VFP and praised the latest Microsoft "best practice" of the moment (which sometimes turned out to be a "bad practice").
Anyway, my irritation in this particular instance was his "contribution" to the topic was basically trying to "scare off" VFP'ers from the project: "doomed to fail..." Which, of course, is utter nonsense. Making sure you have someone that has a deep knowledge of the source language means the real operational requirements can be identified: why the system was designed the way it was. Lack of clear requirements is, by far, the primary reason projects fail. Also, does he think a VFP'er cannot learn C#? ROFL. The best way to learn a new language is to actually work in it: and working in it while stepping through a previous code set that you know well makes things much easier. Heck, I'd have looked into it except I have no interest in Microsoft development tools any more. I'll spend my time with Javascript, Python, some R, maybe Java.
But whatever. I don't really care that he hangs around the list (like I have any say-so about that anyway). Maybe others remember the things he's done on the list differently than I do. For me, I saw just another case of trying to back-hand insult VFP'ers - maybe it wasn't intentional <shrug>. But since he's obviously not interested in VFP any more, why post on topics specifically pertaining to VFP? My little quip in response was just trying to point that out.
-Charlie
But - Charlie - even U admit 2 not working in VFP w/the list of tech U mentioned!
Am curious - how long U been on here?
I go a GOOD Ways back here on the forum - joining circa 2008. But - I didn't stumble upon this great resource until Many years into VFP ! Yeah - like me - Steve has been here a while - even LONGER Than me!!!
We met some years ago on Long Island - when he was visiting his mom on LI. He talks here Of other Tech & helps out plenty. In my day job I've been forced outta VFP & now starting 2 work in VB - although now doing like 2.5 yrs of MS SQL. Systems I support(1 is now gone - replaced by a new Sys) R in VFP w/SQL as back end. So - even I have had 2 move on!!!
Although - those that know me well here - know that I am highly versed in 3D CG & 3D Printing. Many know of my 4.5 foot long Dragon creation - which has been exhibited in Numerous venues - I now also have my 9 foot long Dragon! Although - besides the purely artistic type 3D projects - I have product design prototypes I am trying to bring to market.
Anyway - that's me in a nutshell. And - yeah - many of us are pretty tight in this VFP community & Steve is truly a long respect member. I suggest U don't take his replies in the wrong way.
He's also fun to hang out with over a couple or a 1/2 dozen pints O Beer!!!
:-) -K-
Sent from my iPhone
On Oct 13, 2017, at 7:01 PM, Charlie-gm ccbibleman@gmail.com wrote:
On 10/12/2017 9:20 PM, Kurt at VR-FX wrote: Charlie - R U saying that YOU have no knowledge of VFP??
:-)
Judge for yourself of course. But I do not propagate incorrect claims about how VFP "copies down the whole table across the network whenever you open it" and things like that.
And I certainly do not remember Stephen (Bad Steve?) to have ever been a "big VFP guy". As I recall he generally put down VFP and praised the latest Microsoft "best practice" of the moment (which sometimes turned out to be a "bad practice").
Anyway, my irritation in this particular instance was his "contribution" to the topic was basically trying to "scare off" VFP'ers from the project: "doomed to fail..." Which, of course, is utter nonsense. Making sure you have someone that has a deep knowledge of the source language means the real operational requirements can be identified: why the system was designed the way it was. Lack of clear requirements is, by far, the primary reason projects fail. Also, does he think a VFP'er cannot learn C#? ROFL. The best way to learn a new language is to actually work in it: and working in it while stepping through a previous code set that you know well makes things much easier. Heck, I'd have looked into it except I have no interest in Microsoft development tools any more. I'll spend my time with Javascript, Python, some R, maybe Java.
But whatever. I don't really care that he hangs around the list (like I have any say-so about that anyway). Maybe others remember the things he's done on the list differently than I do. For me, I saw just another case of trying to back-hand insult VFP'ers - maybe it wasn't intentional <shrug>. But since he's obviously not interested in VFP any more, why post on topics specifically pertaining to VFP? My little quip in response was just trying to point that out.
-Charlie
[excessive quoting removed by server]
On 10/13/2017 8:10 PM, Kurt @ VR-FX wrote:
But - Charlie - even U admit 2 not working in VFP w/the list of tech U mentioned!
For cryin' out loud..... those languages were mentioned solely because I said I would never go to C#. But maybe the english/grammar was not clear on this point. I use VFP quite a bit: I use it to do quick proof-of-concept stuff to vet users' requirements and operational needs. But I have to be careful because I put things together so fast it makes the IT department look incompetent (they do a lot of .Net there and I'm not in the IT department). A couple times now they took away my direct database access because the users wanted to use my application for production instead of waiting another year or more for the IT solution.
Anyway, any new language I pick up will NOT be Microsoft "based" (don't bother replying about how they're all "open-source" ... and that C# is not really "MS-owned" - none of that matters - it came from MS, favors MS, tries to lock people into MS.)
Am curious - how long U been on here?
The earliest email I see I kept is back in 1996. But I know I lost some emails before that. I'm thinking I found ProFox a little while before VFP went to version 5.0, whenever that was. That is the timeframe I've been with the list. I've seen many come and go. I don't think you were on here when there was a John Peterson (spelling? JVP was his signature I think). He was quite obnoxious and also a VFP detractor like Steve became. Steve is NO WHERE near as hateful as JVP was.
This thread has drifted terribly off the original content and should have been put in the NF or OT bin already. So I'm out.
-Charlie
Shame I've retired :-)
John Weller 01380 723235 07976 393631
For anyone interested:
https://www.jobserve.com/gb/en/search-jobs-in-Solihull,-West-Midlands,- United-Kingdom/VISUAL-FOXPRO-DEVELOPER-SOLIHULL- 59A76E7DEB6D910B/
or
Dave
-
Charlie-gm -
Dave Crozier -
Fred Taylor -
John Weller -
Kurt ＠ VR-FX -
Kurt at VR-FX
-
Stephen Russell -
Ted Roche