3 ms·

That's the reason I do algorithmic whiteboard instead of full blown "real world" coding exercises. I don't care that someone memorized whatever command line sy

That's the reason I do algorithmic whiteboard instead of full blown "real world" coding exercises. I don't care that someone memorized whatever command line syntax to create a new project in whatever framework. That's just rote. Even what we write on the whiteboard I don't expect it to compile. Is it ToString or toString? Can't recall either. What I care about is that someone can ask the relevant questions, come up with a design and explain what and why they are doing something.

_the_inflator 6y ago
And afterwards? What is the hired guy then doing? Fixing the size of a button? ;)
- munk-a 6y ago
  That really depends on how much management there is for hand holding. I expect a good developer to get a ticket to fix the size of a button and be able to follow up with stakeholders about the size of the button next to it. It'd be really weird if we sunk so much effort into ticket writing that everything really was just reduced to a task - at that point the ticket author should just go ahead and fix the thing.
  - 908B64B197 6y ago
    A dedicated ticket to go fix a button. That's a symptom of a pretty dysfunctional org. If my requirements are that precise I'll farm that to offshored contractors.
    - selfhoster11 6y ago
      It's a symptom of a well organised org. The ticket doesn't need to have a lot of detail (unless your ticketing system is dysfunctional and forces you to input a lot of information, which is sadly more common than it needs to be), only enough to capture what needs to be done and where so it's not forgotten. It's no different to filing a ticket with the building management to replace a broken lightbulb - it's in your interest to know whether they replaced it already without having to stand up from your desk to check, and it's in their interest to know which individual problems are located where so that they can plan their weekly maintenance run through the building accordingly.
lvncelot 6y ago
Last interview I had, I was encouraged to google and afterwards, we talked about the resources I sought out and how I used that information. It was a good experience - if it's a part of my job, why not make it a part of the interview?

_the_inflator 6y ago

And afterwards? What is the hired guy then doing? Fixing the size of a button? ;)

munk-a 6y ago
That really depends on how much management there is for hand holding. I expect a good developer to get a ticket to fix the size of a button and be able to follow up with stakeholders about the size of the button next to it. It'd be really weird if we sunk so much effort into ticket writing that everything really was just reduced to a task - at that point the ticket author should just go ahead and fix the thing.
- 908B64B197 6y ago
  A dedicated ticket to go fix a button. That's a symptom of a pretty dysfunctional org. If my requirements are that precise I'll farm that to offshored contractors.
  - selfhoster11 6y ago
    It's a symptom of a well organised org. The ticket doesn't need to have a lot of detail (unless your ticketing system is dysfunctional and forces you to input a lot of information, which is sadly more common than it needs to be), only enough to capture what needs to be done and where so it's not forgotten. It's no different to filing a ticket with the building management to replace a broken lightbulb - it's in your interest to know whether they replaced it already without having to stand up from your desk to check, and it's in their interest to know which individual problems are located where so that they can plan their weekly maintenance run through the building accordingly.

lvncelot 6y ago

Last interview I had, I was encouraged to google and afterwards, we talked about the resources I sought out and how I used that information. It was a good experience - if it's a part of my job, why not make it a part of the interview?