📃 Make your resume stand out and write your docs with semantic line breaks - 123dev #4
Posted on September 9, 2021 • 3 minutes • 484 words
There’s been a lot of open source news this week between my current employer and Elastic. I have nothing to do with it directly, but it reminds me that open source is people which means there will always be drama.
Even when it’s billion dollar companies it often comes down to a small number of people making decisions. I think this weeks drama hurt the image of open source more than it helped.
I got to review a resume for someone graduating university soon and gave them some feedback. The main thing I tried to explain is your resume needs to focus on what you’ve done, not what you know. You are trying to enter a business contract with someone and they need to know that you have shown a repeated ability to work for money.
It helps a lot if you can quantify the work you’ve done even if the numbers don’t seem impressive to you. “Helped customers do X” is not as good as “Helped twelve customers do X”. It’s even better if you can point out what you did to make the process or product better for you, your employer, or the customer.
If you write markdown or similar markup language docs you owe it to yourself to learn about writing with symantic line breaks. I didn’t know it had a name before last week even though I was always a big proponent to writing this way. It makes editing and reviewing documentation much easier.
Semantic Line Breaks — sembr.org When writing text with a compatible markup language, add a line break after each substantial unit of thought.
Julia has been writing technical zines for a long time now. I’m glad she shared her thought process in how to explain technical content with cartoons. The best news is, you don’t have to be an artist to draw!
How to teach technical concepts with cartoons How to teach technical concepts with cartoons
If you write go and use the AWS SDK you may want to know v2 is generally available. I spent a couple days last week writing an example application and then a couple days converting it to v2 SDK to give it a try.
Updating the SDK was not trivial even though my tool was only a few hundred lines of code. But there are quite a few benefits like improved performance and more go-like API calls that may be worth upgrading for.
AWS SDK for Go Version 2 – General Availability | AWS Developer Tools Blog — aws.amazon.com We are excited to announce the General Availability (GA) release of the AWS SDK for Go version 2 (v2). This release follows the Release candidate of the AWS SDK for Go v2. Version 2 incorporates customer feedback from version 1 and takes advantage of modern Go language features. The AWS SDK for Go v2 requires […]