Simply saying you are working on opensource programming will show that you code as a hobby.
I can't agree with this statement. There are simply too many people out there who say "I'm working on building my own OS kernel written in Perl" or something like that. Just look on SourceForge for projects that were started years ago but have yet to release any files and likely never will (I'm guilty of creating a few of them) (yes, I know they're starting to clean out stale projects).
If you want to put an Open Source project on your resume, be sure that you have released some actual code for it. It doesn't have to be big. It could be full of bugs and only have minimal functionality. As long as it runs through the compiler/interpreter without errors and has some basic functions, you'll be ahead of 90% of the "Open Source Programmers" out there that have nothing to show.
When I got my current job, I was working on a server implementation (in Perl) of the Hypertext Coffee Pot Control Protocol (RFC 2324) (there are a few clients for it out there, but I couldn't find any servers). When I was asked for code examples, I had already gotten the server up to the point of a basic HTTP/1.1 server, but the HTCPCP methods weren't implemented yet. That didn't matter, since I knew what I had worked, so I submitted it. I have now been working for that company for a year and a half, though the HTCPCP server still sits at the point it did back then . . .
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
In reply to Re: Re: Proving I have mad perl skillzzzlz
by hardburn
in thread Proving I have mad perl skillzzzlz
by BUU
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |