DEV Community: Ivole32

Recap Sunday #4: Core Development & Open Sourcing RedisBrowse

Ivole32 — Sun, 28 Jun 2026 21:08:16 +0000

Welcome to the fourth edition of Recap Sunday, our weekly series where we share what happened behind the scenes at QueueForge during the previous week.

This week our primary focus was continuing development of the QueueForge core queue service. We spent most of our time improving the foundation of the platform and preparing it for future functionality.

Alongside our work on QueueForge, we also decided to release one of our internal developer tools as an open source project. The tool is called RedisBrowse.

RedisBrowse was originally built to help us inspect Redis keys and debug Redis Streams during development. Having a dedicated tool made it easier to understand queue state and troubleshoot issues while working on QueueForge.

We believe the tool can also be useful for other developers working with Redis, which is why we decided to make it publicly available.

This is only the beginning for RedisBrowse. We plan to continue expanding it with additional functionality, including the ability to modify data directly and other features that simplify working with Redis during development.

Looking beyond RedisBrowse, we also plan to open source more of the internal developer tools we build while developing QueueForge. Many of these tools solve common development problems, and we hope they can be useful to the wider developer community as well.

Highlights of the Week

Continued development of the QueueForge core queue service.
Open sourced our internal developer tool, RedisBrowse.
Released a tool for inspecting Redis keys and Redis Streams.
Began planning additional functionality for RedisBrowse.
Started preparing more internal developer tools for future open source releases.

Looking Ahead

Next week we plan to continue development of the QueueForge core queue service while also making further improvements to RedisBrowse based on our own development workflow.

We also expect to continue identifying internal tools that could be useful as open source projects and share them with the community over time.

See you next week,

The QueueForge Team

Stats Saturday #4: Website Traffic, SEO Progress & Development Stats

Ivole32 — Sat, 27 Jun 2026 21:51:53 +0000

Welcome back to another Stats Saturday. Every week, we share our progress, the numbers behind QueueForge, and what we're currently focusing on.

Website Stats

This week was relatively stable compared to the previous one. While we didn't experience a major traffic spike, we're happy to see consistent growth in the areas that matter most for the long term.

Here are this week's website statistics:

18 unique visitors (+28.6%)
19 total visits
37 page views (+32.1%)
1.9 pages per visit
57.9% bounce rate (-13.2%)
Average visit duration: 37 seconds

The biggest highlight continues to be SEO. After fixing the indexing issue a few weeks ago, Google is steadily discovering more of our content.

Google Search Console still shows relatively small numbers, but the trend keeps moving in the right direction. Over the last few months we've received 20 clicks from Google Search with 549 impressions , a 3.6% click-through rate , and an average ranking position of 17.3.

Those numbers may still look modest, but for a young project they're a great sign. SEO takes time, and seeing Google gradually send more visitors confirms that the work we've been putting into our content is starting to pay off.

Development

Development continued throughout the week with bug fixes, improvements, and preparations for upcoming features. We also open-sourced one of our internal projects to give something back to the developer community.

We'll publish a dedicated blog post soon explaining why we decided to open source it, what it does, and how you can use it yourself. If you don't want to miss that article, make sure to subscribe to our newsletter.

Productivity

This week wasn't our best when it came to screen time.

We spent approximately 25 hours on TikTok and another 6 hours on Instagram. That's significantly more than we'd like and a noticeable step backwards compared to previous weeks.

While it's frustrating to see those numbers increase again, we believe it's important to be transparent about both progress and setbacks. Building better habits isn't a straight line, and this week reminded us that consistency is something we still need to improve.

Our goal for next week is simple: spend less time scrolling and more time building QueueForge.

Other Stats

Lines of code committed: ~1,145
One internal project open sourced
Money spent: €0

Overall, we're happy with the direction QueueForge is moving in. SEO continues to improve, we're shipping new code every week, and we're excited to share more details about our open-source project soon.

Thanks for following our journey. If you'd like to receive future Stats Saturday updates and be the first to read about our upcoming open-source release, consider subscribing to our newsletter.

Recap Sunday #3: Infrastructure, Progress & Product Decisions

Ivole32 — Sun, 21 Jun 2026 19:48:36 +0000

Welcome to the third edition of Recap Sunday, our weekly series where we share what happened behind the scenes at QueueForge during the previous week.

