I have been reviewing a lot of coding exercises and interviewing for a lot of developers this year, I can confirm this advice is bang on.
It's not just what you have done but also showing the thought process behind it and what you would like to do with more time.
I like to see the full commit history you can learn a lot about a developer by seeing what changes commit by commit, also if their commit messages are clear and logical.
Don't forget all the small things like moving as many imports as possible into dev imports to keep main bundle size down and don't forget to remove junk like console logs.
I have been reviewing a lot of coding exercises and interviewing for a lot of developers this year, I can confirm this advice is bang on.
It's not just what you have done but also showing the thought process behind it and what you would like to do with more time.
I like to see the full commit history you can learn a lot about a developer by seeing what changes commit by commit, also if their commit messages are clear and logical.
Don't forget all the small things like moving as many imports as possible into dev imports to keep main bundle size down and don't forget to remove junk like console logs.
Thanks a lot for the nice words and sharing your insights. That's very valuable.
I wasn't sure how many people actually investigate the commit history. But seems like I'm not the only one :)