Re:Why People Initially Suck at Programming
by AndyKelley on Sunday August 22, 2010 @08:12PM
(#1625542)
Of course we'd all love to have 100% correct, documented libraries, specs which are unambiguous, properly designed code that will stay at version [4.x] and with same API forever...
Qt 4.
Re:Why People Initially Suck at Programming
by TalkBinary on Monday August 23, 2010 @11:55AM
(#1627101)
I have to agree. When I started writing code for a research group I was frustrated because the library didn't have any documentation and the coding was difficult to understand.
When I started writing code, I became frustrated and couldn't write code because half the time I couldn't deal with it. I talked with the professor and after a long conversation, he simply told me to deal with it. So I did.
A month later, I had learned so much from the library by just reading snippets of code and testing it. Before I knew it, I was writing code non-stop.
I haven't seen that attitude before, but recently an idealist graduate joined my team. I can't remember now how many times lately I had to tell "Yes, it has bugs, but writing a new implementation would take a year, so we're just going to patch the library."; "No, it doesn't have a documentation - check if it behaves correctly."; "No, it really doesn't need to be a fully speced system on its own JVM, it doesn't need more than a shell script."; "Yes, requirements change, get used to that."...
Of course we'd all love to have 100% correct, documented libraries, specs which are unambiguous, properly designed code that will stay at version 1.0.0 and with same API forever... Well - it just doesn't work like that, even if it's a good thing to aim for. I can swear every day at some RFCs and the bunch of monkeys who wrote them, but that doesn't mean it's going away. It's already out there - if you have time, build something better. If you don't... take a break, breathe, come back and make it work.