This week was a little different from the last few. While we continued working on QueueForge, much of our focus was directed toward improving the foundation that the platform runs on.

During the first part of the week, we spent a significant amount of time migrating QueueForge to new servers. Infrastructure work is not always the most visible part of building a product, but it is essential for ensuring long-term reliability, scalability, and performance.

Since this migration came with a number of challenges, we decided to share some of the lessons we learned along the way. You can read the full breakdown here.

Beyond the migration, development of the core QueueForge product continued throughout the week. Rather than focusing exclusively on new features, we spent time evaluating different approaches, refining existing ideas, and discussing the overall direction of the platform.

Several important design and product decisions were made during these discussions. These decisions will influence how future features are implemented and help us keep QueueForge focused on solving real operational challenges for teams working with message queues.

Overall, this week was about strengthening both the technical foundation and the long-term vision of QueueForge.

Highlights of the Week

Migrated QueueForge infrastructure to new servers.
Improved the platform's foundation for future growth.
Continued development of the core product.
Made several important design and product decisions.
Prepared groundwork for future improvements and features.

Looking Ahead

Next week we plan to continue building on the work completed during the migration and begin turning some of this week's decisions into actual implementation work.

With much of the infrastructure work completed, we can spend more time focusing on the user experience and the next stage of QueueForge's development.

We are excited about the progress being made and look forward to sharing more updates soon.

See you next week,

The QueueForge Team

Stats Saturday #3: Website Traffic, Productivity & Development Stats

Ivole32 — Sat, 20 Jun 2026 17:21:44 +0000

Welcome to the next edition of Stats Saturday. Every week, we share a few numbers from our work, the habits that help us make progress, and the things that slowed us down.

Website Stats

This week's stats were not significantly better than the previous weeks. However, we're starting to see a clear direction for our marketing efforts, especially when it comes to SEO.

Here are the results:

Unique visitors decreased by 6%
Bounce rate increased by 28%
Average visit duration increased by 115%

One positive development is that we fixed a technical issue that prevented some of our blog posts from being indexed correctly by Google. Since deploying the fix, we're starting to see encouraging signs in Google Search Console and believe this could have a positive impact on our traffic over the coming weeks.

While the overall numbers are still below where we want them to be, seeing an upward trend in search visibility is motivating and confirms that our SEO efforts are beginning to pay off.

What about our TikTok challenge?

TikTok remains one of our biggest productivity challenges, but we're continuing to make progress.

This week, we spent 16 hours on TikTok. While that's still much more than we'd like, it's another improvement compared to previous weeks and brings us closer to our goal.

Reducing our screen time is a gradual process, but the trend is moving in the right direction. Our goal for next week is to continue building on this progress and get even closer to the target we've set for ourselves.

Other Stats

Besides traffic and productivity metrics, here are a few additional numbers from this week:

Lines of code committed: ~1160
Money spent: €0
Purchases considered but not made: €0

We'll share another update next Saturday.

Website Downtime in the Past Days

Ivole32 — Wed, 17 Jun 2026 17:52:01 +0000

Today we want to talk about the downtime and errors some users may have experienced while visiting our marketing website during the past two days. We would like to explain what happened, how we fixed it, and what we learned from the experience.

During the last two days, we migrated our marketing website to our new Hetzner servers, as announced in Future Friday #2: New Servers. While carrying out the migration, we made a few mistakes that resulted in temporary issues on the website.

The migration was divided into two parts. First, we set up the new infrastructure. Second, we migrated all required data from the old database. The main problems occurred during the infrastructure setup.

We encountered issues with communication between Docker containers. Unfortunately, it took longer than expected to identify the cause because we were troubleshooting late at night. After investigating several possibilities, we discovered that the problem was a small configuration mistake.

A missing allowed host entry caused backend API requests to fail whenever the frontend attempted to communicate with the backend. While the fix itself was simple, finding the exact source of the problem was difficult because the relevant configuration was spread across multiple files and locations.

We also ran into a few smaller issues. One example was an incorrect file permission that prevented the QueueForge logo from loading correctly. There were also several other minor configuration errors that needed to be resolved during the migration process.

Although the marketing website is not our main product, we take reliability seriously. Every issue is an opportunity to improve our processes and infrastructure. We want to learn these lessons now so we can provide a stable and reliable experience when we launch our first product.

