Congrats! You're the tech lead - now what? Eryn O'Neil

Congrats! You're the tech lead - now what? Eryn O'Neil | The Lead Developer New York 2017

Рет қаралды 37,772

Күн бұрын

Join us for our next conference: goo.gl/B2bqQ6
You’ve been programming for a while now. You know your way around the code, and you’re becoming a go-to for technical advice. And it looks like someone else noticed, because you’re the technical lead on your next project. Congratulations! But now what? It’s a lot more than just coding: The technical lead can be responsible for designing software architecture, writing requirements, interfacing with clients or management, or dividing work amongst the team- and those are just the parts of the job they tell you about ahead of time.
We’ll talk about how to oversee the technological vision for the project without losing sight of what’s happening on the ground, how to motivate your team members without overstepping your bounds, and some tactics to deal with challenges you might not anticipate, but will almost certainly encounter.
Eryn O’Neil is a Minneapolis-based freelance PHP developer and tech lead. Grounded in the agency world, she has worked on everything from e-commerce and online promotions to a proprietary framework and CMS. Her philosophy is to build software by placing humans first: both the people who will use it and the developers who will build it with you (and maintain it afterward).
Living in Minnesota, Eryn spends most of her free time teaching blues dancing, flying on a trapeze, and wishing it weren’t snowing.
---
When you’re busy leading a team, coding and maintaining standards, how do you find the time to stay ahead of new technologies and develop yourself as a technical lead?
The Lead Developer conference features practical advice from experts on leading and motivating your team and high-level sessions on new and disruptive technologies.
Get tickets at theleaddeveloper.com

Пікірлер: 19

@SubtleAsh-TheImmortal 4 ай бұрын

Fantastic talk, Eryn. Here is the summary for folks: Facilitate, Advocate, Motivate the team and the technological vision Facilitate: Always ask yourself - what's next - Remove roadblocks - Perceive the need -- Tactic #1 --- Tickets, hours and burndowns - be data centric to back your decisions --- Know the answers or point them - I don't know but... I will find out Advocate: - Advocate for your team and give them the context to enable them to take decisions -- Tactic #2 --- Write down everything to avoid ground hog syndrome --- Advocate : Developers, Mgmt, Clients --- Say NO to scope creep Motivate: Your attitude sets the tone of the team - absorb the crazy - Lesser complains = better solutions You're not writing the solution but you're responsible for it You can't wear the IC hat as much as you did - accept it!

@ayusharora8141 23 күн бұрын

very well put

@Dtsun16 Жыл бұрын

Wow this was an incredible talk. Thank you very much for sharing in such a clear way

@papanino4415 4 жыл бұрын

Well structured and well explained. Great talk.

@JohnKerbaugh 6 ай бұрын

Thanks for the talk. Saving to refer back to this one.

@PizzaPizza_99 5 ай бұрын

This was really good. I wished I listened to this video when I first got my tech lead job as I didn't know what it really entailed

@nonamezz20 8 ай бұрын

awesome talk !

@Rare.99 Жыл бұрын

I only have one guy working on my GDD and the pressure is real!

@anythingwithgkc Жыл бұрын

good speech. learn lot

@lesto12321 4 жыл бұрын

realizing i am doing passive-aggressive whiteboarding since forever and never though about that as tool reather than an inconvenient.

@gearboxworks 4 жыл бұрын

Really good and useful talk.I took tons of notes I am taking on an official tech lead at an org after having been the unofficial tech lead for a decade at my own company/micro-agency/dev shop. So I am certainly not an expert here. But I can't help but feel that a one of the things discussed regarding "Facilitate" is more for the project manager role vs. the tech lead, e.g. coordinating people outside the team for unblocking. Am I wrong here, or no? If I am wrong, why is this more of a tech lead role and less of a PM role?

@baz5719 4 жыл бұрын

Hey Mike, that's a great question and got me thinking. I suppose one way to think about it would be from the example of "no but.." so when you're asked "we need X by Y" coming back with "we can do that, but we need Z" or, "We can't because of A" is a _form_ of facilitating beyond the boundaries of your team. It might mean finance or marketing need to do something in order to reach a particular objective. That's not to say it isn't for the PM to do, but you can support them or even take on that responsibility as required. One aspect where being the TL can add weight here is often you'll have the technical responsibility / domain knowledge and or data to back up your claim. In this instance, the PM may very well just be the messenger so it could be more effective coming from yourself, as the lead. Just some thoughts.

@genyklemberg Ай бұрын

Nicely structured without any water. Good job. Or not, water was actually, one for the pretzels😅

Жыл бұрын

We de simplified

@coderider3022 7 ай бұрын

So basically the best Dev being tied up as nanny to less capable Devs ?

@JohnKerbaugh 6 ай бұрын

Some of this can be resolved with good planning, solid task descriptions, and a solid self-help wiki. Better to empower and make introductions then be the one fetching resources. Imho sometimes it means assigning research or co-dev help to a senior dev. Or passing them to the PM, or other business resource (PO, BA, Design).

@stephens3909 5 ай бұрын

If you recall from the presentation, a senior software developer is going to be concerned with technical aspects, deal with difficult problems in contained domains and not see the whole project (no 10,000ft view). That's their job. They may not necessarily be knowledgeable about the other projects within the team, which is true of my team, they're concerned about what they are working on. Likewise, may not be involved in stakeholder, management or client discussions. So if by "best" you mean displaying foresight, leadership tactics and understanding the business, a senior developer can be proactive in their bubble but it'll be impossible for them to be better at that than a good technical lead. If by "best" you mean development capability and understanding, it's not a requirement that a tech lead be a better software developer than the each of their team members, I'd even discourage trying to do that because that mindset is arrogant and full of pitfalls. A good tech lead will encourage and utilise the skills of all of their team members, understand what they tell you so you can make better decisions, but also never pigeon hole someone as the "X speciality dev". Calling a potential team we know nothing about "less capable devs" screams please don't hire me as a tech lead.