For further actions, you may consider blocking this person and/or reporting abuse
Read next
Top 10 JavaScript Frameworks to Use in 2024: An In-Depth Guide
Gladiators Battle -
Setting Up and Exploring Django's Admin Panel
Mr #1738 -
Building a Kanban Board with Next.js,Vercel AI and Tolgee
Arindam Majumder -
New Voice Command System Tackles Variable-Length Speech for Improved Live Transcription
Mike Young -
Top comments (3)
I've been a professional developer for 26 years, working for many different companies, freelancing, hiring my own teams, etc. and... to be perfectly honest, a portfolio website is not really necessary for a developer. An interesting and active GitHub (or similar) account is a far better way to judge someone's skills/competency than a curated vanity project. The honest 'warts and all' approach is way better
Portfolio websites are optional now because we can just use a GitHub readme page for a portfolio. An active GitHub with lots of projects and code should more than suffice.
Showing backend skills is super easy. Just create a backend API using some sort of tech stack like JavaScript and Python. Hook it up to a database and put it inside of a Docker container and boom! You are showcasing your ability to develop backend architectures.
Yes and no.
Yes, because you're creating your online presence and can link some communities or professional profiles (even github) to show your work.
No, because if you main development area is backend, show rainbows or dancing cats don't add anything new to your resume or skills.
As backender you could link some github repositories where your worked or tried to connect some API with a own wrapper library (ie: Wikipedia API o Pokemon API?) to show how you work with them and answer questions in StackOverflow sometimes is a plus...