3 ms·

You know what kills an interview really fast? When you ask the candidate to see some code and they tell you every single thing is under NDA. Brah, if you're a

You know what kills an interview really fast? When you ask the candidate to see some code and they tell you every single thing is under NDA. Brah, if you're a programmer, you have at least some tinker code lying around that you can show.

hocuspocus 4y ago
If that were even remotely true then almost no Apple employee would ever manage to find another job.
ReptileMan 4y ago
The only thing I have is project Euler in haskell. What insights will you get about that corporate java job
- dinedal 4y ago
  If you're slinging Euler in Haskell, the insight is that you're probably overqualified for most corporate java jobs.
- recursive 4y ago
  That you can write code. That's a positive signal. There's a reason FizzBuzz exists.
scarface74 4y ago
I haven’t written a single piece of code outside of work since I started working - in 1996. The only reason I have any open source code is because my company has a very easy open source process. I extract reusable non customer identifying code from projects and it usually takes at most 3 days for approval. There is also a company sponsored open source project I contribute to.
Silhouette 4y ago
The point is that you might not want to show toy code. Toy code I've written for fun is rarely written to the same standards I'd use for anything important, including code written for work. It probably won't have elaborate CI/CD tooling with a clear branching strategy. It probably won't have a comprehensive test suite. It probably won't have systematic error handling. It probably won't have carefully written comments to help other people find their way around it. Most important of all it probably won't be designed or cleaned up to the standards of good professional code, because I wrote it for fun or to solve some specific problem and not to be a portfolio piece and I stopped once the code had served its purpose. If anyone I might work with insisted on judging me on code like that they'd never get a realistic view of my level. If I wanted to show someone an example of code that did faithfully represent what I can do I'd want to show them some of the many projects I've completed to a high professional standard at work. But of course that code really is usually confidential and at least in my case that tends to be because it's important to the business and might not be public knowledge yet so it really would be very unprofessional if I went around handing it out to anyone who asked.
astura 4y ago
I don't... I haven't written any code outside of my 9-5 job since I graduated from college almost 20 years ago. I am still a really good employee and I always get excellent performance reviews.
deleted 4y ago
[deleted]

hocuspocus 4y ago

If that were even remotely true then almost no Apple employee would ever manage to find another job.

ReptileMan 4y ago

The only thing I have is project Euler in haskell. What insights will you get about that corporate java job

dinedal 4y ago
If you're slinging Euler in Haskell, the insight is that you're probably overqualified for most corporate java jobs.
recursive 4y ago
That you can write code. That's a positive signal. There's a reason FizzBuzz exists.

scarface74 4y ago

I haven’t written a single piece of code outside of work since I started working - in 1996. The only reason I have any open source code is because my company has a very easy open source process. I extract reusable non customer identifying code from projects and it usually takes at most 3 days for approval. There is also a company sponsored open source project I contribute to.

Silhouette 4y ago

The point is that you might not want to show toy code. Toy code I've written for fun is rarely written to the same standards I'd use for anything important, including code written for work. It probably won't have elaborate CI/CD tooling with a clear branching strategy. It probably won't have a comprehensive test suite. It probably won't have systematic error handling. It probably won't have carefully written comments to help other people find their way around it. Most important of all it probably won't be designed or cleaned up to the standards of good professional code, because I wrote it for fun or to solve some specific problem and not to be a portfolio piece and I stopped once the code had served its purpose. If anyone I might work with insisted on judging me on code like that they'd never get a realistic view of my level. If I wanted to show someone an example of code that did faithfully represent what I can do I'd want to show them some of the many projects I've completed to a high professional standard at work. But of course that code really is usually confidential and at least in my case that tends to be because it's important to the business and might not be public knowledge yet so it really would be very unprofessional if I went around handing it out to anyone who asked.

astura 4y ago

I don't... I haven't written any code outside of my 9-5 job since I graduated from college almost 20 years ago. I am still a really good employee and I always get excellent performance reviews.

deleted 4y ago

[deleted]