Skip to main content

New role: Lead Dev

A few weeks ago I started my new role as the Lead Dev for my company's summer intern project. We have 10 weeks for a leader, myself, another full time developer, and four student interns to join as a team and create a working application from scratch. In the Lead Dev position I will be focusing most of my time teaching the interns and building them up rather than directly coding the application. I will find ways that I can stop hurdles and roadblocks from slowing progress, while helping the interns gain insight into what goes into building an application. 

Our first couple of weeks together have not been focused on writing code and more on less technical things. We have done team building exercises and already feel like a solid team with everyone willing to share their own ideas. We have defined the requirements for our project and had sketching sessions to mock up what our application it's going to look like. We have taken those sketches through several rounds of feedback coming up with a better solution than any individual idea we had at the beginning. 

Towards the end of this week we were able to start writing code for our actual application. As we have started teaching our technologies, we have taken the approach of all working together focused on the same task. This had worked really well as the interns are getting to see everything that is happening as well as helping each other out if someone gets stuck. We stop to ask questions and work through the thought process a developer would likely use to solve a problem. By the end of the week we had built out a navigation system and a placeholder for each page allowing us to prove out that the navigation worked. It has been super cool to see how much we have accomplished in such a short amount of time.  I believe we accomplished so much because the team is lean, focused, and engaged. 

It had been an incredible first couple of weeks. I have learned so much by leading and teaching and not just doing. It had been awesome to see the interns really jump right into their roles and to see how each one learns differently. I look forward to all the awesome things we will learn together this summer and plan to share more here as we do. 


Popular posts from this blog

Converting a Large AngularJS Application to TypeScript Part 1

I work on a project that uses AngularJS heavily. Recently we wondered if using a preprocesser like CoffeeScript or TypeScript for our JavaScript would be beneficial. If our team is going to switch languages, we would need to be able to convert existing code over without much pain and we would have to find enough value in switching that it would be worth the conversion. I had read an article that stated that because TypeScript is a SuperSet of JavaScript, you could convert a plain JavaScript file to TypeScript by changing the extension to .ts and not much else would need to change. I wanted to test out this claim, so I took a file that I was familiar with, an Angular Controller, and tried to convert it to TypeScript to see how much effort it would take and then try to figure out where we would benefit from using TypeScript. This is what the controller JavaScript file looked like to start out with: ( function () { 'use strict' ; angular .module( 'app'

Interns: Taking off the training wheels

My intern team has been working for several weeks now on our new website. We have already completed one deployment to production and are finalizing our second one. We started with a plan to release often adding small bits of functionality as we go and so far that plan has been working really well. We already feel like we have accomplished a lot because we have completed many of our project's requirements and should easily be able to complete the rest giving us time to do even more than just the original requirements. One of the things I have had some difficulty balancing has been how much to lead the interns and how much to let them figure out on their own. In deciding what our team process should be and how we should allocate our time, I think it was important for me to do more leading. I saw some deficiencies in how we were currently working and brought up some ideas for how we could address them. We had moved into spending all our time just working through stories and did not

My idea for Hearthstone to add more deck slots

Recently someone asked the Blizzard developers for more slots for decks in the game Hearthstone. The response was that they are talking about it and looking into it, but no decision has been made yet. One of the concerns over adding deck slots is that it could complicate the UI for Hearthstone and make it more difficult for new players to understand. I have what I think would be a good solution to add more deck slots without increasing the learning curve for the game much if at all. First I would take a look at the current selection screen for starting to play a game. It defaults to showing the decks that are custom built by the player if they have any custom decks, and there is an option to page over to the basic decks. This basic deck screen is perfect for how I would change this process. Instead of having 2 pages of decks, 1 for basic and 1 for custom, you would just see the select a Hero screen. Then once you selected the Hero you wanted, you would see all of the decks that