Hello HN, i'm a informatics engineering student from Portugal.
Lately i found that i almost always over rely on demos or examples to start something quick or solve some problem.
Checking examples is obviously quicker, but that won't do every time.<p>Last project i did, used apache jena (a java semantic web framework), they provide many examples on their website (i gotta say it needs improvement), if they didn't i'm afraid it would have taken me way too much time to get stuff working.
It has way more classes and patterns that my beginner brain can handle at once. I found generally that is really hard to find the starting points just by looking at javadoc's.
So, how do you manage when something you want to use is complex and there is no examples( or documentation), is this just an endurance problem to figure out how everything works? do you have any special approach?
Thanks
Depending on the situation, you may be able to jump into the source code and check how they do things, but personally, I don't.<p>If the developer/community of a language, framework, library, etc. etc. haven't taken the time to write good documentation and provide some examples, I tend to stay away from it. It takes extra time for us to understand how something was built, and why. The developer should help us along with this.<p>Think about even the simplest API if it isn't documented, how long will it take you to figure out what you can do with it and how.<p>For me, it is also likely that the original developer is a much better programmer than I am. Or at least, I assume they are. I suspect there will be much of their source that I don't understand. Of course, reading their code makes me a better developer, but I'll often need help, and good documentation will help along with that.<p>It sounds horrible to say "I expect that if you're going to create an open-source bit of code that will help me code better/easier/faster, I also expect you to document it well and give examples", but if somebody is going through the trouble of developing something they want other people to use, I think this is an important part of that process.<p>What do people think of documenting first, and building from that documentation? I'm putting together my first open-source project, and am thinking that may be a good way to manage the documentation thing. Anybody done that before?