+972 52-548-6969
70% of my job is Social Engineering
It has been over a year since the last time that I actually shipped software for production. As the NH Prof beta shipping has reminded me, this is not a trivial task. Actually, we had relatively few problems with NH Prof itself, it was with the web site that I run into a few teething issues. I am afraid that I treated the site as an afterthought at first.
Anyway, that made me reflect a bit over the last year. I discovered a very surprising truth. Most of what I do recently is not strictly technical. Oh, there is a heavy technical side for everything that I am doing, but a lot of that is simply social engineering within that context. Even my approach for API design or building a particular user experience are affected by this.
On my business card, I have a big sign saying: "Zero Friction Maintenance". That isn't something that require a technical skill, this is something that require social manipulation skills. Friction is a people problem, not a technical problem.
I am going to start a new series of post about social engineering in software development. Here is the initial topic list:
- Initiating Actions
- Delivering Confidence
- Gliding on the path of least resistance
- Walking on the Path of Success
- Failure Motivation
I probably should point out that what I consider social engineering might be considered by others as PR, politicking or playing with team dynamics.
Comments
Looks like it will be a great series, although I'm still waiting for some post on the last one. ;)
Great idea!
The timing, politics, presentation are non-technical challenges and they make a difference when you are the client-facing lead/developer in a team.
As a consultant, I find its sometimes a challenge to motivate the client to focus and stay on deadlines for feedback, review and UAT.
I like to say that software is a service industry because, according to me, it is. You work with people, you coordinate with people, the work you do is to service people. ..you better know how to deal with people at least a little bit.
Actually, dealing with people might make an interesting topic too.
Completely agree with your opinion of confidence. If the client isnt confident in your capabilities or the capabilities of your software as you start to deliver you are toast.
I have been an independent contractor 1 man shop for 15 years now. If you dont work you dont eat, and you have to sell the work before you can do it, then once you sell the work you perform all jobs from PM, to architect, to coder, to debugger, then finally you clean the toilets and leave to the next job.
You are right on target. 70% is Social Engineering. Coding in the dark is the small pleasure that is performed once the client or boss is confident you know what problem needs to be solved.
One last thing that supports your statement - if you happen to be a contractor your Social Engineering skills have to be very good or you cant sell yourself again and you go back to cubicle city as an employee.
What happens if your better at Social Engineering than actual coding?
I think I have that problem. :(
Ditto. I have the SAME time cut on a frequent basis. Fortunately right now I've been able to focus on development for an unprecedented 80+% of my time! But I know I'll have to start marketing my accomplishments sooner than later.
Comment preview