Skip to main content

So where are all the FoxPro developers?

15 years ago, it was relatively easy to find developer communities - they existed pretty much in one place: CompuServe. Over the past 15 years however, they have spread out to wikis, newsgroups, independent sites (such as the UT or Foxite) as well as many who have gone into hiding. There are now tons of social networks out there and while some may dwell more on the social aspect, such as Facebook (which does have its own FoxPro group), others are more business related, such as LinkedIn.

When I first joined LinkedIn, I linked to a number of developer associates as either "past speaker at conferences" or other relationship concepts along those lines but since then LinkedIn made creating groups much easier. As soon as I created the FoxPro developers group, developers started to join.

The link is here:

LinkedIn: FoxPro Developers Group

What do you do with it? For starters, not much right off the bat. It's a pretty easy way to find other FoxPro developers you know and add them into your LinkedIn network but recently, LinkedIn started adding Discussions as a way for groups to communication so now there's a new tool as well. It's not really intended as a replacement for any UT or Foxite or ProFox where regular discussions are held but it will become whatever it becomes.

If you aren't using LinkedIn, it's a good business resource - as opposed to a traditional social networking site - and it works really well for finding former co-workers or others in a similar area.

Check it out and join the group!

Comments

Anonymous said…
YFI: The European version of LinkedIn is XING. The FoxPro group there can be found at https://www.xing.com/net/foxpro/
Eric Selje said…
Coincidentally I was on LinkedIn this morning and saw that there was some activity in the discussion group. The first thing that crossed my mind was "Jeez, how can anyone keep up on the myriad places where developers post questions nowadays?" It was definitely easier in the past when we were consolidated.

The second thing that crossed my mind was, "Wow, that MacNeill really contributes to a lot of different places." Well done.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...