2016: Year In Review

I had a lot of professional growth goals this year and that included speaking, blogging and engaging my community more. I ended up doing a lot more in 2016 than 2015. 

My goal for 2017 is to keep it simple and do less :)

January

Wrote abstracts for all the conferences I wanted to attend/speak at and laid the groundwork for the year ahead.

February

Ran my first Android Study Jam for Google Developers Group(GDG)/Android Alliance Philly which I co-organize.



March

Gave a lightning talk at GDG/Android Alliance Philly on RecyclerViews which was part of my talk on Material Design implementation for Developers

April

Gave a talk at GDG/Android Alliance Philly on Material Design implementation for Developers.

May

Did an AMA with the AnDevCon Boston team to promote my talk on Material Design.

Attended the global GDG conference in San Francisco and Google I/O in Mountain View which was a blast as I got to hang out with members of the Android and Google tech community from all over the world!


June

Moderated my first panel "Ask an Android developer" at GDG/Android Alliance Philly

Attended  Write/Speak/Code in beautiful Chicago!



July

Spoke at 360|AnDev Denver which was a very well organized conference (and it was their first time running it!)

August

Flew directly from Denver to Boston to speak at AnDevCon for the second time.

September 

Spoke at DroidCon NYC for the second time.

October

Co-Organized the first DevOpsDays in Philly. Was also an MC on the first day of the conference which was fun!

(MC image credit: Talya from Hailey Photography)


November


December

Downtime! Took a much needed break after a crazy whirlwind of a year!









Comments

Post a Comment

Popular posts from this blog

Communicating Paid Time Off and Coverage Plans

Image
As an engineering manager, I often ask people to take at least a week off every quarter depending on the PTO (Paid Time Off) policy at their workplace. This comes up to 4 weeks or 20 business days in a workplace with unlimited PTO which is pretty good for US-based companies, where the standard is usually 2 weeks or 10 business days of PTO.  It’s also important to me to communicate to my teammates and people across the organization that I will be out of office and they can reach out to others in that situation. “How we vacation” is a section that I like to add in my Team Charter which is a document that contains all the rules of engagement on a team - how we do retrospectives and team meetings, how often we meet, how we take time off, how we track metrics, our scope of work, and so on. 🌴 Paid Time Off Here are some of the places I update at my workplace if I am going to be out on vacation for a few days: Slack status Company Time Off calendar My work calendar My Google workspace o...
Read more

Team Charter and Norms: Working together

Image
In my previous blog post , I wrote about setting up a Team Charter and Team Norms on a team. In this post, I elaborate on some of the rules of engagement that teams I have worked on have generally used. Most software development teams that I have worked on have used some sort of Agile practices like the Scrum framework where cross-functional teams use iterative and incremental processes to improve their software delivery process. I have always used Agile in a way that works best for my team and the company’s culture at that time.  🧱 Team Structure I have had to occasionally run Scrum meetings as an Engineering leader since I have been on teams without dedicated Scrum Facilitators or Product Owners. Each Scrum team usually includes an Engineering Manager, Scrum Facilitator or Project Manager, Product Manager and Developers. In the absence of dedicated Project Managers or if there is leadership interest on the team, I make the Scrum lead role rotational so that every person on the t...
Read more

Team Charter and Norms

Image
A Team Charter in the context of a software engineering team is a team document that lists their goals, objectives, scope of work, and rules of engagement. This is a working agreement between all members of the team on how the team collaborates and communicates, and how they hold each other accountable while working towards common goals. Here are some areas I like to cover in a team’s Team Charter. This can be at the team level or the organization level.  Goals: This is a one-line sentence that explains the goal(s) of this team.  Objectives: This section links to the team or organization's objectives, key performance indicators (KPI) or Objectives and Key Results (OKR) which can be quarterly, semi-annual or annual. Organization Chart and Team Structure: This helps people know where they are in the organization and what teams and people they interact with regularly. Helpful Resources: This links to the team’s Request For Comment or Technical Design Documents, Slack channels, me...
Read more