Just a basic Jekyll template. I have had a 2 year break and recently got back into it. In that time I also forgot to renew my old .com domain and had it taken over.
Have had a few posts that previously got attention on Hacker News.
I think it highly depends what kind of company you are looking for, FAANG? Tech startup? Finance? Average company?
To more directly answer your question:
1. Like you said, a recruiter spending 5 seconds on your resume might not understand and move on. However in an interview your passion for this project will be an asset.
2. How self driven are you? Can you spend X hours on something you find boring?
I try to stick to one main project (https://issueembed.dev/) but do allow myself to indulge in one or two other ones when I need a break.
I also try to have my environment setup automated and some level of testing so that if I do switch between projects, I am not wasting time on regression or environment setup. This may be best practice but it is very easy to not bother with in a side project.
It used to be a free for all and I'd have a lot of different projects working on at different stages but I'd rarely finish anything or get it to a stage I was happy with. I now just track any other ideas I have in a Trello board and look at it occasionally to get inspiration.
Thanks for the feedback, I have been thinking of whether making email optional or allowing the admin to not show it. Your feedback is a noted data point, thank you!
Hey thank you very much. No login needed for submitting an issue. However follow up is handled differently:
Public repos: the reporter is given the link on successful submission, so to communicate further a GitHub account is required
Private repos: the reporter needs to supply an email (not shared with repo) which will be held by Issue Embed and handle communication from the issue to email (and visa-versa)
Hey HN creator of Issue Embed here, this is my lockdown project.
I wanted a tool to collect bugs on my websites but every other tool I could find would either want me to use their issue tracking platform or was too expensive. I just needed something simple for small websites, so I could receive issues straight into my GitHub Issues. I am able to use the issues in my current workflows. I scratched my own itch then a few friends asked to be able to use it too.
So here we are today, Issue Embed is on the GitHub Marketplace. I am launching a free plan. Any feedback is welcome.
I lived in Vanuatu for a couple of months working, I used to have kava once a week. I found it to be a lot better than alcohol at helping me wind down from work, got used to the taste after a little bit.
Thank you for the feedback, I am glad you interpreted what I wrote that way. I was trying to essentially take my conversation with my friend, take the advice I gave to him and add some self-reflection.
Author here, with regard to "taking it down/replacing it", I found a middle ground. I moved all those repositories to another organization (that I control), so my profile is clean and if I need/want to see that code I can go there.