4 ms·

The sad reality of software engineering is that the wast majority of code everyone writes is not something they would want to show in an interview. Even if they

The sad reality of software engineering is that the wast majority of code everyone writes is not something they would want to show in an interview. Even if they legally could, which is rarely the case for commercially developed software. Heck, even reasonably good software can produce a very negative impression. Utilitarian code can be seen as ugly or overly simplistic. Elegant conceptual stuff often runs the risk of grinding against biases and preconceptions of the particular reviewer.

Alacart 9y ago
Your first argument is true, but I would argue that if you already know what you're doing, you can write some demo portfolio code specifically to show off your skills in very little time. Make that code pleasant to read, free of legal constraints, and be ready and able to talk about it. You probably will spend at least 40 hours a week at your job and it will dramatically affect your life. That's worth spending a few days, maybe even a few weeks preparing for so that you can get one you like. For your second argument, I know what you mean, but that's also totally subjective, dictated by chance, and would apply equally across the board for all candidates. Even if that happens, it sort of naturally levels itself out competition-wise. Also, remember that you're evaluating the employer too - do you want to work for someone who chooses employees that way? Would you want to work with someone who has a closed mind and an axe to grind about certain concepts? I wouldn't trust people like that to make good decisions that will make the company succeed, thereby keeping me employed - let alone providing opportunities to advance. Plus they sound like they'd be a pain in the ass to work with.
- vonmoltke 9y ago
  > Make that code pleasant to read, free of legal constraints, and be ready and able to talk about it. That would be difficult for people who work for companies that claim presumptive ownership over everything they produce.
  - ameister14 9y ago
    Produce it on your own time, using no company resources. If a company claims ownership of everything you produce in your own time using your own resources, you've signed the worst contract possible and the company should go out of business. Most of the time, they claim things you make using their resources or company time. Avoiding that avoids most issues.
    - ryandrake 9y ago
      Anecdotal, but most companies I've worked for have policies that claim ownership of everything I produced in my own time on my own equipment. I think that's the rule, not the exception.
      - ameister14 9y ago
        That's awful. You should negotiate that out of the contract or at least limit it.
      - a-kojeve 9y ago
        Definitely not the norm and probably not enforceable. I hope you find a new job!

Alacart 9y ago

Your first argument is true, but I would argue that if you already know what you're doing, you can write some demo portfolio code specifically to show off your skills in very little time. Make that code pleasant to read, free of legal constraints, and be ready and able to talk about it. You probably will spend at least 40 hours a week at your job and it will dramatically affect your life. That's worth spending a few days, maybe even a few weeks preparing for so that you can get one you like. For your second argument, I know what you mean, but that's also totally subjective, dictated by chance, and would apply equally across the board for all candidates. Even if that happens, it sort of naturally levels itself out competition-wise. Also, remember that you're evaluating the employer too - do you want to work for someone who chooses employees that way? Would you want to work with someone who has a closed mind and an axe to grind about certain concepts? I wouldn't trust people like that to make good decisions that will make the company succeed, thereby keeping me employed - let alone providing opportunities to advance. Plus they sound like they'd be a pain in the ass to work with.

vonmoltke 9y ago
> Make that code pleasant to read, free of legal constraints, and be ready and able to talk about it. That would be difficult for people who work for companies that claim presumptive ownership over everything they produce.
- ameister14 9y ago
  Produce it on your own time, using no company resources. If a company claims ownership of everything you produce in your own time using your own resources, you've signed the worst contract possible and the company should go out of business. Most of the time, they claim things you make using their resources or company time. Avoiding that avoids most issues.
  - ryandrake 9y ago
    Anecdotal, but most companies I've worked for have policies that claim ownership of everything I produced in my own time on my own equipment. I think that's the rule, not the exception.
    - ameister14 9y ago
      That's awful. You should negotiate that out of the contract or at least limit it.
    - a-kojeve 9y ago
      Definitely not the norm and probably not enforceable. I hope you find a new job!