Career Advice About GitHub

This is somewhat of a random question and I assume it can only help but do Github stars mean anything to big tech (1k+ stars) and is "gaming" it a good use of time? (By gaming I mean honest accumulation of stars where the project is popular but not technically challenging)

Growing into a staff engineer requires the team to trust our skills and accept our leadership. It takes time to establish this.

Does actively creating blog posts, LinkedIn posts, and keeping GitHub activity green by doing side projects accelerate career growth and get the promotion faster? Or should I just focus on doing my work at my company?

What are some opportunities that you've got due to being an engineering influencer?

Do you use some kind of "code reading" techniques? I've always felt the more senior you become, the more time you spend reading others' work, especially across multiple projects. Curious to know if there any recommendations on where to start, gathering context while staying productive.

Hi guys I wanted to ask your opinion on open source on GitHub and how valuable having a solid portfolio of contributions there can be.

Hi everyone,

I'm in the early stages of interviewing for an infrastructure role ("Senior Cloud Infrastructure Development Engineer") at Nvidia. From my initial conversations and research, it seems like the team supports other Nvidia engineers for testing and development. I'll learn more in upcoming interviews, but I'm curious to hear from the Taro community about a couple of things:

• Will this role primarily involve only Devops work & tooling, or will it be focused on developing services and tools?
• Given my background in backend and distributed systems, would a non-revenue-generating role like this offer good growth opportunities at Nvidia?

Any insights you can share about similar roles at Nvidia would be greatly appreciated!

Thanks in advance!

There are a lot of different side projects, from open source tools to end user apps.

For this question, I would like to know your experience creating and promoting open source projects.

What I think makes sense is:

• You should solve a pain point or problem.
• For nature, mostly of the target users are software engineers.
• You should make it easy to use.
• There should be a decent documentation.

In my case, I created , it's a Next.js boilerplate that helps the developers to start a SaaS web application faster.

I would like to help more developers to get their side projects faster, tho I advise to build your own solution from scratch IF you want to experiment the learning experience completely.

What do you think?

(I'm open to feedback for my open source project, too).