Skip to main content

How would you reach Fox developers?

Eric Sink writes a great post about marketing to developers: How would you reach YOU?



I read this and immediately thought of Kevin's Keynote post - how surprised he was with the people who were hearing the announcement for the first time.



Obviously the FoxPro community has a lot of different avenues: devcons, user groups, forums, podcasts, magazines and perhaps more importantly, right within the product itself, the task pane.



So why are developers not hearing about the news? What can we do to make it clearer?





Powered by ScribeFire.

Comments

Hank Fay said…
The fact is that perhaps 1,000 or so fox developers are "in the know," in the sense of being in the actively communicating fox community. This isn't a bad thing: it means that it's possible to be productive on a daily basis without having constant communication with those who have had additional experience. Try developing in WPF without being in constant contact (at least reading) communication...

For the most part, these developers (and I know .Net developers who are the same) don't care to be reached: they just care about doing what they view as their job. We probably ought to simply respect their wishes.
Anonymous said…
I'm struggling to get the word out about FoxForward. Last year, a developer learned about the conference on the day it began. I'm making posts in every location I can think of, short of paying for advertising.
Anonymous said…
Kevin's comment and yours resonate for me. For Southwest Fox, we're trying hard to figure out how to reach those VFP developers who aren't plugged into all the online communities, the ones who maybe read a magazine now and then and may or may not have any VFP books on their desks.

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

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

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...