5 ms·

I'm curious, do you not have any hobbies or better things to do than interview? Interviewing when I want a new job is already difficult enough with how much I h

I'm curious, do you not have any hobbies or better things to do than interview? Interviewing when I want a new job is already difficult enough with how much I have going on

throwawaysleep 5y ago
I am usually taking it out of work time, usually in the form of code approvals that I barely read or just ctrl+f for console.logs. If I have an interview, all code that day is going through.
- silicon2401 5y ago
  Genius. How do you get away with this though? Is your workload really slow? Whenever I try getting cheeky like this I end up stressing about how my workload piling up. Maybe this would be a good motivation to focus and work more effectively
- smt88 5y ago
  So you keep your hobbies, but you find time to interview by neglecting your responsibility to review code. I assume that means any users of your code are less protected from security vulnerabilities, right? I don't think anyone should have fondness for their employer -- it's a business relationship -- but you also have an ethical obligation to do what you're being paid to do. Otherwise, don't agree to do it in the first place.
  - silicon2401 5y ago
    > I don't think anyone should have fondness for their employer -- it's a business relationship -- but you also have an ethical obligation to do what you're being paid to do. Otherwise, don't agree to do it in the first place. I disagree with this view. My employment is a simple arrangement: entity X pays me $Y to be their employee. To some extent, they can tell me to do things and I'll do things in response. It's up to me to find a new employer if I'm unhappy with what they're telling me to do (or the salary, etc), and it's up to them to have a convo with me or fire me if they're unhappy with what I do. If he hasn't gotten fired or even spoken to by his manager for his work, then his work is satisfactory.
  - type-r 5y ago
    Can you go into more detail on the ethical obligation an engineer has regarding rigorousness of code review? How does neglecting code review to interview elsewhere compare to neglecting code review to get other features out for the same employer? How about for a different employer that you're also being paid by?
    - smt88 5y ago
      > Can you go into more detail on the ethical obligation an engineer has regarding rigorousness of code review? The comment I responded to was not talking about rigor. They said they weren't doing the code review at all. > How does neglecting code review to interview elsewhere compare to neglecting code review to get other features out for the same employer? If my employer pays me to prioritize new features over code review, then any bugs that arise are their responsibility. If my employer pays me to do a code review, I take the money, and I don't review the code, then I'm responsible. My employer assigned the right amount of resources to code review, and I was dishonest about actually doing it. > How about for a different employer that you're also being paid by? I don't understand this one. You mean if you're a contractor and are neglecting code review to work on another contract? If you're a contractor, it depends on whether you're being paid for time or whether you're being paid for good code. If you're being paid for time, the above applies as well. If you're being paid for good code, then it's always your responsibility to review the code.
- blindmute 5y ago
  Do you have no pride in your craft?
  - ascendantlogic 5y ago
    This is a very blurry line. People in the industry always will be the first to tell you you owe companies no loyalty and to always look out for yourself first and foremost. But then when someone says they slack off on code reviews while they're interviewing suddenly they should be taking pride in their craft. As a matter of course I want to do a good job each and every day. But it's still a job and if I'm unhappy to the point I'm actively searching for another job do I still owe that company my best? I think multiple different people will have multiple different answers for that.
    - blindmute 5y ago
      In my opinion, pride in one's craft doesn't depend upon output quantity, but quality. It would be acceptable to slack by working less, taking longer to do things, etc. But the quality of what you do insert into the codebase, and allow to be inserted, should always be the highest. Nobody will remember how quickly or slowly you did a task, but they will see your name beside some shitty code in a git blame or PR approval and think "what the fuck was this guy doing?". To me, that's where an engineer should never impugn his reputation. Just my opinion though.

I'm curious, do you not have any hobbies or better things to do than interview? Interviewing when I want a new job is already difficult enough with how much I have going on

throwawaysleep 5y ago

I am usually taking it out of work time, usually in the form of code approvals that I barely read or just ctrl+f for console.logs. If I have an interview, all code that day is going through.

silicon2401 5y ago
Genius. How do you get away with this though? Is your workload really slow? Whenever I try getting cheeky like this I end up stressing about how my workload piling up. Maybe this would be a good motivation to focus and work more effectively
smt88 5y ago
So you keep your hobbies, but you find time to interview by neglecting your responsibility to review code. I assume that means any users of your code are less protected from security vulnerabilities, right? I don't think anyone should have fondness for their employer -- it's a business relationship -- but you also have an ethical obligation to do what you're being paid to do. Otherwise, don't agree to do it in the first place.
- silicon2401 5y ago
  > I don't think anyone should have fondness for their employer -- it's a business relationship -- but you also have an ethical obligation to do what you're being paid to do. Otherwise, don't agree to do it in the first place. I disagree with this view. My employment is a simple arrangement: entity X pays me $Y to be their employee. To some extent, they can tell me to do things and I'll do things in response. It's up to me to find a new employer if I'm unhappy with what they're telling me to do (or the salary, etc), and it's up to them to have a convo with me or fire me if they're unhappy with what I do. If he hasn't gotten fired or even spoken to by his manager for his work, then his work is satisfactory.
- type-r 5y ago
  Can you go into more detail on the ethical obligation an engineer has regarding rigorousness of code review? How does neglecting code review to interview elsewhere compare to neglecting code review to get other features out for the same employer? How about for a different employer that you're also being paid by?
  - smt88 5y ago
    > Can you go into more detail on the ethical obligation an engineer has regarding rigorousness of code review? The comment I responded to was not talking about rigor. They said they weren't doing the code review at all. > How does neglecting code review to interview elsewhere compare to neglecting code review to get other features out for the same employer? If my employer pays me to prioritize new features over code review, then any bugs that arise are their responsibility. If my employer pays me to do a code review, I take the money, and I don't review the code, then I'm responsible. My employer assigned the right amount of resources to code review, and I was dishonest about actually doing it. > How about for a different employer that you're also being paid by? I don't understand this one. You mean if you're a contractor and are neglecting code review to work on another contract? If you're a contractor, it depends on whether you're being paid for time or whether you're being paid for good code. If you're being paid for time, the above applies as well. If you're being paid for good code, then it's always your responsibility to review the code.
blindmute 5y ago
Do you have no pride in your craft?
- ascendantlogic 5y ago
  This is a very blurry line. People in the industry always will be the first to tell you you owe companies no loyalty and to always look out for yourself first and foremost. But then when someone says they slack off on code reviews while they're interviewing suddenly they should be taking pride in their craft. As a matter of course I want to do a good job each and every day. But it's still a job and if I'm unhappy to the point I'm actively searching for another job do I still owe that company my best? I think multiple different people will have multiple different answers for that.
  - blindmute 5y ago
    In my opinion, pride in one's craft doesn't depend upon output quantity, but quality. It would be acceptable to slack by working less, taking longer to do things, etc. But the quality of what you do insert into the codebase, and allow to be inserted, should always be the highest. Nobody will remember how quickly or slowly you did a task, but they will see your name beside some shitty code in a git blame or PR approval and think "what the fuck was this guy doing?". To me, that's where an engineer should never impugn his reputation. Just my opinion though.