I think when you're hoping to get hired for a professional role, it's worth taking 30s to proof-read your post.
Respectfully, if I received a cover letter with the same sort of prose and grammar I wouldn't be considering the candidate. How you communicate online says a lot about how you might behave in the workplace.
Yes, I understood what you wanted to say. In this case, I am very sure that I did not proofread my other posts as this post was purely random. Thanks for bringing this to my notice.
On the project: It is a development tool that helps new employees while they undergo onboarding. Every time when a new employee comes into a job, large repositories are difficult to understand and hence, they tend to ask a senior for help. But, the problem is solved in this case as it gives a complete insight about the codebase to the user.
All you need to do is simply write "n3mo impact "function name" and it would give you an idea of how the change made to that function will affect the whole system.
Understand the frustration, but a defeatist attitude won't attract the attention you want.
In terms of traction, though, posting anything top-level due to the reasons you mention (everyone having their own AI tool) doesn't work anymore and, a lot of the time, just gets ignored, removed, or downvoted aggressively on things like Reddit.
What worked for me was signing up for or joining communities of the person I wanted to help and then waiting for them to bring up the problem my tool solved and immediately helping them out and then assuming my tool solved a meaningful part of thier problem, dropping a link to the tool, or DMing them afterward.
Much more effective because you're reaching someone in active frustration, so they are likely to immediately try the tool out, which is fantastic for early feedback on whether what you're solving is important.
I open-sourced what I use to find those threads, so other builders could also focus on helping instead of searching for pain (or worse, giving up)
I think when you're hoping to get hired for a professional role, it's worth taking 30s to proof-read your post.
Respectfully, if I received a cover letter with the same sort of prose and grammar I wouldn't be considering the candidate. How you communicate online says a lot about how you might behave in the workplace.
Your project seems interesting but it's pretty hard to understand what it does. https://github.com/RajX-dev/N3MO
What do your users think?
Yes, I understood what you wanted to say. In this case, I am very sure that I did not proofread my other posts as this post was purely random. Thanks for bringing this to my notice. On the project: It is a development tool that helps new employees while they undergo onboarding. Every time when a new employee comes into a job, large repositories are difficult to understand and hence, they tend to ask a senior for help. But, the problem is solved in this case as it gives a complete insight about the codebase to the user. All you need to do is simply write "n3mo impact "function name" and it would give you an idea of how the change made to that function will affect the whole system.
Understand the frustration, but a defeatist attitude won't attract the attention you want.
In terms of traction, though, posting anything top-level due to the reasons you mention (everyone having their own AI tool) doesn't work anymore and, a lot of the time, just gets ignored, removed, or downvoted aggressively on things like Reddit.
What worked for me was signing up for or joining communities of the person I wanted to help and then waiting for them to bring up the problem my tool solved and immediately helping them out and then assuming my tool solved a meaningful part of thier problem, dropping a link to the tool, or DMing them afterward.
Much more effective because you're reaching someone in active frustration, so they are likely to immediately try the tool out, which is fantastic for early feedback on whether what you're solving is important.
I open-sourced what I use to find those threads, so other builders could also focus on helping instead of searching for pain (or worse, giving up)
https://github.com/obris-dev/openmagpie