When did it become acceptable to deny content, based on certain criteria, because it was inconvenient?
Tag Archive / coding
There is this “thing” that has been nagging me for almost a year.
Basically, it’s a conversion that I had with a CEO of a company. Anyways, during the course of the conversation, he brings out this remark:
“Your job is to code, just like the designer’s job is to design.”
That comment bothered me. It wasn’t a comment bore of malice or ignorance. It had some truth to it. But it missed an important point. It was the equivalent of saying “My job is to write HTML.”
Now, there’s nothing bad; that is part of my job. But only a part.
No, my annoyance is this:
If my job was just coding, then I’m not doing a good enough job.
OK. Let me explain.
Coding is (relatively) easy. Businesses can pick and choose what company or freelancers to do the work. For a cheap price, the work can be farmed out to anyone of the many off-shore companies at will.
Altogether, that the big talent pool of coding talent.
You, (client/CEO) have to go through this massive pool to find the right person. But that is not what you are looking for. The truth is that you are not looking for someone to code.
You need someone to solve your problem.
As for coding? It’s a means to an end. Employers don’t hire people who code; they hire people who can solve their problems. (And also it’s the same thing that will keep them around…)
Now, I wish he was around when I said this. I have no doubt that both of us would be agreement.
There was another thing that he said, in jest, but in hindsight just as important. Basically, people like myself like the “shiny, new projects”. And yes, I admit, they are the nice ones to work on.
But. There is a group of problems, the “old – fixed it just for now” problems that really need attention. The ones that are begging for someone to just look at and say “you know, if you give me some time, I think I could make this better.”
There are lots of those problems that need serious attention, not the million dollar, new app of the month ones.
Then, there is The Content Problem.
The role of a front-end developer is to build interfaces that give the user access to information with the least amount of interference.
— Ivan Wilson (@iwilsonjr) January 28, 2013
I want to apologize for all the bad coding decisions that I have made during the last couple of years. A number of decisions were made with ignorance as the impact they may have made in terms of performance. Some of those decisions may have been made without consideration for the user.
If I seem out of sort during the last couple of week, it was simply because the changes I need to make will require changing not just code but a mental process. Like anything, this will take more than a fortnight to change. It is a process of renewal and making mistakes and just throwing stuff into the trash bin.
What I need is some understanding and some patience while this process works itself out.
This is not a joke.
If you are laughing at this, I understand. It still won’t change anything.
Let me explain.
In 2009, through contact with interaction designers, I saw the coming wave that we now call mobile. That wave moved so fast that it took everyone by surprise. Today, designers and developers are dealing with this via responsive design and other techniques.
Now, what does it have to do with me. One day recently, I was tasked to revised some code I made in late 2009. Now, it was good by those standards but it has a few faults. Not perfect but usable and everyone was satisified.
At the time, it was "Job done. Go to sleep."
But I didn’t.
What does one write about on a two hour plane trip to Chicago?
coding, mobile, Shadout Mapes, Churchill, and John Lennon
Important? What does this mean?
Well, you’ll find out in the next blog entry…