Where programmers share ideas and help each other grow. All developers are welcome to submit stories, tutorials, questions, or anything worth discussing. The front page is curated by the folks behind @ThePracticalDev.
Have fun and don't be afraid to contribute, everyone's perspective is valuable! ✌️
I am thinking starting small (in a limited group of people) to try this out.
1. Find (or write) a codebase to refactor - this might not be that easy, since not everyone is willing to give up their ugly source code for chopping
2. Define metrics for successful refactoring (tools for static code analysis?) - for example Sonar, or similar
3. Provide beer an pizza :)
Wanted to do psychology, one day someone asked me "soo.. <.< psychology huh... what are you gonna do with that... I was so sure I knew what I wanted to do, and that moment I don't why I just felt lost. I was in the library after that break and my girlfriend at the time, was like, you should take college more seriously, I was like "aight fine". Looked up high paying jobs, found that computer oriented jobs seemed to be up there, I said "hey I like computers", so I signed up for it just like that... I spent the summer before my first semester diving into it, every day got more and more exciting, I saw a whole new world and it was made of code. Never turned back since, except those last 3 years where I took a break, found passion for life and explore my creative perspectives. Some source code manipulation you know. Now with long hair and beard, the coding world welcomes me 2.0
We set them a task of building a font page of a site, this allowed us to know where they were, we gave feedback and they were told to improve what they had done. This went on for a 4 week period and it was quite effective, they weren't experts by any means but they were confident and knew how to figure out problems.
It might seem like a long time, but it was worth it in the end we saw these people produce better work in a shorter space of time compared to the other hires that didn't end up going through our process.
I think the most important thing to do when hiring new staff members (junior or expert) is to make them feel confident and comfortable, that way they feel more empowered and have ownership on what they are doing and don't have anxiety of what they are going to have to battle on that day.
Things I have found most effective
Documentation (you can say code should document itself, but you forget other people aren't at the same level as you)
Maintainable code (if not document why and how to work with it)