What We Learned

Test infrastructure changes in a dedicated environment before deployment.
Keep configuration files organized and well documented.
Create deployment checklists for recurring tasks.
Verify file permissions as part of every migration.
Improve monitoring and error reporting to detect issues faster.

While no migration goes perfectly, every challenge helps us improve. We appreciate your patience and understanding while we continue building a reliable platform.

The QueueForge Team

QueueForge Is Taking a Break

Ivole32 — Tue, 09 Jun 2026 14:00:00 +0000

This week will be a little different from usual.

The QueueForge team is taking a short break and spending some time away from development. Over the past months, a significant amount of time has gone into building the platform, planning new features, improving infrastructure, and preparing for future growth.

While we enjoy working on QueueForge, we also believe that taking time off is important for maintaining a healthy balance and returning with fresh ideas and motivation.

Because of this, regular development activities will be paused for most of the week. New features, larger infrastructure projects, and long term planning tasks will continue once the team returns.

That does not mean QueueForge is completely unattended. We will continue monitoring our systems and will remain available for important support requests.

In addition, if critical bugs, stability issues, or security related problems are identified, we will continue to deploy patches when necessary. Keeping the platform reliable remains a priority, even during periods where active development is reduced.

This short break also gives us an opportunity to step back and review our plans for the coming months. Sometimes taking a pause is the best way to return with a clearer perspective on what should come next.

We appreciate everyone who continues to follow our journey and support QueueForge while we build the platform.

What Will Continue This Week

Monitoring of platform infrastructure and services.
Handling important support requests.
Deploying critical bug fixes when required.
Deploying security related patches when necessary.
Planning improvements for after the break.

Looking Ahead

Regular development is expected to resume next week. Once we are back, we will continue working on infrastructure improvements, platform development, and the projects currently on our roadmap.

Until then, QueueForge will remain online, monitored, and maintained while the team takes a short break.

See you soon,

The QueueForge Team

Security Monday #1: Securing Our New Server Infrastructure

Ivole32 — Mon, 08 Jun 2026 13:30:00 +0000

Welcome to the first edition of Security Monday, a new series from the QueueForge Security Team where we share updates about infrastructure security, operational security, monitoring, and the processes we use to protect our platform.

Security is not something that can be added at the end of a project. It has to be part of the entire development and operations process. With this series, we want to provide insights into the work that happens behind the scenes to keep QueueForge secure and reliable.

As announced in Future Friday #2, we recently deployed new servers that will become an important part of our future infrastructure.

While these systems provide additional capacity and flexibility, deploying new infrastructure is only the first step. A significant part of our current work focuses on securing these systems before they take on production workloads.

We are currently performing extensive hardening of the new servers. This includes reviewing system configurations, reducing unnecessary attack surface, improving access controls, and establishing security baselines that can be applied consistently across the infrastructure.

To support this process, we are using industry recognized standards such as the CIS Benchmarks while also applying our own experience and internal security requirements.

In parallel, we are working on a broader security improvement plan for QueueForge. The goal is to strengthen the security of our existing website and internal services while preparing them for migration to the new infrastructure.

This work includes improving monitoring capabilities, reviewing existing configurations, evaluating operational procedures, and identifying areas where additional safeguards can be introduced.

We are also introducing new internal security standards. One example is a structured audit process that will include regular monthly security reviews. These reviews will help us identify weaknesses earlier, verify that security controls remain effective, and ensure that security remains an ongoing process rather than a one time task.

While much of this work is not directly visible to users, it forms an important part of building a reliable platform that can continue to grow over time.

Highlights of the Week

Started hardening the new server infrastructure.
Applied security guidance based on CIS Benchmarks and internal requirements.
Created a plan for improving the security of existing services.
Reviewed monitoring and operational security processes.
Introduced plans for monthly security audits and reviews.

Looking Ahead

Over the coming weeks, we will continue hardening the new infrastructure and begin transferring security improvements to existing systems and services.

Future editions of Security Monday will cover additional topics related to infrastructure security, monitoring, operational security, and the lessons we learn while building QueueForge.

See you next Monday,

The QueueForge Security Team

Recap Sunday #2: Doing Nothing Can Be Healthy Too

