Thanks for sharing your perspective. Another big issue is i18n in SSR, but that's for another discussion :)

@tomaszgil.me Out of your experience, how do you feel about the "rule of thumb" of abstracting text in an i18n way even for unilanguage apps? Of course, it depends on the scale (e.g., I wouldn't do that for my personal blog), but in general, how does this sound to you?

Thanks for feedback Tomasz, appreciated! 🙏

I believe this becomes particularly noticeable when working with a 3rd party translator. This is the point when you realize how it can reduce the effectiveness of the whole workflow. In such cases, concatenated strings are likely to result in bug tickets.

Do you have it deployed somewhere or is it just local for now?

I would like more people to learn that Sometimes You Need to Save Even Valid Criticism for Later When Your House is Literally Burning Down

For quite some time I was looking for a solution to improve my personal project’s productivity. I was reluctant to try all those corporate-targeted apps as they felt to complex for my needs. However, after your recommendation I’ll give it a try. Thank you 😊

Thank you!

I'm considering a modular (or "composable") approach to create feature variants without needing an API to customize every potential scenario, which would become a maintenance nightmare.

Thank you for the article. It was delightful to read!

I finally managed to read the article, and it actually fits my current challenges. While gathering new requirements for the piece of the app I own, I've noticed that if we keep making it generic like we do now, we'll end up with a legacy-like spaghetti code despite the fact it has just 18 months.

Sounds cool! By join you mean sharing the posts/articles we discussed or some dev work as well? Is this something we can discuss on your Discord?

Thank you! I've already done that to some extent. I'm curious about how one develops into a regular contributor. Does it happen organically through consistent contributions, or should I proactively reach out to the maintainers? Perhaps it's a combination of both? Sorry for these basic questions! 😅

💡 Looking ahead, I foresee the evolution of frontend developers into technical user experience advocates, actively shaping product discovery, design, implementation, and performance strategies.

Let me know If you'd be interested in a post on how to approach these exams efficiently 🙌

➡️ Delving into AWS has broadened my understanding of software engineering, highlighting the importance of a more comprehensive approach in our roles as developers.

➡️ Certifications serve mainly as important milestones, delineating specific knowledge boundaries and guiding our learning paths.

➡️ Nowadays, "just building working #React components" is no longer sufficient for career growth. A deeper understanding of general infrastructure aspects, including cloud services like AWS, is becoming increasingly essential.

➡️ As frontend developers, we often underestimate the extent to which we interact with cloud services on a daily basis. Services like S3, CloudFront, EC2, Route53, ECR/ECS, are impacting our work more than we realize. More so, many 3rd party services we use are built on top of AWS.

Thanks you so much! Saving this one to read on the weekend.

Thanks! Just Astro with some simple vanilla JS for theme and animation.

Good luck 🤞 my blog for now is framework free but I plan to play with islands as well. Let’s see where it takes us.