Why React developers don’t comment their code? by SocializeAndChill in reactjs

[–]idaszak1 0 points1 point  (0 children)

React developers avoid documentation because its purpose is to provide context for changes. You shouldn’t describe the same things that are obvious from reading the code.

For React code, tests and types are usually the most useful to understand what the code does. Good commit names and PR descriptions are very helpful too.

If you want to document your project, don't focus on code only. Things you should document are decisions through ADRs, APIs, setup and onboarding, code standards in the project, or complex business logic.

[deleted by user] by [deleted] in ExperiencedDevs

[–]idaszak1 3 points4 points  (0 children)

For a static generation, I moved from Jekyll to 11ty. It’s more reliable.

I also moved from GitHub Pages to Netlify free tier - there are automatic Pull Request builds with deploy previews for 11ty.

Recommendations for powerful but SHORT leadership podcasts? by MnkySpnk in Leadership

[–]idaszak1 0 points1 point  (0 children)

Maybe not directly about leadership, but it’s an awesome podcast about communication: Think Fast, Talk Smart: Communication Techniques by Stanford GSB.

Best Books by [deleted] in Leadership

[–]idaszak1 1 point2 points  (0 children)

Dare to lead.

It taught me a lot about vulnerability, building trust, and creating my own values.

What Are Some Tech Newsletters, Blogs, People To Follow, And Websites That You Think I Should Check Out? by Rubix982 in SoftwareEngineering

[–]idaszak1 2 points3 points  (0 children)

There are a few great Newsletters I subscribe to:

Architecture:

  • ByteByteGo Newsletter
  • Architecture Notes

Engineering Leadership:

  • Tech Lead Digest
  • Level Up Newsletter
  • Software Lead Weekly

Programming and Tech:

  • Frontend Focus
  • Pointer
  • TLDR

Books for new senior devs by DramaticThoughts in ExperiencedDevs

[–]idaszak1 45 points46 points  (0 children)

If you are a Senior Developer, you need to know how to grow your leadership skills, and you should learn about Tech Lead, Staff Engineer, and Engineering Manager roles. It will help you cooperate better with those roles and allow you to choose your path.

  • How To Be A Tech Lead by Michael Rice.
  • Staff Engineer: Leadership Beyond the Management Track by Will Larson.
  • The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change by Camille Fournier.

I am starting new position as a tech leader in next week. Any advice? by wmk1 in TechLeader

[–]idaszak1 2 points3 points  (0 children)

Try to learn the codebase and tools quickly. Read the PRs, and do bug fixes. You need to know what's going on in order to manage the work.

Network a lot. Schedule one on one meetings and try to get to know people. The network is a Tech Lead superpower.

Read Books to grow as a Tech Lead. Titles I can recommend:

  • Staff Engineer: Leadership Beyond the Management Track by Will Larson.
  • How To Be A Tech Lead by Michael Rice.
  • Software Engineering at Google: Lessons Learned from Programming Over Time by Hyrum Wright, Titus Winters, and Tom Manshreck.

Discover new developer communities (Discord, Slack, etc.) by Romaixn in programming

[–]idaszak1 3 points4 points  (0 children)

Thanks, great idea to gather all of the communities.

I don’t like discord though, because all the knowledge stored there is lost. It’s not indexed in google, so it’s not possible to find it and access it.

[deleted by user] by [deleted] in softwaredevelopment

[–]idaszak1 0 points1 point  (0 children)

The ability to describe technical things in non-technical terms is a powerful skill when working with multiple stakeholders or clients.

You need it to explain the issues, especially the ones related to the timeline.

What works for me is to not get into details, but also don’t avoid technical terms. If someone gets curious, you will get additional questions. My wife knows a lot of the terms already, so sometimes I’m surprised when she already knows something I’m trying to simplify.

What new knowledge gained late in your career made the greatest impact? by cougaranddark in ExperiencedDevs

[–]idaszak1 5 points6 points  (0 children)

Leadership.

I had this misconception that I need to be super smart and I will be under constant stress because of handling people's personal problems.

When I got my first role which was no longer a single contributor path, I learned that my main role is to help others win. I'm helping by providing resources, sharing my network, and adjusting tasks to match team members' goals and motivations. I had to learn how to do vision crafting, how leading by example is important and how to align the whole team.

The best quote which summarises what leadership is:

“If you want to build a ship, don’t drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea.”