How to recover from a missing portfolio element?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
2
down vote

favorite












The situation:



I worked freelance from high school as a "web designer" (I'd label myself a front end developer now) for a bad client. Not good, not a client from hell, but overall, it was a bad time. I spent 9 years embedded in this site only to have a situation arise where I needed to move away from the place I lived to the place I live now and pretty much lost all proof that I did work on this website. Add insult to injury, the site is now GONE except for traces of it existing on the Wayback Machine.



I'm trying to find work now and I've created a small portfolio site to recover and rebuild, but the question is what do I do about this experience with the client? Do I use it? Do I drop it? Am I lugging around 9 years of dead weight or can I salvage the situation somehow?



Edit: I forgot to mention that when I lost all proof, I meant the package briefs regarding the work. I have some emailed briefs, but they might not be enough.







share|improve this question
















  • 1




    Surely you can talk at length about that project to demonstrate your competency and prove that it was a legitimate project? What kind of proof do you need? Do you have no screenshots at all that show your work, even from an archive?
    – Lilienthal♦
    Feb 24 '16 at 0:05










  • The screenshot would more than likely consist of the opening splash pages from the archive. The rest is broken links from the archive - they were running the e107 content management system for the whole while before the site went under, and the archive didn't even manage to capture a snapshot of the CMS index page.
    – C. Charette
    Feb 24 '16 at 0:40
















up vote
2
down vote

favorite












The situation:



I worked freelance from high school as a "web designer" (I'd label myself a front end developer now) for a bad client. Not good, not a client from hell, but overall, it was a bad time. I spent 9 years embedded in this site only to have a situation arise where I needed to move away from the place I lived to the place I live now and pretty much lost all proof that I did work on this website. Add insult to injury, the site is now GONE except for traces of it existing on the Wayback Machine.



I'm trying to find work now and I've created a small portfolio site to recover and rebuild, but the question is what do I do about this experience with the client? Do I use it? Do I drop it? Am I lugging around 9 years of dead weight or can I salvage the situation somehow?



Edit: I forgot to mention that when I lost all proof, I meant the package briefs regarding the work. I have some emailed briefs, but they might not be enough.







share|improve this question
















  • 1




    Surely you can talk at length about that project to demonstrate your competency and prove that it was a legitimate project? What kind of proof do you need? Do you have no screenshots at all that show your work, even from an archive?
    – Lilienthal♦
    Feb 24 '16 at 0:05










  • The screenshot would more than likely consist of the opening splash pages from the archive. The rest is broken links from the archive - they were running the e107 content management system for the whole while before the site went under, and the archive didn't even manage to capture a snapshot of the CMS index page.
    – C. Charette
    Feb 24 '16 at 0:40












up vote
2
down vote

favorite









up vote
2
down vote

favorite











The situation:



I worked freelance from high school as a "web designer" (I'd label myself a front end developer now) for a bad client. Not good, not a client from hell, but overall, it was a bad time. I spent 9 years embedded in this site only to have a situation arise where I needed to move away from the place I lived to the place I live now and pretty much lost all proof that I did work on this website. Add insult to injury, the site is now GONE except for traces of it existing on the Wayback Machine.



I'm trying to find work now and I've created a small portfolio site to recover and rebuild, but the question is what do I do about this experience with the client? Do I use it? Do I drop it? Am I lugging around 9 years of dead weight or can I salvage the situation somehow?



Edit: I forgot to mention that when I lost all proof, I meant the package briefs regarding the work. I have some emailed briefs, but they might not be enough.







share|improve this question












The situation:



I worked freelance from high school as a "web designer" (I'd label myself a front end developer now) for a bad client. Not good, not a client from hell, but overall, it was a bad time. I spent 9 years embedded in this site only to have a situation arise where I needed to move away from the place I lived to the place I live now and pretty much lost all proof that I did work on this website. Add insult to injury, the site is now GONE except for traces of it existing on the Wayback Machine.



I'm trying to find work now and I've created a small portfolio site to recover and rebuild, but the question is what do I do about this experience with the client? Do I use it? Do I drop it? Am I lugging around 9 years of dead weight or can I salvage the situation somehow?



Edit: I forgot to mention that when I lost all proof, I meant the package briefs regarding the work. I have some emailed briefs, but they might not be enough.









share|improve this question











share|improve this question




share|improve this question










asked Feb 23 '16 at 23:44









C. Charette

133




133







  • 1




    Surely you can talk at length about that project to demonstrate your competency and prove that it was a legitimate project? What kind of proof do you need? Do you have no screenshots at all that show your work, even from an archive?
    – Lilienthal♦
    Feb 24 '16 at 0:05










  • The screenshot would more than likely consist of the opening splash pages from the archive. The rest is broken links from the archive - they were running the e107 content management system for the whole while before the site went under, and the archive didn't even manage to capture a snapshot of the CMS index page.
    – C. Charette
    Feb 24 '16 at 0:40












  • 1




    Surely you can talk at length about that project to demonstrate your competency and prove that it was a legitimate project? What kind of proof do you need? Do you have no screenshots at all that show your work, even from an archive?
    – Lilienthal♦
    Feb 24 '16 at 0:05










  • The screenshot would more than likely consist of the opening splash pages from the archive. The rest is broken links from the archive - they were running the e107 content management system for the whole while before the site went under, and the archive didn't even manage to capture a snapshot of the CMS index page.
    – C. Charette
    Feb 24 '16 at 0:40







1




1




Surely you can talk at length about that project to demonstrate your competency and prove that it was a legitimate project? What kind of proof do you need? Do you have no screenshots at all that show your work, even from an archive?
– Lilienthal♦
Feb 24 '16 at 0:05




Surely you can talk at length about that project to demonstrate your competency and prove that it was a legitimate project? What kind of proof do you need? Do you have no screenshots at all that show your work, even from an archive?
– Lilienthal♦
Feb 24 '16 at 0:05












The screenshot would more than likely consist of the opening splash pages from the archive. The rest is broken links from the archive - they were running the e107 content management system for the whole while before the site went under, and the archive didn't even manage to capture a snapshot of the CMS index page.
– C. Charette
Feb 24 '16 at 0:40




The screenshot would more than likely consist of the opening splash pages from the archive. The rest is broken links from the archive - they were running the e107 content management system for the whole while before the site went under, and the archive didn't even manage to capture a snapshot of the CMS index page.
– C. Charette
Feb 24 '16 at 0:40










1 Answer
1






active

oldest

votes

















up vote
8
down vote



accepted










Don't leave a 9 year gap in your resume for any reason. Do you want people to assume you were unemployable? In prison? In a coma?



As a front-end developer, the portfolio is only part of your resume. You'll also be expected to show proficiency with front-end tools, best practices, and workflows. For the portfolio, there's no reason to emphasize that the relationship went sour. All that matters is that the work is no longer available to you. It's fairly common for businesses to go under, so a missing website doesn't raise any red flags. If you can talk to the talk about functionality, and show your design skills in another way, you don't need to worry. If the issue is raised in an interview, volunteer the archive links to show what has been salvaged--and then steer the conversation back to your front-end skills.






share|improve this answer


















  • 1




    +1 for a very detailed and professional answer that fully addresses the OP's concerns.
    – Richard U
    Feb 24 '16 at 15:36










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "423"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f62534%2fhow-to-recover-from-a-missing-portfolio-element%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
8
down vote



accepted










Don't leave a 9 year gap in your resume for any reason. Do you want people to assume you were unemployable? In prison? In a coma?



As a front-end developer, the portfolio is only part of your resume. You'll also be expected to show proficiency with front-end tools, best practices, and workflows. For the portfolio, there's no reason to emphasize that the relationship went sour. All that matters is that the work is no longer available to you. It's fairly common for businesses to go under, so a missing website doesn't raise any red flags. If you can talk to the talk about functionality, and show your design skills in another way, you don't need to worry. If the issue is raised in an interview, volunteer the archive links to show what has been salvaged--and then steer the conversation back to your front-end skills.






share|improve this answer


















  • 1




    +1 for a very detailed and professional answer that fully addresses the OP's concerns.
    – Richard U
    Feb 24 '16 at 15:36














up vote
8
down vote



accepted










Don't leave a 9 year gap in your resume for any reason. Do you want people to assume you were unemployable? In prison? In a coma?



As a front-end developer, the portfolio is only part of your resume. You'll also be expected to show proficiency with front-end tools, best practices, and workflows. For the portfolio, there's no reason to emphasize that the relationship went sour. All that matters is that the work is no longer available to you. It's fairly common for businesses to go under, so a missing website doesn't raise any red flags. If you can talk to the talk about functionality, and show your design skills in another way, you don't need to worry. If the issue is raised in an interview, volunteer the archive links to show what has been salvaged--and then steer the conversation back to your front-end skills.






share|improve this answer


















  • 1




    +1 for a very detailed and professional answer that fully addresses the OP's concerns.
    – Richard U
    Feb 24 '16 at 15:36












up vote
8
down vote



accepted







up vote
8
down vote



accepted






Don't leave a 9 year gap in your resume for any reason. Do you want people to assume you were unemployable? In prison? In a coma?



As a front-end developer, the portfolio is only part of your resume. You'll also be expected to show proficiency with front-end tools, best practices, and workflows. For the portfolio, there's no reason to emphasize that the relationship went sour. All that matters is that the work is no longer available to you. It's fairly common for businesses to go under, so a missing website doesn't raise any red flags. If you can talk to the talk about functionality, and show your design skills in another way, you don't need to worry. If the issue is raised in an interview, volunteer the archive links to show what has been salvaged--and then steer the conversation back to your front-end skills.






share|improve this answer














Don't leave a 9 year gap in your resume for any reason. Do you want people to assume you were unemployable? In prison? In a coma?



As a front-end developer, the portfolio is only part of your resume. You'll also be expected to show proficiency with front-end tools, best practices, and workflows. For the portfolio, there's no reason to emphasize that the relationship went sour. All that matters is that the work is no longer available to you. It's fairly common for businesses to go under, so a missing website doesn't raise any red flags. If you can talk to the talk about functionality, and show your design skills in another way, you don't need to worry. If the issue is raised in an interview, volunteer the archive links to show what has been salvaged--and then steer the conversation back to your front-end skills.







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 24 '16 at 12:23









Lilienthal♦

53.9k36183218




53.9k36183218










answered Feb 24 '16 at 1:13









jimm101

11.6k72753




11.6k72753







  • 1




    +1 for a very detailed and professional answer that fully addresses the OP's concerns.
    – Richard U
    Feb 24 '16 at 15:36












  • 1




    +1 for a very detailed and professional answer that fully addresses the OP's concerns.
    – Richard U
    Feb 24 '16 at 15:36







1




1




+1 for a very detailed and professional answer that fully addresses the OP's concerns.
– Richard U
Feb 24 '16 at 15:36




+1 for a very detailed and professional answer that fully addresses the OP's concerns.
– Richard U
Feb 24 '16 at 15:36












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f62534%2fhow-to-recover-from-a-missing-portfolio-element%23new-answer', 'question_page');

);

Post as a guest













































































Comments

Popular posts from this blog

Long meetings (6-7 hours a day): Being “babysat” by supervisor

What does second last employer means? [closed]

One-line joke