Daily Update @DevOpsMetricsHQ

- finished public roadmap setup
- defined pricing packages
- wrote some tickets to implement basic subscription management

#buildinpublic

Daily Update @DevOpsMetricsHQ

- fiddled around with Upvoty for a public roadmap

#buildinpublic

Currently in the process of setting up @upvoty for a public roadmap. Whenever I onboard a new product, I keep a close eye on flows, communication, and UX. Learning for free.

#buildinpublic

Daily Update @DevOpsMetricsHQ

- decided on @upvoty as a public roadmap tool
- decided on @PaddleHQ as the payment provider
- removed two tickets which I will not do for the public beta

Weekend, so that's it. 😅

#buildinpublic

Daily Update @DevOpsMetricsHQ

- fixed edge case data bug from Wednesday
- added support for master to main branch renaming
- added arrows to trend badge components
- Mastermind group weekly

Also, client work. So, that's it for today.

#buildinpublic

Looks like mid of May, the public beta will start.

#buildinpublic

Daily Update @DevOpsMetricsHQ

- added bot detection for all interactions in pull requests
- refactored cycle time calculations
- discovered an edge case data bug
- a lot of smaller tasks for launching the public beta

#buildinginpublic #buildinpublic

Daily Update @DevOpsMetricsHQ

- added feature pr tag
- added maintenance pr tag
- added all pr tags to filter in the frontend
- sent a weekly report manually via email (testing a new feature idea)

#buildinginpublic #buildinpublic

How do I tell my users that I forgot to multiply with -1.0 in some trend calculations because I thought this code was so obvious that I didn't need a test... 😅

#buildinpublic

Random Friday thought: I cut more features and can offer a public beta of @DevOpsMetricsHQ in the next two weeks. I showcase what's possible on a public roadmap. You vote, and everything else will be developed by the feedback from early customers and you.

#buildinpublic

Now that I have actual database costs let's set up payment. 🤣

At least I know now where AWS has its margins.

#buildinpublic

Also, such fuck ups always happen after I sent out an update to the early users with new features yesterday evening.

#buildinpublic

Scaling the database instance of @DevOpsMetricsHQ

#buildinpublic

I got comfortable hopping on video calls with random people and doing cold outreach.

#buildinpublic

Some of you asked me what my plan with @DevOpsMetricsHQ is: I am in private beta with early adopters.🤗

Due to some life-changing events and the war, I had a dip in productivity Jan to Mar.

A #buildinpublic update will come. My priority is on private -> public beta currently.

☝️💡 I need your help: I am working on a new feature for @DevOpsMetricsHQ

Depending on some characteristics, pull requests are classified. Enables better analytics and overview.

How would you name such a feature from a UX perspective?

#buildinpublic #buildinginpublic

☝️💡 I need your help: I am working on a new feature for @DevOpsMetricsHQ - Depending on some characteristics, PRs are classified. Enables better analytics and overview.

How would you name this feature from a UX perspective?

#buildinpublic #buildinginpublic

Back to println debugging

#buildinpublic

My strategy to keep some sanity in these times: developing baking skills.

Call me, Senior Cake Developer 👨‍🍳

#buildinpublic #bakeinpublic

User requests are changing my roadmap. You want that!

Today I also sketched a nice feature in a call with a user together. Always nice when I propose sth, and then the response is, 'ya, this would work for us'.

Cutting scope successfully. 😅

#buildinpublic