Skip to main content

Publish or Perish

Back in 1999 or 2000, I showed up at a North American FoxPro conference after being away for several years. I hadn't been invisible during the previous few years. Instead, I had been focusing on promoting development efforts local to me in Ottawa, Canada. I had done a number of Microsoft DevDays and training in the area. But in terms of the international community, I had effectively "disappeared".

I think this happens more and more especially as people stop writing on one site and then start on another. One might be forgiven for thinking that Lisa Slater Nichols had disappeared off the face of the earth years ago when, in fact, she had merely moved into a different development environment and writing of SSRS. One of my favourite memories of Ms. Nichols was when I first met her in 1991. Everyone wanted to talk to her and my colleague had no idea of who she was. Someone said "This is Lisa Slater." He looked at her and said "You're the only Lisa Slater in the world?" Her quick wit showed forth - "You don't get on CompuServe much."

This post isn't to go back and reminisce, although one can find the recent exciting efforts of former FoxPro developers here and here. And the world of database development is really exciting...big data, business intelligence, NoSQL, PaaS, and it's hard to know where to go.

I've never stopped writing - in fact, I use the site 750Words to try and write every day. But it's not "out there". It's not adding to the public discourse of work and development as my original goal of writing on this spot was.  Should I move to another site to write? Many are now using LinkedIn or Medium as their posting mechanism. Despite being one of the first group of podcasters, the FoxShow podcast has limped along slowly to where it comes out once a year, primarily to showcase the latest comings in Southwest Fox.

So it's time to start publicly stating my process again here, sharing my experiences in the development world, thoughts on other key areas, promoting a few new initiatives, and adding value, hopefully, to your world, whoever you may be. Agree or disagree, similar or different experiences, or even better, new products and ideas...let me know. One thing is true...I haven't perished...just haven't published in a while. And it's time to restart.

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