3 ms·

You may ignore skills sections, but a great deal of people utilize them. They're hiring a guy who can write React code, so they look for the word "React" and so

by muzani 4y ago

You may ignore skills sections, but a great deal of people utilize them. They're hiring a guy who can write React code, so they look for the word "React" and some measure of experience, and it gets put on the phone interview pile. I don't necessarily agree with it, but too often the resume has to go through people who don't have tech proficiency and skim the thing. Or a bot. The skills section is like the armor plated casing that doesn't do the real damage, but punches through that layer.

scarface74 4y ago
In that case in your bullet point. - “Used React to do $x”
- muzani 4y ago
  Some practical scenarios. I want to hire people who code in Kotlin. I personally know it cuts down LOC by 40% vs Java. But I don't care that they've measured this process or why they do it, as long as they code in Kotlin. I want to hire someone who uses Room to access DB vs direct SQLite queries. I know it's used for databases and I know it cuts down mistakes by a lot of %. Someone who uses Jetpack Compose. Or Kotlin Flow. I know the benefits of these. And in many cases there are no measurable benefits - it makes debugging harder, but also means less bugs as an application scales. Compose cuts necessary code to write/maintain by half in some instances, but cuts down on the cognitive load by a hell lot. I don't need to see the whys in a resume. They have a high learning curve. They're battlefield tested. I need someone who can use an assault rifle. It's cool if they won a war with a spear, but I'd rather hire a newbie with an assault rifle for the position.
  - scarface74 4y ago
    I’m not saying the BS about “Wrote a React app that brought in 50% more revenue”. I’m saying “Used React to create $YetAnotherSaasCRUDApp”. I want to know you did something with it besides write Yet Another TODO app following a tutorial.

by muzani 4y ago

scarface74 4y ago

In that case in your bullet point. - “Used React to do $x”

muzani 4y ago
Some practical scenarios. I want to hire people who code in Kotlin. I personally know it cuts down LOC by 40% vs Java. But I don't care that they've measured this process or why they do it, as long as they code in Kotlin. I want to hire someone who uses Room to access DB vs direct SQLite queries. I know it's used for databases and I know it cuts down mistakes by a lot of %. Someone who uses Jetpack Compose. Or Kotlin Flow. I know the benefits of these. And in many cases there are no measurable benefits - it makes debugging harder, but also means less bugs as an application scales. Compose cuts necessary code to write/maintain by half in some instances, but cuts down on the cognitive load by a hell lot. I don't need to see the whys in a resume. They have a high learning curve. They're battlefield tested. I need someone who can use an assault rifle. It's cool if they won a war with a spear, but I'd rather hire a newbie with an assault rifle for the position.
- scarface74 4y ago
  I’m not saying the BS about “Wrote a React app that brought in 50% more revenue”. I’m saying “Used React to create $YetAnotherSaasCRUDApp”. I want to know you did something with it besides write Yet Another TODO app following a tutorial.