++ for documentation. I'd say start with that first and think about how a brand new user will use your software. How do I install? What are the dependencies? Etc.
Good documentation can easily trump bad code and architecture.
With no experience at all, I'd like to add a marketing lesson: if you write a blog post concerning your project, make sure it features an easy link to that project.
4 comments
[ 0.20 ms ] story [ 61.8 ms ] threadGood documentation can easily trump bad code and architecture.
That means my ten year supported version of Red Hat or Windows.