469 karma · joined November 24, 2018
Go is especially well suited for this activity (disagree but irrelevant).
We can leverage 3D modeling to better facilitate this mapping process. Also it could be VR. Also we could reverse engineer these models from existing code (awesome idea, do it please, and blend it with an IDE for when I drill down into nodes).
I think a better question is: what if this conflict - and the accompanying energy and food shortages - are here to stay for the foreseeable future.
It's a hobby but i've had an indie label release and made a few bucks from streaming services and i pay for promotion with each new release.
Also a fan of numerous small commits - makes good documentation and elimates wasted time untangling hours of thought.
And when I'm reviewing the last thing I want is for someone to waste time doing me the favor of burying their journey into some "perfect" mega-commit
* Watch them to solve a series of programming challanges. Offer them assistance if they ask. Let them search the net for assistance. Let them choose the language because your candidate will need to be able to learn on the fly anyway. Speaking of that...
* Don't neglect personality assessment, lots of tools out there to assess. Maybe your candidate should demonstrate a thirst for knowledge, history of independent learning, and some raw determination. Avoid hypothetical questions here and look for red flags that could make them suck to work with.
* Have them hang out with the team for a while, this could be during the code challange.
* Use the same process for all candidates
"If there is hope it lies in the proles" - George Orwell, 1984
My favorite solution so far is delete social media and take away the audience.
But manual testing is for the birds and you cant put breakpoints in a distributed cloud architecure. Better to strike a balance with a variety of testing scopes depending on the complexity of a given area of the system.