3 ms·
Please understand that I intend this as honest and helpful: you are completely, wildly deluding yourself. It is unlikely that someone with your background real
by Silhouette 16y ago
Please understand that I intend this as honest and helpful: you are completely, wildly deluding yourself.
It is unlikely that someone with your background really knows even one or two of the tools you mentioned "like the back of your hand" by professional standards. It is completely implausible that even the most gifted and enthusiastic geek on the planet knows all of them to that standard at your stage in your career.
The world is, however, full of people (usually students with little or no professional experience) who think they have these skills. It just comes across to experienced professionals as arrogant, ill-informed, lacking in perspective... amateurish and risky, basically. Would you hire (or even interview) someone you thought was like that?
My advice to you is this: decide which skills you want to highlight at the start of your career, and if you really have no demonstrable experience with those skills, make something. Build a simple game in C++. Write a simple but well presented CRUD application to show your web skills. Write an interactive symbolic calculator in Haskell. Make sure the code is clean and you have some respectable documentation to go with it. You presumably have several years to go at uni, so you have plenty of time to develop your skills. Just keep the example programs you develop along the way.
Actual demos of real projects that you have personally completed are just about the best advert there is for your programming skills. Even if those projects are just small demos, they still beat beautiful but empty CVs any day for getting noticed and attracting the right kind of attention from prospective employers.
- petercooper 16y agoMy advice to you is this: decide which skills you want to highlight at the start of your career I think this part of Silhouette's advice is more critical than its brevity suggests. I can only say this in hindsight but it's critical for you to only highlight a few of your skills (or even just one, in some cases) even if you have many. Saying you can do HTML, CSS, Photoshop, assembler, Ruby, and 101 other things is not going to floor the sort of people you need to impressive. I didn't know or understand this at 20. At nearly 30, I know enough people and have had enough experience to know that even if you're not a specialist, appearing to be one and then pulling out your jack-of-all-trades card is the most powerful way in to some great situations.
- derefr 16y agoYou're right, of course. I would never list any of these skills on my resume, or tell any interviewer that I could do them. I would never try to get a freelance contract that requires these skills. They're completely self-taught, completely untested, and I have zero confidence that I really "know" any of them. When I said I have no proof—I meant I have no proof for myself, either, as an empiricist. Really, what it amounts to is that when I come home, I spend twelve hours (that is, 4PM-4AM) "studying": reading programming books, testing out bits of code, writing scripts and hanging out in places like /r/coding and LtU. It's basically my sole hobby, and I started when I was 11 (with a website run on a scrounged Pentium Pro off a Slackware LAMP stack.) I'v continued teaching myself various skills since then, never producing useful output, just reading and testing myself. I don't have confidence that my skills are anything more than a bunch of academic knowledge. If I recall, these are the most code I've ever actually written: * Stargazer, an interactive galaxy creation program in SDL/Ruby (you plot and name stars, create flight/jump/trade paths, and classify arbitrary three-dimensional regions with arbitrary metadata; it's for sci-fi writers.) * Persona, a webapp where you create a user, that user creates several fictional characters (personas), and then, as a specific character, you answer questions out of a user-generated pool in order to flesh out your individual character. It's sort of like OKCupid in reverse—you specify the "factors" your graph of characters should display in advance (love, hate, admiration, apathy, etc.) and then the service helps you answer questions in a way that will conform to those pre-ordained relationships. * Nameclasser, a Bayesian classifier trained on the details of individual words (sound, length, derivation, etc.) You feed it a dictionary; it spits back a subset of it usable as "interesting" character names. * Folio, a mark-up language (and reference parser) similar to markdown, but intended for fiction (distinguishes pages, has footnotes, does neat things when it recognizes sections of screenplay-like dialogue, etc.) * Christmas, a graph adventure (it's a text adventure, but with the interface being clickable words in bubbles—basically an ever-expanding tree of circle-menus.) It's two-player, networked: the client(s) are in C with Lua extensions, server in Clojure. It also features something I've never seen before: network-transparent undo. (Only works under certain world-model-specific conditions, of course.) * SMS Importer, a little tool to sanitize a copy of your SMS database, copied from your iPhone's backup folder (SMS data has always been stored in 3d0d7e5fb2ce288813306e4d4636395e047a3d28.mddata, if you're curious), and present it as a folder of formatted-text chat logs. (It also keeps its own gateway database, just merging in previously-unseen texts, so you can delete an SMS record on your iPhone—it makes it a might bit faster—and still keep the record after re-importing.) * An unnamed, unfinished project involving editing timelines of narratives and meta-narratives in time-travel stories. * Nodepad, a hierarchical outliner (where every "node" was a folder+rtf file underneath, so you could make any node the working root), and Sponge, a visual to-do list (all the tags were importable 16x16 icons), both in C#. * Wikirei, a wiki designed from the top-down to look as clean, presentable, and non-wiki-ish as possible when you don't have editing rights, and elegantly expose editing features when you do. And each and every one of those is crap, in my opinion, and I would never release any of them. ...Having said that, and looking at that list, my problem might more be anxiety at releasing my work, than actually producing it. I've been working in a silo for so long, with no feedback as to whether my code has any quality (except what books say) that I have no idea what others will say when they see mine.