Skip to content
markdown guide

I think including an API you built in your portfolio is fine. It gives the potential employer/client a lot of things to check out, like:

  • is the code written cleanly?
  • is it documented?
  • are there tests?

You could even write a small case study on it and host it on your personal site. That'll let people get a sense of a) what it does, b) why you built it, and c) any interesting problems you had to solve.


Building a presence online (ie. writing posts and participating to conversations about backend stuff), keepin your resume updated with details o what you did here and there and possibly having some github activity (if you have time) can all help.

GitHub is optional, the resume needs to be updated anyway, so... I guess blogging is the way :)

I'm sure others will have other ideas I can't think of now.


I agree with @rhymes , but I would add that is more important to have a few high quality posts than a bunch of unfinished stuff. At least that is my experience.
For instance, you can write a post about how to optimize a query.


This is definitely an issue for backed devs. My suggestion would be to blog about the product/project you build and include the challenges and specs you worked on, the technical metrics like the load the system can handle, the design patterns you used, argument your design decisions.


thank you guys... so remember that for us backend devs, mostly blogging will help us. It sounds like producing a lot of docs

Classic DEV Post from Jun 23 '19

What Advice Would You Give Your 20-year-old Self?

If you could go back in time, what advice would you give your 20-year-old self?

ADONIS SIMO profile image
Python/Js developer. Learning GoLang