Monday, August 15, 2022
HomeCloud ComputingWhat I discovered by doing tech assist

What I discovered by doing tech assist


It was after 11 PM and an invitation for a compulsory staff assembly popped up on my telephone, from the director, for 9 AM the next morning. This can’t be good, I believed . My fears have been confirmed throughout the assembly: the product that my staff had developed from the bottom up over 6 years was being migrated to a bunch abroad. My job was being eradicated.

Administration provided me a task in one other enterprise unit, nevertheless it was to offer developer assist — for the product that I had invested 6 years of my life constructing. My response: dismay and anger. I’m a full stack engineer. Assist, I believed, was a waste of my expertise. I discovered the supply offensive.

However within the curiosity of household stability, I took the job. I might do that for a short time not less than, I believed. 5 5 years later, I’m completely happy I did. I’m grateful that circumstances pushed me to take a job I didn’t need. As a result of it made me a greater software program engineer.

The assist position helped me to see that I used to be residing in a developer’s bubble, and that I didn’t really perceive the tip buyer of my work. Had I by no means taken the assist position, I would by no means have.

My profession has continued to evolve since that transition, however the classes I discovered from my time in assist have stayed with me. Listed here are the large ones:

Know your buyer(s)

The software program you might be constructing might serve multiple buyer persona. For instance, if the product exposes APIs, the persona of the API person is sort of actually completely different than the persona of the buyer person of the product. Understanding every persona, by figuring out their wants and challenges, permits builders to design each bit of the product accordingly.

Additionally, don’t overlook to jot down persona-specific documentation. Your clients and your assist staff will discover it extraordinarily useful.

Don’t assume experience

Builders typically consider that the shoppers of their software program and APIs are specialists within the expertise, course of, or enterprise related to the product. More often than not, they aren’t. Once I was offering API assist, I discovered that the majority clients fell into two classes: They have been both knowledgeable within the product, however new to growth due to the change of their job position; or they have been contracted builders who knew how one can code however didn’t perceive the product and expertise, or the enterprise. So within the product itself and within the documentation, you have to use phrases which are clear to a novice person. When writing documentation, outline industry-specific phrases. Spell out all acronyms. Clarify the options and APIs as if the person is model new to the expertise.

Admire the client’s atmosphere

A buyer’s atmosphere is nothing just like the developer’s testing atmosphere. Prospects will push the boundaries of what’s supported. Some will go method past what your organization considers the bounds of assist. The shopper atmosphere can also be sometimes advanced and comprised of quite a few merchandise built-in collectively. Builders have a tendency to check merchandise within the easiest supported atmosphere resulting from {hardware} and budgetary constraints.

Prospects have management

“That’s not supported.” These have been my favourite phrases as a developer as a result of that meant we didn’t must deal with these situations. Once I turned a assist engineer I discovered that my favourite phrases have been meaningless. If the product doesn’t actively limit the purchasers from what’s unsupported, the client is probably going to make use of it in simply that method and nonetheless count on full assist when it doesn’t work. When a high-profile buyer does this, what was initially unsupported would possibly should be supported ASAP. Which suggests builders must drop the whole lot to make it occur.

Have a look at the large image

When software program is developed, options and APIs are cut up amongst a number of teams of builders and are labored on in parallel. This can be a affordable tactic for getting advanced software program written, however builders which are targeted on their particular person deliverables can fail to grasp the client’s end-to-end use instances and circulate. We are able to assume the client will take a sure path, however assumptions hardly ever match actuality. By understanding the client’s use instances and flows, builders (and undertaking managers) can cowl all potential mixtures and paths. That is primarily a problem of inner staff communication and coordination.

Doing assist was extra beneficial than I anticipated

To my shock, being a developer assist engineer ended up being very rewarding. I’ve all the time taken pleasure within the software program that I develop. It was fulfilling to see it being utilized by massive and respected firms, and to speak to the individuals who have been utilizing it. . I discovered so much concerning the clients, and gained empathy for his or her struggles. I’m a greater software program engineer than I used to be earlier than. I can now advocate doing assist – not less than for a brief time period — to any developer.

See Cisco DevNet’s Coding Studying Labs!

Come meet me at Cisco Reside in Las Vegas, June 13 to 16. I’ll be within the DevNet zone, working a Python Superior workshop — amongst different actions. Join at this time!


We’d love to listen to what you suppose. Ask a query or depart a remark under.
And keep linked with Cisco DevNet on social!

LinkedIn | Twitter @CiscoDevNet | Fb Developer Video Channel




Most Popular

Recent Comments