Designers can create visual stuff and publish them on behnace and others, same for front end dev. But when you only know how to optimize databases, SQL queries, and API what should you add into a portfolio ?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (6)
System Designs and Design Patterns are in the new rage. You could write about your take on some system design issues. Challenge some existing norms, bring in your ideas there, how it can be improved.
And in case of design patterns, we find a lot of theory on the web. Code about it. Implement use cases to show off your design pattern strengths.
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:
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