Ivole32 — Sun, 07 Jun 2026 13:00:00 +0000

Welcome to the second edition of Recap Sunday, our weekly series where we share what happened behind the scenes at QueueForge during the previous week.

This week was different from most weeks. Instead of focusing heavily on development, planning, or marketing, we decided to take things a little slower.

Over the past months, QueueForge has become a large part of our daily lives. While we enjoy building it, we also know that constantly working without breaks is not sustainable.

Because of that, we spent more time with friends, enjoyed activities outside of development, and allowed ourselves to step away from our computers for a while.

As a result, there is not a long list of new features or technical updates to share this week, and that is completely fine.

We believe that taking breaks is an important part of any long term project. Sometimes the best thing you can do for productivity is to stop working for a moment and come back with a fresh perspective.

While QueueForge remained in our minds, this week was mostly about recharging and maintaining a healthy balance between work and personal life.

Highlights of the Week

Spent more time with friends and family.
Took a short break from intensive development work.
Focused on maintaining a healthy work life balance.
Reflected on future plans for QueueForge.
Returned with fresh motivation for the coming weeks.

Looking Ahead

Next week will probably be similar. We will be traveling for part of the week, which means development will continue at a slower pace than usual.

While we may not spend as much time working on QueueForge, we believe it is important to occasionally step away from a project and return with a clear mind.

We will likely share more about our trip in a separate blog post, so stay tuned for that.

Sometimes progress means moving fast, and sometimes it means taking a break. This week was the second kind, and next week will probably be as well.

See you next week,

The QueueForge Team

Stats Saturday #2: Website Traffic, Productivity & Development Stats

Ivole32 — Sat, 06 Jun 2026 15:00:00 +0000

Welcome to the next edition of Stats Saturday. Every week, we share a few numbers from our work, the habits that help us make progress, and the things that slowed us down.

Website Stats

We want to start by sharing some statistics from our marketing website, even though the results this week were disappointing. Transparency is important to us, and we also want to explain what we believe caused these numbers.

Here are the results:

Unique visitors decreased by 82%
Bounce rate increased by 4%
Average visit duration decreased by 65%

These numbers are clearly not where we want them to be. Here's what we think caused the decline and how we plan to improve.

Problems and Solutions

The biggest issue was inactivity. Our blog and social media channels received very little attention last week because we were focused on other tasks and simply neglected them.

Another challenge was losing access to our X account. We were suspended after sharing our landing page in several replies. We are currently in contact with support and hope to regain access soon, as X has been one of our main sources of website traffic.

Our goal for the coming week is to return to a consistent publishing schedule for both our blog and social media channels.

TikTok Again?

Unfortunately, TikTok continues to be a problem.

This week, we spent a total of 18 hours on TikTok. While this is an improvement compared to last week, it is still far above what we consider acceptable.

We also failed to reach our goal. Last week, we spent 21 hours on TikTok and aimed to reduce that number by 14 hours. We made progress, but not enough.

Other Stats

Besides traffic and productivity metrics, here are a few additional numbers from this week:

Lines of code committed: ~317
Money spent: €0
Purchases considered but not made: €0

We'll share another update next Saturday.

Future Friday #2: New Servers and Security Improvements

Ivole32 — Fri, 29 May 2026 16:30:00 +0000

Future Friday #2: New Servers

During the last days we worked on an important part of the QueueForge infrastructure. QueueForge is currently preparing a move to a new and more local hosting provider.

The new infrastructure gives us more control over our systems, better long term planning and a stronger foundation for future development. At the moment the migration is still in progress and the main QueueForge services are continuing to run on the current infrastructure.

Alongside the infrastructure work we also redesigned parts of our security strategy. New internal rules, improved network structures and better separation between services are now part of the new setup.

Preparation for a new local server infrastructure
Improved internal security planning
Ongoing work on the future website migration
Better structure for future QueueForge products
Long term scalability and stability

More details about our security related work will be published soon in our upcoming Security Monday series.

Development of QueueForge continues alongside the infrastructure changes. We are actively working on ways to keep all QueueForge products secure while preparing the migration of additional services and websites to the new servers.

If you want to follow future updates, infrastructure changes and upcoming releases, you can subscribe to the QueueForge newsletter.

What comes next

