SillyCon Valley

Shooing recruiters away

To reel in great software engineering talent, you recruiting team needs to spend time  looking only for truly compelling resumes. These not only narrate the work and education story of the devs but also allows them to know that candidates have the necessary skills, education and experience to perform a good – even outstanding – job.

You will most likely want your applicants to stay away from resume points that only show what they were assigned to do and what they did in the role – usually referred to as ‘grunt’. This is not a good description of how they spent their time in any past professional scenario. Instead, look for impact statements that focus on what was accomplished, what the outcome was and what impact they made, like “developed X to accomplish Y, resulting in Z”.

Should you look – or worse, ask – for a pic on a resume? Not really (in LATAM, you’d be surprised how many recruiters and HR managers make this mistake) Look for links to their GitHub, StackOverflow, or LinkedIn profiles, each of which may or may not have a profile picture.

Is your recruiting team being shooed away – and wasting time – thanks in part to an influx of poorly crafted resumes? If such is the case, let us help you find out what works best for you. 

CONTACT US, WE CAN HELP!

Sometimes, we just don’t function.

As a CTO, you probably know that functions are a good alternative to having repeating blocks of code in a program while also increasing the reusability of code. Values can be passed to a function using variables called parameters or arguments. They can also return values and do many other nice, cool things with software that’ll make you look good, even if your devs didn’t have coffee that day.

But we’re all human after all, aren’t we? Sometimes even the highest coveted software engineers might simply have had a bad day at home and not call their functions. Should this be the case, if you want to reduce a complicated program into smaller, more manageable chunks and avoid unnecessary complexity in a program to ease your day (and your output)…have your dev team remember to create – and call – their functions.

But just in case…make sure they are wearing spandex pants or stretch jeans.

And if your development team could use some overhaul to function properly…

CALL US NOW TO FIND OUT HOW WE CAN HELP

Not all specs are stitched together, like Frankenstein’s monster. 

The most commonly known best practices in software development determine that a document that describes what the software will do and how it will be expected to perform is created as a first step. It also describes the functionality the product needs to fulfill the needs of the user. This being said, have you found yourself in a position where you throw a bunch of specs at a developer, simply hoping that the outcome does indeed fulfill the expected needs and functionalities, only to be deceived? If the outcome was less than satisfactory, was it because of the specs themselves, the development team’s quirks, sheer bad luck or an act of God?

We’d love the chance to help you find out!

CALL US NOW TO FIND OUT HOW WE CAN HELP

To comment, or not to comment. That is the geeky question.

Commenting involves placing human readable descriptions inside of computer programs detailing what the code is doing. Some developers are convinced that proper use of commenting can make code maintenance much easier, as well as helping make finding bugs faster… But is that always the case? Some geeky devs believe that well-documented code is as important as correctly working code.

What do you think? We’d love to help you find out the best approach!

CALL US NOW TO FIND OUT HOW WE CAN HELP