The name placard in your cube might not say anything about sales, but the truth is that everyone, employed as such or not, is a salesperson at some point every single day. In the traditional sense, this could mean something like pitching your company’s solutions to a client. In the less-traditional sense, it could mean convincing your child to eat their vegetables. Yet for those two drastically different examples and everything in between, there is a constant for successful sellers: unveiling the “Why.”

Spending time and energy making prospects understand why you do what you do instead of exactly what it is you do or how you do it is not a new concept. But I’m a firm believer that proven concepts, no matter how old and frequently referenced they are, can’t be repeated enough. This idea has recently and fervently been popularized by marketer, author, and thinker extraordinaire Simon Sinek via his 2009 book, Start With Why. You can learn about him here on Wikipedia or here on his site. To begin, let me suggest that you watch Sinek’s TED talk on Starting With Why here on YouTube before reading any further. I’ll let him take care of the bulk of explaining the basics, and then will offer some ideas of my own to back this up in the real world and explore the best ways to start thinking this way and apply it to your business.

First, a little on me. After all, if I were to practice what Sinek preaches, it would follow that I explain why it is I’m writing this piece so that you, the reader, not only have a good reason to pay attention but also understand what drives me on a deeper level. So, who am I? I’m an entrepreneur in the music space. I do freelance work in the realms of copywriting, business development, and marketing for artists and industry / music-tech folks, but my main project is doing all of the above for a project I’ve been on the team for since day one called Presskit.to. In short, Presskit.to builds digital portfolios that artists of all kinds can use to represent themselves professionally when pitching their projects to gatekeepers like label reps, casting directors, managers, the press, etc. This core technology is also applicable to larger entertainment industry businesses and fine arts education institutions in enterprise formats, and solves a variety of the problems they’re facing.

Not interesting? I don’t blame you for thinking so, if you did. That’s because I just gave you a bland overview of what we do, instead of why we do it. What if, instead, I told you that myself and everyone I work with is an artist of some sort and believes that the most important thing you can do in life is create; that our technology exists to make creators’ careers more easily sustainable. Or, another approach, that we think the world is a better place when artists can make more art, and that because our technology was built to help artists win more business, we’re trying our best to do our part. Only you can be the judge, but I think that sort of pitch is more compelling. It touches on the emotions responsible for decision making that Sinek outlines in his Ted Talk, rather than the practical language-based reasons like pricing, technicalities, how everything works to accomplish given goals, etc. These things are on the outside of the golden circle Sinek shows us for a reason – they only really matter if you’ve aligned your beliefs with a client’s first. Otherwise these kind of tidbits are gobbledygook, and mind-numbingly boring gobbledygook at that.

It’s the eternal conundrum of a hiring manager – you have to hire for every single position in the company without any first-hand experience. How to do it? If you can have a trusted programmer sit in on the interview, that’s ideal, of course. But what if you’re hiring your first programmer? Or what if you’re hiring a freelancer? Or what if company policy dictates that you’re the only person allowed to do the interviewing? Well, in that case, you need some helpful advice and your innate bullshit detector. We questioned programmers and hiring managers and compiled a list of dos and don’ts. Here are some things to ask when interviewing programmers:

Past Experience

Ask the programmer about the biggest disaster of his career so far, and how he handled it. Did he come in at midnight to fix the code? Was he unaware of the problem until someone brought it up? Did someone else handle it?  According to our programmer sources, “Anyone worth their salt has caused a major meltdown. If they say they haven’t, they’re lying. Or very, very green.” Pushing a code with bugs in it isn’t necessarily bad. Not handling it well is bad.

As usual, your biggest asset is not knowing the field, it is knowing people. Asking about career disasters can be uncomfortable, but if the interviewee is experienced and honest then she won’t have a problem telling you about it, and you will get an idea of how she handles mishaps. Even if you don’t understand what the disaster was or how it was fixed, you should be able to tell how honest she’s being and how she handles being put on the spot.

Being treated like a twelve year old at work by a Tasmanian-devil-manager and not sure what to do about it? It is simply a well-known fact that no one likes to be micro managed. Not only do they not like to be micro managed, but tend to quit for this very reason. Unfortunately the percentage of people leaving their jobs for this reason is higher that you would imagine. Recently, an employee retention report conducted by TINYpulse, an employee engagement firm, surveyed 400 full-time U.S. employees concluded that, "supervisors can make or break employee retention."

As companies mature, their ability to manage can be significant to their bottom line as employee morale, high staff turnover and the cost of training new employees can easily reduce productivity and consequently client satisfaction.  In many cases, there is a thin line between effective managing and micro managing practices. Most managers avoid micro managing their employees. However, a decent percentage of them have yet to find effective ways to get the most of their co-workers.  They trap themselves by disempowering people's ability to do their work when they hover over them and create an unpleasant working environment. This behavior may come in the form of incessant emailing, everything having to be done a certain way (their way), desk hovering, and a need to control every part of an enterprise, no matter how small.

Superimpose the micro manager into the popular practice of Agile-SCRUM methodology and you can imagine the creative ways they can monitor everything in a team, situation, or place. Although, not always a bad thing, excessive control, can lead to burnout of managers and teams alike.  As predicted, agile project management has become increasingly popular in the last couple of decades in project planning, particularly in software development.  Agile methodology when put into practice, especially in IT, can mean releasing faster functional software than with the traditional development methods. When done right, it enables users to get some of the business benefits of the new software faster as well as enabling the software team to get rapid feedback on the software's scope and direction.

Despite its advantages, most organizations have not been able to go “all agile” at once. Rather, some experiment with their own interpretation of agile when transitioning.  A purist approach for instance, can lead to an unnecessarily high agile project failure, especially for those that rely on tight controls, rigid structures and cost-benefit analysis.  As an example, a premature and rather rapid replacement of traditional development without fully understating the implications of the changeover process or job roles within the project results in failure for many organizations.  

A career in the field of software development remains immensely popular due to various factors. Chief among them of course is the higher compensation and lucrative pay scale in the IT industry when compared to other career options. In addition, the flexibility of work hours and the sheer sense of achievement experienced by one while creating new programs are unsurpassed by any other job.

Popularity and reach of Software Programs

Software programming has become a quintessential part of our day to day life, right from the smartphones in your pocket, to video gaming, and everything in between. The opportunities in this field are truly astounding. The niches for specializing are also diverse, from creating operating systems, to mobile app development, or web app development to name a few.

There are various ways in which you can distinguish yourself in the market for the much coveted title of software programmer. Here, we focus on some of them.