I think its only reasonable that if I must show u my code during i terview process, I get to see some of the code that I'll get to work with if I'm hired.

Starting to think employers just straight up lie up everything..

Why do i need to find out about your shit code on the first day?!
Cutting edge tech my ass...

  • 7
    One of the questions I thought to try during my next interview: "What measures do you take to ensure the quality of the code in your products stays high?"

    It should become apparent if they have never heard of coding standards, unit tests, code reviews, pair programming, and so on - all things to ensure you don't end up working with the kind of codebase I'm working with at the moment... *sigh
  • 3
    @Qwby yes, I'm also devising a list of questions that I'm going to ask next time.
    Thinking of staying away from anything that was written more than 3 years ago either way..
    I'm not interested in maintaining some legacy code with new features that a brainless monkey can add.. I'm here for fucking creating new things, and solve real problems
  • 8
    It's a fair question to ask them.

    How they answer sets the tone for the kind of place it will be to work. If they won't consider it, they view themselves as having the upper hand, as though you are begging for the job.

    I hope it goes without saying, but people should never accept jobs at places that act like you should be grateful just to work there; that kind of mentality is top down.
  • 5
    Don't know if I should write a separate rant but just as an example of what I have to deal with:

    The products I have to maintain use SQLj. For security. Have you ever heard of SQLj? Me neither. IntelliJ just marks this code as an error, because JetBrain even said back in 2008 there are no plans to support an obsolete standard that is that old, and nobody bothered with creating a plug-in for it.

    You can imagine it's great to work on these products when you know that articles like this exist: https://blog.jooq.org/2014/01/...

    And that's just 1 of 20 things that's too old to find any knowledgeable developers for. Working with projects that are 5 years old would be heaven in comparison. Yet they said I would be working with "transforming this company to a new technical era and tech stack". The "new" tech stack is using frameworks that nobody has heard of either... urgh.
  • 2
    SQLj has the downside of being borderline esoteric. It's like Apache orb, or struts.
  • 0
    Been in a company where they rejected a potential good candidate because he wasn't applying some standards for development.

    By standards I ofc mean made up shit which is company-specific and deliriums like NEVER use for each "because it's slower"
Add Comment