In episode 15, Jamison and Dave join Brad Green, engineering director at Google and Angular team manager, to answer these questions:

How do I deal with non-technical people at work? I often get questions that put me into a position where I have to explain really basic concepts to non-technical people like sales and marketing. They seem to rely on me like a crutch, and it gets tiring to have to explain things over and over. How do I strike the right balance of being helpful, but not so helpful that they become dependent on me? I want to be helpful, but I don’t want to spend 90% of my time acting as tech support.

How do I keep up with new technology but avoid being sucked in by hype?

In episode 14, Jamison and Dave answer these questions:

Since I am primarily a web developer, I often find there is a bit of developer prejudice, against web developers from software engineers of other categories. Often I find they think I am not capable of anything other than jquery dom manipulations, and talk down at me like I wouldn’t understand their expertly setup mysql queries. As it turns out, I too have my CS degree, and start new projects in all kinds of programming languages just to learn them. Any tips for breaking the web dev stereotypes?

How to deal with legacy code and legacy coders? The code was probably good once, but it is impossible to maintain and doesn’t work on new hardware. You know the best approach is to scrap it and start from scratch but the original coder is resistant and wants to find a way to “make it work”. What do you do? In my situation, this legacy coder is a peer, and the only person above us doesn’t want to take a side on the argument, so we are left at a stale-mate.

In episode 13, Jamison and Dave answer these questions:

What should you do about a boss, or in my case ‘solution architect’, who won’t push back to the client and just keeps sacrificing quality of the product to push more features out?

What’s the difference between contract and permanent positions?