Mixing
Can I censor certain parts of source code submitted to recruiters [duplicate]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
This question already has an answer here:
What are employers looking for when they ask to see sample code during the hiring process for a programmer?
7 answers
I am currently looking for my first job in software development. A recruitment agency has asked me for some example code to show to a prospective employer.
The only relevant and substantial code I have at present is my final degree project. However, I am intending to patent and copyright this app for future personal release, so I am a little wary of letting the source go to other companies.
Should I redact/censor the sensitive parts of the code I submit, although that will render the app inoperable? Or is there another way of protecting my idea / code whilst still presenting it as an example?
software-industry job-search
asked Feb 22 '16 at 11:35
Fubrite
464
marked as duplicate by Lilienthal♦, gnat, Masked Man♦, Dawny33, panoptical Feb 22 '16 at 19:05
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
suggest improvements |Â
up vote
1
down vote
favorite
This question already has an answer here:
What are employers looking for when they ask to see sample code during the hiring process for a programmer?
7 answers
I am currently looking for my first job in software development. A recruitment agency has asked me for some example code to show to a prospective employer.
The only relevant and substantial code I have at present is my final degree project. However, I am intending to patent and copyright this app for future personal release, so I am a little wary of letting the source go to other companies.
Should I redact/censor the sensitive parts of the code I submit, although that will render the app inoperable? Or is there another way of protecting my idea / code whilst still presenting it as an example?
software-industry job-search
asked Feb 22 '16 at 11:35
Fubrite
464
marked as duplicate by Lilienthal♦, gnat, Masked Man♦, Dawny33, panoptical Feb 22 '16 at 19:05
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
4
This is probably too situational to get a universal answer: some interviewers will be fine with partial or censored code, some will consider it useless. I think your question may be answered by the answers on this question.
– Lilienthal♦
Feb 22 '16 at 11:43
suggest improvements |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
This question already has an answer here:
What are employers looking for when they ask to see sample code during the hiring process for a programmer?
7 answers
I am currently looking for my first job in software development. A recruitment agency has asked me for some example code to show to a prospective employer.
The only relevant and substantial code I have at present is my final degree project. However, I am intending to patent and copyright this app for future personal release, so I am a little wary of letting the source go to other companies.
Should I redact/censor the sensitive parts of the code I submit, although that will render the app inoperable? Or is there another way of protecting my idea / code whilst still presenting it as an example?
software-industry job-search
asked Feb 22 '16 at 11:35
Fubrite
464
This question already has an answer here:
What are employers looking for when they ask to see sample code during the hiring process for a programmer?
7 answers
I am currently looking for my first job in software development. A recruitment agency has asked me for some example code to show to a prospective employer.
The only relevant and substantial code I have at present is my final degree project. However, I am intending to patent and copyright this app for future personal release, so I am a little wary of letting the source go to other companies.
Should I redact/censor the sensitive parts of the code I submit, although that will render the app inoperable? Or is there another way of protecting my idea / code whilst still presenting it as an example?
This question already has an answer here:
What are employers looking for when they ask to see sample code during the hiring process for a programmer?
7 answers
software-industry job-search
asked Feb 22 '16 at 11:35
Fubrite
464
asked Feb 22 '16 at 11:35
Fubrite
464
asked Feb 22 '16 at 11:35
Fubrite
464
asked Feb 22 '16 at 11:35
Fubrite
464
464
marked as duplicate by Lilienthal♦, gnat, Masked Man♦, Dawny33, panoptical Feb 22 '16 at 19:05
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Lilienthal♦, gnat, Masked Man♦, Dawny33, panoptical Feb 22 '16 at 19:05
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
4
This is probably too situational to get a universal answer: some interviewers will be fine with partial or censored code, some will consider it useless. I think your question may be answered by the answers on this question.
– Lilienthal♦
Feb 22 '16 at 11:43
suggest improvements |Â
4
This is probably too situational to get a universal answer: some interviewers will be fine with partial or censored code, some will consider it useless. I think your question may be answered by the answers on this question.
– Lilienthal♦
Feb 22 '16 at 11:43
4
4
This is probably too situational to get a universal answer: some interviewers will be fine with partial or censored code, some will consider it useless. I think your question may be answered by the answers on this question.
– Lilienthal♦
Feb 22 '16 at 11:43
This is probably too situational to get a universal answer: some interviewers will be fine with partial or censored code, some will consider it useless. I think your question may be answered by the answers on this question.
– Lilienthal♦
Feb 22 '16 at 11:43
suggest improvements |Â
2 Answers
2
active
oldest
votes
up vote
5
down vote
All the companies I interviewed for so far didn't try to actually run the code, AFAIK. They just wanted to check the quality of the code.
So, as long as your code is good, censor it. Maybe tell them why you censored some of it when you send them the code.
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
suggest improvements |Â
up vote
3
down vote
Just like on Stack Overflow, you could prepare a Minimal, Complete, and Verifiable example.
Your application isn't all new and perfect and shiny. It is bound to have code that just does the boring work. Like a public algorithm you implemented? Or a subroutine that is necessary, but not really patent-worthy? Or any part of the program that is just plain old coding work.
Extract that part. Extract the unit tests for that part. Deliver it.
edited May 23 '17 at 12:37
Community♦
1
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
suggest improvements |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
All the companies I interviewed for so far didn't try to actually run the code, AFAIK. They just wanted to check the quality of the code.
So, as long as your code is good, censor it. Maybe tell them why you censored some of it when you send them the code.
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
suggest improvements |Â
up vote
5
down vote
All the companies I interviewed for so far didn't try to actually run the code, AFAIK. They just wanted to check the quality of the code.
So, as long as your code is good, censor it. Maybe tell them why you censored some of it when you send them the code.
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
suggest improvements |Â
up vote
5
down vote
up vote
5
down vote
All the companies I interviewed for so far didn't try to actually run the code, AFAIK. They just wanted to check the quality of the code.
So, as long as your code is good, censor it. Maybe tell them why you censored some of it when you send them the code.
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
All the companies I interviewed for so far didn't try to actually run the code, AFAIK. They just wanted to check the quality of the code.
So, as long as your code is good, censor it. Maybe tell them why you censored some of it when you send them the code.
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
edited Feb 22 '16 at 13:04
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
answered Feb 22 '16 at 11:49
GustavoMP
1,6842816
1,6842816
suggest improvements |Â
suggest improvements |Â
up vote
3
down vote
Just like on Stack Overflow, you could prepare a Minimal, Complete, and Verifiable example.
Your application isn't all new and perfect and shiny. It is bound to have code that just does the boring work. Like a public algorithm you implemented? Or a subroutine that is necessary, but not really patent-worthy? Or any part of the program that is just plain old coding work.
Extract that part. Extract the unit tests for that part. Deliver it.
edited May 23 '17 at 12:37
Community♦
1
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
suggest improvements |Â
up vote
3
down vote
Just like on Stack Overflow, you could prepare a Minimal, Complete, and Verifiable example.
Your application isn't all new and perfect and shiny. It is bound to have code that just does the boring work. Like a public algorithm you implemented? Or a subroutine that is necessary, but not really patent-worthy? Or any part of the program that is just plain old coding work.
Extract that part. Extract the unit tests for that part. Deliver it.
edited May 23 '17 at 12:37
Community♦
1
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
Just like on Stack Overflow, you could prepare a Minimal, Complete, and Verifiable example.
Your application isn't all new and perfect and shiny. It is bound to have code that just does the boring work. Like a public algorithm you implemented? Or a subroutine that is necessary, but not really patent-worthy? Or any part of the program that is just plain old coding work.
Extract that part. Extract the unit tests for that part. Deliver it.
edited May 23 '17 at 12:37
Community♦
1
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
Just like on Stack Overflow, you could prepare a Minimal, Complete, and Verifiable example.
Your application isn't all new and perfect and shiny. It is bound to have code that just does the boring work. Like a public algorithm you implemented? Or a subroutine that is necessary, but not really patent-worthy? Or any part of the program that is just plain old coding work.
Extract that part. Extract the unit tests for that part. Deliver it.
edited May 23 '17 at 12:37
Community♦
1
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
edited May 23 '17 at 12:37
Community♦
1
edited May 23 '17 at 12:37
Community♦
1
edited May 23 '17 at 12:37
Community♦
1
1
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
answered Feb 22 '16 at 11:50
nvoigt
42.6k18105147
42.6k18105147
suggest improvements |Â
suggest improvements |Â
4
This is probably too situational to get a universal answer: some interviewers will be fine with partial or censored code, some will consider it useless. I think your question may be answered by the answers on this question.
– Lilienthal♦
Feb 22 '16 at 11:43