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

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...