Clif wants us to stop "ducking." He talks about how changing habits within
your IT department can make all the difference in the world. This article
explores some behavior patterns that make MultiValue databases look old and
hard to work with. See his suggestions on some minor changes you can make in
your IT department to make it more appealing to new developers.
In part one, we discussed some of the things we could do (and a number of
things not to do) to attract new blood to the MultiValue community. Now
let's talk about some of the things we need to do, not only to attract
Millennials to our shops, but also to keep them. It does us little good as a
community if a bright, energetic, young developer joins our team, suffers
their own version of "burnout," and two months later quits because they are
bored to tears. Or if they are embarrassed to admit to their cohorts what
they do for a living.
I just don't believe it. I don't have an MBA and never took any marketing
classes. But it seems to me that announcing, "sure our product sucks, but it
doesn't suck as bad as our competitor's," is a rather bizarre way of getting
new customers or making existing customers happy with their purchase
If you haven't already read Nathan Rector's From the Inside column this
issue, I would strongly suggest you turn to the front of the magazine and do
so. He is requesting help in getting the word out that MultiValue is alive
and well and quite able to tackle your modern application requirements. It
is also very capabile of fitting into a "mainstream" IT shop having a number
of different platforms working together. But as long as there are only a
handful of us who write articles or blog entries about the kinds of problems
we have solved using our various MultiValue platforms and the techniques we
used to do it, as a community we are going to continue to appear to be much
smaller than we really are. Whereas other platforms have dozens of writers
publishing articles for various magazines, journals, and newsletters, in the
MultiValue world it seems like you see the same bylines over and over. Not
that there is anything wrong with seeing certain writers consistently
producing articles! But when those are the only writers you see, it gives
the impression that there must not be very many people using this thing,
otherwise you would see a lot more people writing about it and discussing
it. I think he did an excellent job explaining some of the issues and
shooting down some of the myths about what it takes to write an article. Now
I would like to add a couple of thoughts then share with you an idea about
how to make the process even less daunting.
Well surprise, surprise. I bet long-time readers never expected to see this
column, let alone the current lead article of the magazine, be about New
Year's resolutions. If you look back in the last two to three years of
January-February issues at Clif notes, you will see that I have a habit of
poking fun at the idea.
A while back, our Content Editor, Shannon Stoltz, introduced me to a book
by Rajesh Setty titled Beyond Code: Learn To Distinguish Yourself In 9
Simple Steps. It is targeted at the IT professional who wants to break out
of the rut of constantly rushing to acquire another skill (programming in
Python, for example) only to find out they have become what he calls a
"commodity"— just another Python programmer easily replaced with any other
Python programmer (at least in the perception of upper management).
Many of you have heard (probably ad nauseum) of Edward Snowden, an employee
of a contractor to the National Security Agency who took it up upon himself
to divulge a number things about NSA's intelligence gathering activities.
The information has caused quite an uproar, not only within the United
States, but also in other countries. But Snowden is not the main topic of
this column. Some think that he is the highest form of traitor. Others think
that he is some sort of hero figure. (Personally, I think he's a
narcissistic little pinhead.) Let's talk instead about how people have
reacted to the information "leaked."
I think I set a new efficiency record this New Year. I have never been into
New Year's resolutions very much. With 365 days in a year, I don't
understand waiting for a particular one in order to make a decision to
accomplish something in the next 364. But, it seems to be a cultural
tradition, not unlike the ritual of eating certain foods on New Year's Day
in a magical attempt to woo Lady Luck or the Goddess Ifni to smile upon us.
Nevertheless, this year I decided to participate.
I used to enjoy the holidays.
The year 2013 is barely underway, and I already feel like I'm falling
behind. What a great time to be a MultiValue developer. There are just so
many new toys to play with technologies to explore that I hardly know where
to start. Unless a person is a MultiValue couch potato, clinging to their
outdated skill set and hoping to just slide by without learning anything new
until they can retire, how could anybody be bored? With all of the major
MultiValue platforms now having good connectivity to the latest modern
technologies, there are numerous adventures opportunities to move the user
experience off of the database and let MultiValue do what MultiValue does
best — model data, store and retrieve it efficiently, and provide the
application developer with a cost-effective database that is flexible, easy
to work with, and doesn't insist on getting in the way of what you're trying
to accomplish. Here are a few examples of what I'm talking about.