hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9K
active users

#TechLead

4 posts4 participants0 posts today
Continued thread

While I wish I could start coding sooner, I can't change the fact that improving our efficiency by f.ex. 20% as a team through all the things I've mentioned in this thread, is just quantifiably more than I could contribute as an individual through writing code alone.

Despite the feedback and progress so far, it still feels weird not writing code yet...

It'll be fine, and I know I'll get to it soon enough, I'm just looking forwards to contributing to a few parts of the codebase 👩‍💻 :ms_two_hearts:

Continued thread

By collaborating closely with, and with thanks to the product owner, I've been able to apply structure and standards, that I hope will allow us to start measuring velocity and start estimating capacity for the future. If successful, it should be a win-win, as we'll be able to give better estimates to our clients, and avoid crunch for the team.

Cost of this has been spending my evenings the first 2 weeks making agile visualisations, docs and (re)writing, linking and organising work items (tickets/issues) to the point where I'm now the author of 2/3 of our total count :neocat_laugh_sweat:

I'm amazed at how receptive and supportive everyone has been so far, which hopefully is a sign that I'm doing the right things. Low-key also feels like, they're just happy to have a tech lead again after being without one for a while.

Hope this will continue, never had a job I felt this welcome in, and happy doing before 🤞 💼

It's been interesting to see how I've had to change my approach as a tech-lead, but as I now have different responsibilities than that of a senior developer it sorta makes sense?

As expected, it's already changed several times as I've had to re-evaluate it throughout my interview and onboarding process, but as of right it's three main points, in order:

  1. Documentation: as in, create the structure and process for it to be created, maintained and kept up-to-date with examples.
  2. DevOps: as in, step into the unfilled role and create a structured release process and build up a CI/CD pipeline for automated deployments.
  3. Testing: as in, introduce new tooling to allow test-generation supplement existing ones to increase coverage.

Though doing this as I've been getting to know the team, going to conferences and meeting clients and integration partners has been a lot :neocat_woozy:

Today's reading is dedicated completely to the Tech Lead role.

👉🏼 What are the responsibilities of a Tech Lead?

👉🏼 How to ensure you deliver the right value?

👉🏼 Seek opportunities, all the time

👉🏼 How do you deal with and reduce the technical debt?

👉🏼 How do you know you are performing well as Tech Lead?

All that os covered here 👇🏼

newsletter.optimistengineer.co

Тимлид или ведущий дейликов?

«У меня не тимлид, а просто ведущий дейликов!» — с горечью однажды воскликнул мой знакомый, и эта фраза послужила для меня поводом к написанию этой статьи. Ведь я тоже уже давно замечаю, что с ролью тимлида в последние годы происходит что-то не то. Причем как со стороны самих лидов, так и со стороны их руководителей

habr.com/ru/articles/877580/

#teamlead #techlead #management #cto #cpo #11 #raciматрица #performance #управление_людьми #управление_командой

ХабрТимлид или ведущий дейликов?«У меня не тимлид, а просто ведущий дейликов!» — с горечью однажды воскликнул мой знакомый, и эта фраза послужила для меня поводом к написанию этой статьи. Ведь я тоже уже давно замечаю, что с ролью...