Hey everyone,
I’m wondering how you guys handle your work and personal GitHub profiles. Do you keep them separate or use the same account for both?
I’ve been using my personal account for everything, but I’m starting to think maybe I should have a separate one for work stuff. What are the pros and cons of having two accounts?
Also, how do you decide what to put on your public profile? I want to show off my skills, but I’m not sure what’s okay to share from work projects.
Any advice or experiences would be super helpful. Thanks!
I’ve actually found a middle ground that works pretty well. Instead of two separate accounts, I use one GitHub account but leverage the ‘Organizations’ feature for work projects. This keeps things tidy while still presenting a unified profile.
For public sharing, I’m selective. I’ll describe the tech stack and problem-solving approach for work projects, but never share actual code without explicit permission. Personal projects are fair game though - they’re great for showcasing creativity and learning new skills.
One tip: use pinned repositories to highlight your best work, whether personal or professional. It gives visitors a quick overview of your capabilities.
Remember, your GitHub is like a living resume. Keep it updated, but always prioritize your current job’s confidentiality. It’s a balancing act, but with some thought, you can make it work to your advantage.
i keep one account for everything. it’s easier to manage and shows my full range of skills. just be careful wat u share from work projects. i usually just describe the tech i used and problems i solved without sharing actual code. make sure to check ur company’s policies tho. its important to showcase ur best stuff, whether its from work or personal projects.
I’ve actually been grappling with this same issue recently. After much deliberation, I opted to stick with a single GitHub account for both work and personal projects. Here’s why:
Simplicity is key. Managing one account means less hassle with SSH keys, logins, and context switching. It’s also easier for potential employers or collaborators to see my full body of work in one place.
To keep things organized, I use clear repository naming conventions and leverage GitHub’s ‘Organizations’ feature for work-related projects. This allows for a clean separation while maintaining a unified presence.
As for sharing work stuff publicly, I’ve found it’s best to err on the side of caution. I focus on describing the problems I’ve solved and technologies I’ve used, rather than sharing actual code. When in doubt, I always check with my employer first.
Remember, your GitHub profile is essentially your coding portfolio. Curate it wisely to showcase your best work and skills, regardless of whether it’s from personal or professional projects.
I’ve found that maintaining a single GitHub account for both personal and professional use has worked well for me. It streamlines management and presents a comprehensive view of my skills. To differentiate between work and personal projects, I use clear naming conventions and leverage GitHub’s organization feature for work-related repositories.
Regarding public sharing, I’m cautious with work projects. I focus on describing technologies used and problems solved without disclosing proprietary code. Always consult your employer’s policies on this matter. For personal projects, I’m more open, using them to demonstrate my coding style and ability to tackle diverse challenges.
Ultimately, your GitHub profile serves as a coding portfolio. Curate it carefully to showcase your best work, balancing professional accomplishments with personal passion projects. This approach has helped me maintain a strong online presence while respecting professional boundaries.
I’ve been in your shoes, and I ultimately decided to maintain separate accounts for work and personal projects. The main advantage is clear separation between professional and personal endeavors. It helps prevent accidental commits to the wrong repositories and keeps your work contributions distinct from personal experiments.
However, managing two accounts can be cumbersome, especially when switching between them. You’ll need to set up separate SSH keys and be vigilant about which account you’re using.
Regarding public profiles, I focus on showcasing personal projects and open-source contributions. For work-related skills, I describe technologies and methodologies used without sharing proprietary code. Always consult your employer’s policies on what’s permissible to share publicly.
Ultimately, the decision depends on your specific circumstances and comfort level with blending professional and personal coding activities.