Over the next weeks we will continue preparing the migration, improving internal tooling and building the next stage of QueueForge services on the new infrastructure.

Recap Sunday #1: Marketing Progress and Backend Design Updates

Ivole32 — Sun, 24 May 2026 22:08:09 +0000

Welcome to the first edition of Recap Sunday, our new weekly series where we look back at the progress, decisions, and milestones from the previous week at QueueForge.

QueueForge has been in development for quite some time, but this marks the beginning of a new way for us to share our journey and keep you updated on what happens behind the scenes.

This week, our primary focus was on marketing and finding effective ways to introduce QueueForge to a wider audience.

To support this goal, we started implementing a structured content strategy across our social media channels and this blog.

As part of this initiative, you may have already noticed new content series such as Future Friday. Several additional formats are currently in development and will be introduced over the coming weeks.

The initial results have been encouraging. We have already seen positive changes in our analytics, reinforcing our decision to consistently share updates, insights, and behind-the-scenes content about QueueForge.

Although marketing was our primary focus this week, development continued as well. We implemented additional functionality for the core queue management system and finalized several important architectural decisions that will help us build a scalable and maintainable platform moving forward.

One of the biggest topics this week was refining how different components of the backend should communicate with each other. While much of this work is not directly visible to users, these decisions are critical for ensuring reliability, performance, and future scalability.

Highlights of the Week

Created and started executing a structured content marketing plan.
Launched the new Future Friday content series.
Observed positive engagement and growth across our channels.
Implemented additional backend functionality for queue management.
Finalized key architectural decisions for future scalability.

Looking Ahead

Next week, we plan to continue expanding our content efforts, introduce additional recurring content formats, and further develop the core QueueForge platform.

We are excited about the progress we are making and look forward to sharing more updates with you in the next edition of Recap Sunday.

See you next week,

The QueueForge Team

Stats Saturday #1: How Endless Scrolling Steals Our Time

Ivole32 — Sat, 23 May 2026 18:30:00 +0000

Welcome to the first edition of Stats Saturday. Every week we will share a few numbers from our work, the habits that helped us move forward and the things that slowed us down.

The goal is simple. By making our progress public, we want to stay accountable and continuously improve. Some weeks will look better than others, but we believe that tracking the right metrics is one of the easiest ways to identify what works and what needs attention.

How TikTok reduces our productivity

We have to admit something: we spend too much time on TikTok.

This week alone, our total screen time on TikTok reached 21 hours. That is almost an entire day spent scrolling through short videos. While entertainment and breaks are important, this amount of time clearly comes at the expense of other activities.

Those 21 hours could have been used for writing content, improving QueueForge, learning new skills or simply taking proper breaks away from a screen. Instead, much of that time disappeared into endless scrolling.

To reduce this number, we are setting a goal for next week: spend at least 14 fewer hours on TikTok. Public accountability can be a strong motivator, so we will publish our scrolling time every week in Stats Saturday and track whether we are making progress.

The objective is not to completely stop using social media. We simply want to be more intentional with our time and avoid opening an app out of habit.

Website statistics

Using our analytics platform GhostlyX, we were able to review how our recent content strategy performed.

One encouraging result is that posting consistently appears to be working. During the last seven days, the website received 13 unique visitors, representing growth of 116.7 percent compared to the previous period.

If you are reading this article on our official blog, you are part of those statistics.

Another positive metric is the bounce rate, which decreased by 22.8 percent. In practical terms, visitors are exploring more pages instead of leaving immediately after opening the first one.

However, not every number moved in the right direction. The average visit duration dropped by 55.1 percent and now stands at only 22 seconds. This suggests that while more people are discovering the site, the content is not yet keeping their attention for as long as we would like.

Over the coming weeks we will experiment with longer articles, clearer calls to action and more useful content to increase engagement and encourage visitors to spend more time on the website.

Other stats

Besides traffic and productivity metrics, here are a few additional numbers from this week:

Lines of code committed: ~500
Money spent: €0
Purchases we almost made: €9

Looking ahead

Our focus for next week is straightforward:

Reduce TikTok usage by at least 14 hours
Continue publishing content consistently
Increase average visit duration
Maintain growth in website traffic

We will share the results in the next edition of Stats Saturday. If you would like to follow our progress, consider subscribing to the newsletter and checking back next week.