• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Code Portfolio

 
Ranch Hand
Posts: 434
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi there

Firstly, this is a hypothetical question (for anyone from my company reading this). But I figure that you leave every job at some point, right?

I want to put together a code portfolio and I have two questions.

1 - If our company does not have a policy with regards to taking code off the premises, then do I need to ask permission to use some of my code from company projects in my portfolio? Obviously not taking the core of the application such that it would be advantageous to a competitor if they got their hands on it. Also, I intend for it to be distributed only as a hard copy portfolio.

2 - If I do need to ask permission, how can I phrase it in such a way that it doesn't look like I'm looking for another job?

Many thanks,
Rachel
 
Ranch Hand
Posts: 1902
Hibernate Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hypothetically, I think it's probably better to ask questions about permission than not to, just because then you're covered if it turns out that someone really does have an issue with the matter (it looks more suspicious if no one's aware that you're doing it and you're caught, after all). And I think you have the best idea, namely keeping out the sections that would be a competative advantage for your current firm.

As for how to keep it from looking like you're looking for another job.. that's really more behavioral than a concern about code-sharing, I think. Just make it clear when you ask that you're not looking for another job, and have an explanation ready as to why you're putting together a portfolio.

Hope that helps!
 
Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I do not think I would mention it to management.

I think 2 .. 4 classes

you wrote

would be enough.

Most interviewers won't have the time to look at them.

Some pin heads, the kind in Dilbert, think a code portfolio is a nice piece of paper work. What's really important, is when you get to the interview with the techno-geek, you score well.

I don't believe it's ethical to leave any samples or photocopies with your prospective. If your a student, open source developer or a volunteer then you may do as you please.

Seldom have I seen a code sample asked for.
 
and POOF! You're gone! But look, this tiny ad is still here:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic