In this video, you will be introduced to some bad practices that many software engineers do when they are writing or designing their CV.
Notice that many of this practices could be needed or critical for other job positions. However, it's not favorable for software engineers.
Check out previous bash tutorials:
Top comments (9)
Can't you just write them down, so that we don't have to watch a 5min video?
I just needed to explain why each point is not preferable. If I just listed them without explanation, some may argue that they could be important.
You can use a transcription service like Speechpad (speechpad.com) to transcribe your videos for like $1 per minute, then easily paste that as your blog.
Maybe that would be helpful for cases like this where you want to record your ideas, but your audience would also find value in a written post.
Great points but would be better written (or podcast). Speaking of vizualizations that don't add value.
A podcast would be a good idea. I'll try that next time I create this type of content.
I'm afraid I disagree with the first part of the SUMMARY.
Recruiters and maybe the team's members remember the candidates based on their summary somehow. We mark our developers based on important parts of their summary like "The guy how were is expertise in infrastructure.".
My CV is written in LaTeX. I cannot possibly have colors, visualizations, stars, emojis, etc.
I thought the same when a friend told me about LaTeX, but you can make some great templates from Overleaf
I suggest you write instead of put a video. I read on the phone and I don't want to pair my bluetooth headphone right now.