It's an interesting idea, but I prefer to take my experience and tell a story that specifically targets the role for which I am applying. From that perspective, having a single "story" out there for all potential employers isn't optimal for me.
They should let you tag items on the timeline for different roles, so that you can quickly filter it for employers and send out.
The Stack Overflow Developer Story: A New Technical Resume
111–120 of 147 posts
Re: The Stack Overflow Developer Story: A New Technical Resume
#112Re: The Stack Overflow Developer Story: A New Technical Resume
#113I'm trying to get hired as a junior front end developer. Suck at writing resumes. This is my worst one so far. Also I've been applying but no responses, I have a defeatist mentality and also I think I do accept that I don't meet the requirements. http://m.imgur.com/a/oCdvU I have changed the format some as the bullets as titles doesn't make sense. Still I have to condense and overall my "achievements" are pretty basi…
Re: The Stack Overflow Developer Story: A New Technical Resume
#114I'm trying to get hired as a junior front end developer. Suck at writing resumes. This is my worst one so far. Also I've been applying but no responses, I have a defeatist mentality and also I think I do accept that I don't meet the requirements. http://m.imgur.com/a/oCdvU I have changed the format some as the bullets as titles doesn't make sense. Still I have to condense and overall my "achievements" are pretty basi…
Don't take this the wrong way, but you need to change the way you project yourself. Even just from this resume, you're talking yourself down. Who would you hire?
"I wanted to keep track of who/what was visiting my websites. Turns out they were mostly crawlers for search engines. I keep track of IPs and URLs requested, I store them in a MySQL database using PHP"
or
"Wrote an application to process and analyse logfiles across a collection of websites, using a common web application stack. Stores requested IPs and URLs for future analysis. Identified the split of automated search engine crawlers and other bots vs human visitors. Tools and languages used include PHP and MySQL"
Resumes are all about how you present what you've done.
On that point - if you're applying for frontend developer positions, use your skills! Build a cool website to present your resume rather than a plain piece of paper. You'll probably still need the paper, but the first line of it can be "View my resume online at example.com".
Re: The Stack Overflow Developer Story: A New Technical Resume
#115Re: The Stack Overflow Developer Story: A New Technical Resume
#116Surprisingly, not many people know just how to write a good developer resume. The Developer Story is a good approach but even that is missing the key element that makes a resume work _when you are looking for a job_. Imagine this scenario: - Farmer looking for horse to plough my fields and inspect my farm - Horse 1: "I am a stallion! My coat shines in the sun, my mane is dark and glossy, and the very earth trembles a…
Would you say this level of openness has an impact (positive or negative) on sales of your book? It's pretty refreshing but the cynic in me wonders if it hurts sales.
Re: The Stack Overflow Developer Story: A New Technical Resume
#117Earlier quoted context omitted.
I don't like this notion of having a "good" GitHub profile. GitHub started off as an easy place for me to dump code, no matter how crappy. Dumb ideas, samples from learning, incomplete experiments, whatevs. Then I noticed that I had started censoring my code krapola. I was sepf conscious about the code I was making visible, as I didn't want to be judged. Then I decided that lame. Now I shamelessly put garbage on GitH…
I'm the same way. I removed a lot of old stuff from my early days because I was afraid I was going to be judged on it. Now I don't care. GitHub is my dumping ground for everything. I start a new project almost every time I want to learn a specific thing so I have lots of incomplete projects on there simply because I move on once I learned the goal task. Unfortunately like most people all the clean and polished code l…
Re: The Stack Overflow Developer Story: A New Technical Resume
#118Earlier quoted context omitted.
Not for a useful interview. If you tell me you founded and sold a machine learning company but can't explain the pros and cons of using variance versus standard deviation then you didn't sell a machine learning company.
One (stddev) is in the same units as the quantity being measured, while the other isn't. I know nothing about machine learning and suck at math and statistics. Did I pass?
Re: The Stack Overflow Developer Story: A New Technical Resume
#119Earlier quoted context omitted.
One (stddev) is in the same units as the quantity being measured, while the other isn't. I know nothing about machine learning and suck at math and statistics. Did I pass?
if I was recruiter, math knowledge would make the difference, it helps even unconsciously for problem solving, logic reasoning, algorithms
What makes you think this? Anything aside from intuition?
Re: The Stack Overflow Developer Story: A New Technical Resume
#120Earlier quoted context omitted.
This is why the resume endures despite it's many flaws (talked about this in some other comments). There needs to be a summarized, editorialized version of your "history" and that's what the resume does in a (semi) standardized format. The big thing for me is that this summarized/editorialized version shouldn't be what you (the one with the career) manage on a regular basis. You should have a source of truth that is…
It's all marketing really. Many of the devs who struggle the most have some difficulty giving themselves credit for things they've done - they're modest perhaps. I think when I write some of these resumes they are more accepting of them because it's me bragging about their accomplishments. Unfortunately in the resume writing game, there are lots of failed writers that were never involved in hiring. They are good writ…
I think being modest is a good trait overall just not so good for writing your own CVs.