Mixing
![Potential employer is uncontactable [duplicate]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
Give demo/snapshot site rather than actual site in web developer resume
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
3
down vote
favorite
Is this OK or less preferred?
Sometimes the site that I developed before was not longer live or had new design.
Is it good to still keep a snapshot of the site or give the demo site with my personal website domains in my resume?
resume developer
edited May 12 '14 at 19:41
gnat
3,22973066
asked May 12 '14 at 15:50
dgahel
182
add a comment |Â
up vote
3
down vote
favorite
Is this OK or less preferred?
Sometimes the site that I developed before was not longer live or had new design.
Is it good to still keep a snapshot of the site or give the demo site with my personal website domains in my resume?
resume developer
edited May 12 '14 at 19:41
gnat
3,22973066
asked May 12 '14 at 15:50
dgahel
182
@JoeStrazzere some freelance websites and actual job websites
– dgahel
May 12 '14 at 18:48
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
Is this OK or less preferred?
Sometimes the site that I developed before was not longer live or had new design.
Is it good to still keep a snapshot of the site or give the demo site with my personal website domains in my resume?
resume developer
edited May 12 '14 at 19:41
gnat
3,22973066
asked May 12 '14 at 15:50
dgahel
182
Is this OK or less preferred?
Sometimes the site that I developed before was not longer live or had new design.
Is it good to still keep a snapshot of the site or give the demo site with my personal website domains in my resume?
resume developer
edited May 12 '14 at 19:41
gnat
3,22973066
asked May 12 '14 at 15:50
dgahel
182
edited May 12 '14 at 19:41
gnat
3,22973066
edited May 12 '14 at 19:41
gnat
3,22973066
edited May 12 '14 at 19:41
gnat
3,22973066
3,22973066
asked May 12 '14 at 15:50
dgahel
182
asked May 12 '14 at 15:50
dgahel
182
asked May 12 '14 at 15:50
dgahel
182
182
@JoeStrazzere some freelance websites and actual job websites
– dgahel
May 12 '14 at 18:48
add a comment |Â
@JoeStrazzere some freelance websites and actual job websites
– dgahel
May 12 '14 at 18:48
@JoeStrazzere some freelance websites and actual job websites
– dgahel
May 12 '14 at 18:48
@JoeStrazzere some freelance websites and actual job websites
– dgahel
May 12 '14 at 18:48
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
Is it legal?
This is perhaps the most important question.
If you developed it for an employer, I believe it's actually fairly likely that they have full legal rights to it, thus you may not have a legal right to do anything at all with it.
You should probably check your contract or consult a lawyer to determine your exact legal rights.
The design versus other aspects
In website development, there may be other factors, like performance, that also plays a role. Having it be seen supporting a large user base efficiently can be a lot better than a sandbox view of it.
Proof of the accomplishment
Saying you developed this for some company (even with a link provided) isn't quite the same as pointing them to the company website which shows them running it.
Regarding redesign
If you just say you developed a website, with or without mentioning that it's been redesigned, isn't good - either you don't have anything to demonstrate, or you are passing off someone else' work off as your own.
Uptime
This can go for either the company website or your website.
With your website, you have a fair amount of control over scheduled downtime.
A company website is more likely to be the target of Denial of Service attacks or hacks.
With your website, you probably don't have the top of the line hosting, so it's more likely that there's some expected or unexpected downtime, and you may even find yourself without a host in the worst case.
The extreme example is a company website that is no longer live, which obviously favours your website.
answered May 12 '14 at 19:30
Dukeling
8,66632347
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
add a comment |Â
up vote
1
down vote
As a developer, using an actual site is risky for the following reasons:
- A poor user experience may make you look bad, even though the code is good
- Developer specific work like test assertions and build scripts are not visible
- Poor CDN configuration such as minified code without source maps may make code hard to demonstrate
- You may need to login using real credentials which can compromise your personal information
Using a demo site is also risky for different reasons:
- The code you demo may not make sense outside the context of the real site
- The techniques used in the code may be outdated based on the architecture of the real site
- The things you demo may violate some company policy, especially if the business logic depends on company specific mock data structures
Focusing on generic things like stackoverflow questions you've answered or specific things like articles you've written or algorithms you've implemented may be a better choice.
References
Clearing your Front End Job Interview  —  JavaScript
Algorithms With Javascript For Coding Interview
answered Mar 11 at 23:45
Paul Sweatte
20514
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Is it legal?
This is perhaps the most important question.
If you developed it for an employer, I believe it's actually fairly likely that they have full legal rights to it, thus you may not have a legal right to do anything at all with it.
You should probably check your contract or consult a lawyer to determine your exact legal rights.
The design versus other aspects
In website development, there may be other factors, like performance, that also plays a role. Having it be seen supporting a large user base efficiently can be a lot better than a sandbox view of it.
Proof of the accomplishment
Saying you developed this for some company (even with a link provided) isn't quite the same as pointing them to the company website which shows them running it.
Regarding redesign
If you just say you developed a website, with or without mentioning that it's been redesigned, isn't good - either you don't have anything to demonstrate, or you are passing off someone else' work off as your own.
Uptime
This can go for either the company website or your website.
With your website, you have a fair amount of control over scheduled downtime.
A company website is more likely to be the target of Denial of Service attacks or hacks.
With your website, you probably don't have the top of the line hosting, so it's more likely that there's some expected or unexpected downtime, and you may even find yourself without a host in the worst case.
The extreme example is a company website that is no longer live, which obviously favours your website.
answered May 12 '14 at 19:30
Dukeling
8,66632347
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
add a comment |Â
up vote
1
down vote
accepted
Is it legal?
This is perhaps the most important question.
If you developed it for an employer, I believe it's actually fairly likely that they have full legal rights to it, thus you may not have a legal right to do anything at all with it.
You should probably check your contract or consult a lawyer to determine your exact legal rights.
The design versus other aspects
In website development, there may be other factors, like performance, that also plays a role. Having it be seen supporting a large user base efficiently can be a lot better than a sandbox view of it.
Proof of the accomplishment
Saying you developed this for some company (even with a link provided) isn't quite the same as pointing them to the company website which shows them running it.
Regarding redesign
If you just say you developed a website, with or without mentioning that it's been redesigned, isn't good - either you don't have anything to demonstrate, or you are passing off someone else' work off as your own.
Uptime
This can go for either the company website or your website.
With your website, you have a fair amount of control over scheduled downtime.
A company website is more likely to be the target of Denial of Service attacks or hacks.
With your website, you probably don't have the top of the line hosting, so it's more likely that there's some expected or unexpected downtime, and you may even find yourself without a host in the worst case.
The extreme example is a company website that is no longer live, which obviously favours your website.
answered May 12 '14 at 19:30
Dukeling
8,66632347
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Is it legal?
This is perhaps the most important question.
If you developed it for an employer, I believe it's actually fairly likely that they have full legal rights to it, thus you may not have a legal right to do anything at all with it.
You should probably check your contract or consult a lawyer to determine your exact legal rights.
The design versus other aspects
In website development, there may be other factors, like performance, that also plays a role. Having it be seen supporting a large user base efficiently can be a lot better than a sandbox view of it.
Proof of the accomplishment
Saying you developed this for some company (even with a link provided) isn't quite the same as pointing them to the company website which shows them running it.
Regarding redesign
If you just say you developed a website, with or without mentioning that it's been redesigned, isn't good - either you don't have anything to demonstrate, or you are passing off someone else' work off as your own.
Uptime
This can go for either the company website or your website.
With your website, you have a fair amount of control over scheduled downtime.
A company website is more likely to be the target of Denial of Service attacks or hacks.
With your website, you probably don't have the top of the line hosting, so it's more likely that there's some expected or unexpected downtime, and you may even find yourself without a host in the worst case.
The extreme example is a company website that is no longer live, which obviously favours your website.
answered May 12 '14 at 19:30
Dukeling
8,66632347
Is it legal?
This is perhaps the most important question.
If you developed it for an employer, I believe it's actually fairly likely that they have full legal rights to it, thus you may not have a legal right to do anything at all with it.
You should probably check your contract or consult a lawyer to determine your exact legal rights.
The design versus other aspects
In website development, there may be other factors, like performance, that also plays a role. Having it be seen supporting a large user base efficiently can be a lot better than a sandbox view of it.
Proof of the accomplishment
Saying you developed this for some company (even with a link provided) isn't quite the same as pointing them to the company website which shows them running it.
Regarding redesign
If you just say you developed a website, with or without mentioning that it's been redesigned, isn't good - either you don't have anything to demonstrate, or you are passing off someone else' work off as your own.
Uptime
This can go for either the company website or your website.
With your website, you have a fair amount of control over scheduled downtime.
A company website is more likely to be the target of Denial of Service attacks or hacks.
With your website, you probably don't have the top of the line hosting, so it's more likely that there's some expected or unexpected downtime, and you may even find yourself without a host in the worst case.
The extreme example is a company website that is no longer live, which obviously favours your website.
answered May 12 '14 at 19:30
Dukeling
8,66632347
answered May 12 '14 at 19:30
Dukeling
8,66632347
answered May 12 '14 at 19:30
Dukeling
8,66632347
answered May 12 '14 at 19:30
Dukeling
8,66632347
8,66632347
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
add a comment |Â
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
Hi Dukeling, thanks for the reply! But I'm still kind of confused. Are you implying it is better not to leave actual site urls? I thought it's more convincing to have some live sites in resume like mentioned here blog.codinghorror.com/a-programmers-portfolio
– dgahel
May 12 '14 at 21:21
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
@dgahel There isn't one answer that's always right - it depends on the circumstances and what you're trying to show off. I mentioned that it may not be legal (you'll have to investigate that, as it depends on your circumstances), and beyond that gave you some pro's and cons to ponder over in order to make an informed decision yourself.
– Dukeling
May 12 '14 at 21:36
add a comment |Â
up vote
1
down vote
As a developer, using an actual site is risky for the following reasons:
- A poor user experience may make you look bad, even though the code is good
- Developer specific work like test assertions and build scripts are not visible
- Poor CDN configuration such as minified code without source maps may make code hard to demonstrate
- You may need to login using real credentials which can compromise your personal information
Using a demo site is also risky for different reasons:
- The code you demo may not make sense outside the context of the real site
- The techniques used in the code may be outdated based on the architecture of the real site
- The things you demo may violate some company policy, especially if the business logic depends on company specific mock data structures
Focusing on generic things like stackoverflow questions you've answered or specific things like articles you've written or algorithms you've implemented may be a better choice.
References
Clearing your Front End Job Interview  —  JavaScript
Algorithms With Javascript For Coding Interview
answered Mar 11 at 23:45
Paul Sweatte
20514
add a comment |Â
up vote
1
down vote
As a developer, using an actual site is risky for the following reasons:
- A poor user experience may make you look bad, even though the code is good
- Developer specific work like test assertions and build scripts are not visible
- Poor CDN configuration such as minified code without source maps may make code hard to demonstrate
- You may need to login using real credentials which can compromise your personal information
Using a demo site is also risky for different reasons:
- The code you demo may not make sense outside the context of the real site
- The techniques used in the code may be outdated based on the architecture of the real site
- The things you demo may violate some company policy, especially if the business logic depends on company specific mock data structures
Focusing on generic things like stackoverflow questions you've answered or specific things like articles you've written or algorithms you've implemented may be a better choice.
References
Clearing your Front End Job Interview  —  JavaScript
Algorithms With Javascript For Coding Interview
answered Mar 11 at 23:45
Paul Sweatte
20514
add a comment |Â
up vote
1
down vote
up vote
1
down vote
As a developer, using an actual site is risky for the following reasons:
- A poor user experience may make you look bad, even though the code is good
- Developer specific work like test assertions and build scripts are not visible
- Poor CDN configuration such as minified code without source maps may make code hard to demonstrate
- You may need to login using real credentials which can compromise your personal information
Using a demo site is also risky for different reasons:
- The code you demo may not make sense outside the context of the real site
- The techniques used in the code may be outdated based on the architecture of the real site
- The things you demo may violate some company policy, especially if the business logic depends on company specific mock data structures
Focusing on generic things like stackoverflow questions you've answered or specific things like articles you've written or algorithms you've implemented may be a better choice.
References
Clearing your Front End Job Interview  —  JavaScript
Algorithms With Javascript For Coding Interview
answered Mar 11 at 23:45
Paul Sweatte
20514
As a developer, using an actual site is risky for the following reasons:
- A poor user experience may make you look bad, even though the code is good
- Developer specific work like test assertions and build scripts are not visible
- Poor CDN configuration such as minified code without source maps may make code hard to demonstrate
- You may need to login using real credentials which can compromise your personal information
Using a demo site is also risky for different reasons:
- The code you demo may not make sense outside the context of the real site
- The techniques used in the code may be outdated based on the architecture of the real site
- The things you demo may violate some company policy, especially if the business logic depends on company specific mock data structures
Focusing on generic things like stackoverflow questions you've answered or specific things like articles you've written or algorithms you've implemented may be a better choice.
References
Clearing your Front End Job Interview  —  JavaScript
Algorithms With Javascript For Coding Interview
answered Mar 11 at 23:45
Paul Sweatte
20514
answered Mar 11 at 23:45
Paul Sweatte
20514
answered Mar 11 at 23:45
Paul Sweatte
20514
answered Mar 11 at 23:45
Paul Sweatte
20514
20514
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f23943%2fgive-demo-snapshot-site-rather-than-actual-site-in-web-developer-resume%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
@JoeStrazzere some freelance websites and actual job websites
– dgahel
May 12 '14 at 18:48