I've been brainstorming a new portfolio solution for myself over the last few days, something atypical when you think of the word portfolio. What I've come up with so far:
Leaning towards a one-pager, no thought given on HTML/CSS/JS frameworks yet.
Content is a combination of static and dynamic data. Dynamic data would be information from third-party services & insights that would have to be re-calculated every time new data is added.
Since some of this dynamic data might be large (ex: stock ticker analysis), worker tasks would be written to fetch this data and compile insights on a schedule, saving the new data to a db or redis for the website to quickly fetch.
Open Source source so my work can be reviewed for technical competency
Github Actions for CI and CD
Continuous delivery trigger on something like a release tag being added to a commit on the main trunk.
Likely will live in Digital Ocean or GCP
Localized for translation
In terms of dynamic data, some ideas I'm floating:
Pull in blog posts from dev.to
A "top 10 dividends" report which returns which stocks have the highest dividend yield.
Github data like the contribution graph (although today's looks far less impressive to my team lead days)
Insights around my cloud spend - What resources I'm using, how many domains have I registered, etc.
LinkedIn data
Career twitter insights, using current twitter data + prior archives
Clips from xbox
Health data like steps and workouts, maybe more to add transparency around cancer treatment.
Your portfolio sounds super impressive / comprehensive so I feel like the work would just speak for itself with a simple website builder (that wouldn't require your having to maintain it)? Every time I've tried to create a comprehensive CV, coded from scratch, I've regretted it lolol.
Here's my portfolio / cv site that I created with carrd.co: ria.run
:)
Hi Ria! Thanks for sharing your portfolio, you may have actually inspired me to look further into carrd and see if maybe I can just publish updates there.
Could I achieve what I'm looking for with something more simple? Absolutely. But the truth is that I don't need a portfolio to market myself either. My interest of late in publishing a portfolio was to use it as an exercise in implementing a background worker process. I've done a lot of SaaS feature work, but I never got around to background processes before I moved on from an individual contributor role.
Beyond wanting to scratch that itch, I'm all for KISS with the rest of the stack.
Oh man, that’s sick. What about it gives you that itch exactly? I’ve gotten a different itch lately —to get back to the tech side from this marketing role. Lol.
I'm coming up on 2 years since I moved from an IC role into management and I haven't had many consulting opportunities of late due to covid and cancer.
Now that we're getting beyond the pandemic and my health has stabilized, it's time to shake off the rust and get back to the hustle I had previously, scratching this itch is practice for invoicing someone else for a similar job
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
I run my blog/portfolio (nabeel.dev/nabeel.blog) site on DigitalOcean Kubernetes, with a few other sites. Most of the content is static, but there are some dynamic components that are pulled from a database:
Site is built in ASP.NET Core
I paid for a simple bootstrap-based HTML theme
Main pages are hand-crafted HTML
Blog posts are written in Markdown and "compiled" to HTML
Dynamic data is fetched by the C# code and returned to some simple JS code in the UI
I started on WordPress, then moved to Hugo for a while. Both are fine options, but I'm really enjoying my current setup. The advantaged that I see are:
The ability to use my favorite programming language.
Static and dynamic content are both really easy to do.
The education that comes with doing things from scratch.
It's really easy to experiment and add new features.
No more nginx/php-fpm/mysql, or messing with other people's code.
I'm not even sure if my current approach is harder or more time consuming overall. I may be starting at a lower layer than a CMS/SSG, but on the flip side I don't have to spend as much time trying to understand a complex system, its plugins, and dealing with the bugs and limitations that comes with all of that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've been brainstorming a new portfolio solution for myself over the last few days, something atypical when you think of the word portfolio. What I've come up with so far:
In terms of dynamic data, some ideas I'm floating:
Static Content I'm toying around with:
Your portfolio sounds super impressive / comprehensive so I feel like the work would just speak for itself with a simple website builder (that wouldn't require your having to maintain it)? Every time I've tried to create a comprehensive CV, coded from scratch, I've regretted it lolol.
Here's my portfolio / cv site that I created with carrd.co: ria.run
:)
ria.run looks amazing! congrats, I loved the experience (of browsing it).
I love yours too Ria. Was that a template? It's very beautiful...what tech stack did you use?
Check out carrd.co! I think it's probably the cleanest UI I've ever seen in a site builder. That anti-aliasing is on point! 👌
Love your microcopy under "Curriculum Vitae"
Hi Ria! Thanks for sharing your portfolio, you may have actually inspired me to look further into carrd and see if maybe I can just publish updates there.
Could I achieve what I'm looking for with something more simple? Absolutely. But the truth is that I don't need a portfolio to market myself either. My interest of late in publishing a portfolio was to use it as an exercise in implementing a background worker process. I've done a lot of SaaS feature work, but I never got around to background processes before I moved on from an individual contributor role.
Beyond wanting to scratch that itch, I'm all for KISS with the rest of the stack.
Oh man, that’s sick. What about it gives you that itch exactly? I’ve gotten a different itch lately —to get back to the tech side from this marketing role. Lol.
I'm coming up on 2 years since I moved from an IC role into management and I haven't had many consulting opportunities of late due to covid and cancer.
Now that we're getting beyond the pandemic and my health has stabilized, it's time to shake off the rust and get back to the hustle I had previously, scratching this itch is practice for invoicing someone else for a similar job
I enjoy that you're so chill about being inspiring AF.
This sounds like fantastic portfolio.
I run my blog/portfolio (nabeel.dev/nabeel.blog) site on DigitalOcean Kubernetes, with a few other sites. Most of the content is static, but there are some dynamic components that are pulled from a database:
I started on WordPress, then moved to Hugo for a while. Both are fine options, but I'm really enjoying my current setup. The advantaged that I see are:
I'm not even sure if my current approach is harder or more time consuming overall. I may be starting at a lower layer than a CMS/SSG, but on the flip side I don't have to spend as much time trying to understand a complex system, its plugins, and dealing with the bugs and limitations that comes with all of that.