this post was submitted on 14 Apr 2024
328 points (94.1% liked)

linuxmemes

21172 readers
990 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    328
    Code interviews for a PHP developer roles (reddthat.com)
    submitted 6 months ago by reddthat@reddthat.com to c/linuxmemes@lemmy.world
    128 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] lunarul@lemmy.world 2 points 6 months ago* (last edited 6 months ago)

    That is totally a non-trivial problem, which requires a lot more conception before it can be solved.

    Most candidates don't realize that. And when I say they split by single space I mean split(' '). Not even split(/\s+/).

    Does "don't" consist of one or two words? Should "www.google.com" be split into three parts? Etc.

    Yes, asking those questions is definitely what you should be doing when tackling a problem like this.

    If I got that feature request in a ticket, I'd send it back to conception.

    If I got it, I'd work together with the product team to figure out what we want and what's best for the users.

    If you asked me this question in an interview, I'd ask if you wanted a programmer, a requirements analysis, or a linguist and why you invite people for a job interview if you don't even know what role you are hiring for.

    That would be useful too. Personality, attitude, and ability to work with others in a team are also factors we look at, so your answer would tell me to look elsewhere.

    But to answer that question, I'm definitely not looking for someone who just executes on very clear requirements, that's a junior dev. It's what you do when faced with ambiguity that matters. I don't need the human chatGPT.

    Also, I'm not looking for someone perfectly solving that problem, because it doesn't even have a single clear solution. It's the process of arriving to a solution that matters. What questions do you ask? Which edge cases did you consider and which ones did you miss? How do you iterate on your solution and debug issues you run into on the way? And so on