Back from Prague – Fresh Perspective on Project Angmar

October 21, 2025

Another day, another blog post — and I apologize for the large gap between updates. I've been on an amazing vacation in Prague for the past few days, and during that time, I put Project Angmar on the shelf to simply enjoy the break.

It was a delightful and necessary disconnection from code, deadlines, and endless to-do lists. But more importantly, it gave me a fresh perspective on my project and where I want to take it next.

🌍 Why Taking Breaks Matters#

As developers, we often get caught in the trap of constant productivity. There's always one more feature to build, one more bug to fix, one more optimization to make. But stepping away — truly stepping away — can be just as valuable as the work itself.

Prague gave me that space. Walking through cobblestone streets, exploring historic architecture, and experiencing a different culture reminded me why I started this journey in the first place: to build things that matter, not just to build for the sake of building.

When you're deep in the code, it's easy to lose sight of the bigger picture. You start optimizing pixels, debating component structures, and obsessing over details that, honestly, most users will never notice. But when you step back, you see what actually matters:

• Is the site functional?
• Is it accessible?
• Does it tell my story?
• Does it showcase my work effectively?

The answer to most of these? Yes, but there's room for improvement.

📊 Current State – About 25% Complete#

So far, I've focused primarily on four main sections:

• Home – The landing page with hero, features, and CTAs
• About – Profile, tech stack, and timeline
• Blog – This very section you're reading
• Portfolio – Project showcase with case studies

I'd estimate these sections are about 25% complete. They're functional, they look decent, and they serve their purpose. But they're not finished. There's still polish to add, interactions to refine, and content to expand.

What's Working Well#

Let me start with the positives:

1. Design System – The theme system with the different colors palettes is solid. Light/dark mode works seamlessly, and the color tokens make it easy to maintain consistency.

2. i18n Implementation – The internationalization system is clean and scalable. Switching between Norwegian and English is smooth, and adding new languages would be straightforward.

3. Component Structure – The component architecture is logical and reusable. Motion components, layout components, and content components are well-separated.

4. Portfolio Showcase – The project cards look professional, and the case study pages provide good context for each project.

5. Blog System – MDX integration works well, and the blog layout is clean and readable.

What Needs Work#

Now for the areas that need attention:

1. Mobile Experience – While responsive, some components could be more touch-friendly and better optimized for smaller screens.

2. Performance – There's room for optimization in image loading, bundle size, and initial page load.

3. Content Depth – Some sections feel a bit sparse. More detailed case studies, more blog posts, and more personality would help.

4. Animations – The motion system is in place, but some interactions feel a bit generic. More thoughtful micro-interactions would elevate the experience.

5. Accessibility – While I've tried to follow best practices, a proper accessibility audit would likely reveal areas for improvement.

🚧 The Elephant in the Room – Contact & Resume#

If you've explored the site, you've probably noticed that two major sections are still quite empty:

• Contact – Placeholder content, no functional form yet
• Resume – Barely started

These are critical sections that I've been putting off, and it's time to address them.

The Resume Challenge#

The resume section is particularly interesting because I want to do it right. My vision is:

• Web-based CV – A beautiful, interactive resume that lives on the site
• PDF Export – The same content, formatted for print and download
• Dynamic Content – Easy to update without touching code
• Professional Layout – Clean, scannable, and ATS-friendly

This is more complex than just throwing together a PDF. I want the web version to be engaging and interactive, while the PDF version needs to be professional and printable. Finding that balance is the challenge.

I'm considering using a library like react-pdf or jsPDF to generate the PDF dynamically from the same data source. That way, I maintain a single source of truth and avoid the nightmare of keeping two versions in sync.

The Contact Form Dilemma#

The contact form is another beast. I need to decide:

• Backend solution – Do I use a service like Formspree, EmailJS, or build my own API route?
• Validation – Client-side, server-side, or both?
• Spam protection – reCAPTCHA, honeypot, or something else?
• Success handling – Toast notification, redirect, or inline message?

I'm leaning towards a simple API route with server-side validation and a honeypot for spam protection. Keep it simple, keep it functional.

🎯 What's Next?#

With a fresh perspective and renewed energy, here's what I'm prioritizing:

Short-term (Next 1-2 Weeks)#

1. Resume Section – Build the web-based CV with all relevant experience, skills, and education
2. PDF Generation – Implement downloadable/printable resume functionality
3. Contact Form – Create a functional contact form with proper validation
4. Mobile Polish – Improve touch targets, spacing, and interactions on mobile devices

Medium-term (Next Month)#

1. Performance Audit – Optimize images, reduce bundle size, improve loading times
2. Accessibility Review – Run automated tests and manual checks for WCAG compliance
3. Content Expansion – Write more blog posts, expand case studies, add more personality
4. Animation Refinement – Add thoughtful micro-interactions and improve existing animations

Long-term (Next Quarter)#

1. Advanced Features – Consider adding a newsletter, comment system, or project filtering
2. Analytics – Implement privacy-friendly analytics to understand user behavior
3. SEO Optimization – Improve meta tags, structured data, and search visibility
4. Continuous Improvement – Regular updates, new projects, and ongoing refinement

💭 Lessons from the Break#

Taking time away from the project taught me a few valuable lessons:

1. Perfection is the Enemy of Progress#

I've been holding back on launching certain sections because they're "not perfect yet". But perfect is a moving target. It's better to ship something functional and iterate than to endlessly polish in private.

2. User Perspective Matters#

When you're building, you see every flaw, every misaligned pixel, every suboptimal choice. But users don't. They see the overall experience. Stepping back helped me see the site through fresh eyes — and it's better than I thought.

3. Breaks Fuel Creativity#

Some of my best ideas came while walking through Prague, not while staring at code. The brain needs downtime to process, connect dots, and generate new ideas. Constant grinding isn't sustainable or productive.

4. Documentation is Future You's Best Friend#

Coming back after a break, I was grateful for the documentation I'd written. Clear comments, structured folders, and documented decisions made it easy to jump back in. Future me says thanks.

🚀 Moving Forward#

I'm excited to dive back into Project Angmar with fresh energy and clear priorities. The resume and contact sections are next on the list, followed by polish and optimization.

This project is a marathon, not a sprint. It's about building something I'm proud of, learning along the way, and creating a portfolio that truly represents my skills and personality.

Prague was amazing, but it's good to be back. Let's build something great.

Have you taken breaks from your projects? How do you balance productivity with rest? I'd love to hear your thoughts (once I implement that comment system... 😅)