I always describe parts of the work ex) "While building RESTful Web Services I wrote a server-sided cache system that reduced dynamic database queries by 67% and improved the services response time by 46%". Mention notable things, don't pile on information to interviewers.
I've conducted interviews and there are things that mean nothing to me: how many lines of code you've written (you may write one billion lines of code that do absolutely nothing, I really don't care), how many projects you've completed (project is a very vague word, you may have been hired to write a shell script that echos 'foo'; is that a real project? no one knows).
What I do care about are your achievements, work you're proud of.
thanks, Jake
I have no restrictions in my work it's just a matter of ethics, and actually, I was asking if it is ok to talk about the code architecture, infrastructure.
If you don't have any written restrictions then technically you can talk about anything. Ethically it's entirely up to you, ask yourself: "If I had hired this person what wouldn't I want them talking about in regards to this job?". Architecture & Infrastructure are great topics to bring up in interviews.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I always describe parts of the work ex) "While building RESTful Web Services I wrote a server-sided cache system that reduced dynamic database queries by 67% and improved the services response time by 46%". Mention notable things, don't pile on information to interviewers.
I've conducted interviews and there are things that mean nothing to me: how many lines of code you've written (you may write one billion lines of code that do absolutely nothing, I really don't care), how many projects you've completed (project is a very vague word, you may have been hired to write a shell script that echos 'foo'; is that a real project? no one knows).
What I do care about are your achievements, work you're proud of.
thanks, Jake
I have no restrictions in my work it's just a matter of ethics, and actually, I was asking if it is ok to talk about the code architecture, infrastructure.
If you don't have any written restrictions then technically you can talk about anything. Ethically it's entirely up to you, ask yourself: "If I had hired this person what wouldn't I want them talking about in regards to this job?". Architecture & Infrastructure are great topics to bring up in interviews.