Skip to main content

David Stevenson's Talking Fox: Writing for free vs. writing for publications

David, I didn't think it was so much an advertisement for FoxTalk but I am glad to hear about the new online only subscription.

Myself - I get it three ways -
a) I talk about a product that I'll be covering in FoxPro Advisor on the FoxShow podcast
b) I typically do a screencast about it (or did one recently) as well as blog about it
c) the final article goes into FoxPro Advisor

The difference?

1. The article usually covers a lot more of "how to do" stuff. Much in the same way a book might cover the details, a posting that refers to content in a book only covers the basics.

2. The screen cast is, perhaps, the most ideal way of viewing it because it shows the ease of use.

3. The podcast works because it usually happens that week, the week before the article is sent off.

That said, I also have my own Articles and Writings page. I don't put ALL of my articles on there (as many are fairly time sensitive) but I do recall a Devcon 2001 (?) meeting with Susana, Tamar, Pamela and Christof in which it was stated that as long as the body of the article has changed somewhat that it can be posted for public consumption. Wonder if that's the same for FoxTalk...

David Stevenson's Talking Fox: Writing for free vs. writing for publications

Comments

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

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

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP