Explore >> Select a destination
|
You are here 
|
initialcommit.com | ||
| | | | |
www.techelevator.com
|
|
| | | | | The relationship between math and programming and answering the question "How much math do I need to be good at this?" | |
| | | | |
blog.hulacorn.com
|
|
| | | | | From Atalanta to Korea to Virginia, this is how I got into my first software engineering job. | |
| | | | |
claritydev.net
|
|
| | | | | Lately, I have been asked increasingly often for some tips on how to become a self-taught developer, so I thought I'd write a post about it, reflecting on my experience and pointing out the things I'd do differently. In this article, I'll try to give general advice on how to improve for those considering or maybe already on the way to becoming self-taught software developers. It should be noted that the focus of the post is on front-end development since that's what I did; however, a majority of the advice can be applied to becoming a software engineer, irrespective of focus. | |
| | | | |
code.dblock.org
|
|
| | | When I joined Microsoft in '99 I was taught how to properly interview candidates. I was shown the wheel of competencies, a kind of a wheel of fortune where a color represents the candidate's technical skill, ability to solve complicated problems or to communicate with their peers. Each slice included broad interviewing suggestions, which often gave birth to elaborate puzzles. What could possibly be the best way to figure out whether the candidate is capable of thinking out of the box? Ask them why the potholes are round. Can they crank complex working code on a deadline? Ask them to implement a memory allocator in 30 minutes or less in C. | ||
