Skip to main content

Andy Kramek: Morituri te salutant

Wow - he doesn't post for a month but when he does...

So after at least one swipe at Advisor, Andy and Marcia are moving the Kitbox from FoxTalk over to Advisor. (a revolution from within may begin... )

The why is one of those not well-guarded secrets in the FoxPro world. FoxTalk was recently taken over by Eli Research who adopted their own formatting guidelines fairly tight restrictions(see comment) over the writers and editors. With such a wild bunch as the FoxPro community, it only stood to reason that some more shakeups would occur.

FoxPro Advisor now gets two of the best writers around - what a great coup - because the KitBox is one of the best reads around.

It's going to be interesting - Advisor may become more like FoxTalk and FoxTalk may become more like Advisor with its new layout.

The result? More FoxPro articles abound for all developers to read and we, the community, are wealthier for it.

Andy Kramek : Morituri te salutant (Those who are about to die, salute you)

Comments

Anonymous said…
I'm not sure that "fairly tight restrictions" over writers is fully accurate. Just as Ragan had its own formatting standards across its journals, Eli Research has its own formatting. For example, figures were numbered under Ragan, but lettered under Eli Research. There were a few other formatting changes, but the Kit Box was exempted from most of them.

I think this is mostly about the fact that some people have the need to react a certain way to minor changes that wouldn't bother most people. I understand that; people react in different ways, and they do what they have to do, based on what's right for them.

We certainly regret Andy's and Marcia's leaving, and wish we had had more of a chance to respond to any concerns that they had.

We'll do our best to continue to accommodate the needs of top-notch VFP writers, and to be attentive to the suggestions and wishes of our subscribers.
Andrew MacNeill said…
Thanks for the corrections - I've revised my posting to be a little more accurate.

I look forward to seeing what the new FoxTalk looks like.

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