Hi, > This was not a poor accident by a single employee. It's noble that the author tries to take all the blame on himself, but honestly, I feel like that is a

Hi, > This was not a poor accident by a single employee. It's noble that the author tries to take all the blame on himself, but honestly, I feel like that is a moment where a leader has to step in and accept their mistake and not let a small trooper eat all the bullets. The issues you have found are all assigned to me, or I created them. My task is to create blog posts, some of which being a hackathon and challenge. The KPI are impressions, other metrics are hard to measure. As a Developer Evangelist, I often need to learn new technologies, or dive into unknown areas connecting the dots. You can learn more about our focus areas in our handbook: https://about.gitlab.com/handbook/marketing/community-relations/developer-evangelism/ https://about.gitlab.com/handbook/marketing/community-relati... I'm focussing on the Ops side, with a backend development background in the past 15 years. I was once a maintainer of an OSS monitoring project called Icinga, a Nagios fork back then. I decided to take on a new journey with becoming a Developer Evangelist in March 2020 (you can learn more on my website https://dnsmichi.at/about/ https://dnsmichi.at/about/ in case you're interested). That being said, I've found it interesting to learn about web apps and their deployment, and dive into new things. Never having found a use case for trying Heroku, March brought up one: There was a Twitter theme of "Everyone is building a better Heroku" - https://twitter.com/adamhjk/status/1369704730218299392?s=27 https://twitter.com/adamhjk/status/1369704730218299392?s=27 From there, I thought of learning Heroku while comparing it with the 5 minute production app. I underestimated the challenge of creating a web app with a persistent backend, and decided to stick with the simple battleships demo I had initially found. This state of the blog post felt good enough for me, and I did not include the persistent backend just yet, but moved it into a separate blog post. This is feedback I got during the review. Turns out that this decision was wrong, next to other negative raw sentiments I had added in the blog post. You can try to convince that it is not my fault, and I will convince you - it is, and I am standing up for it. Public and transparent. I know we all get better from making mistakes. The lesson I learned today helped me improve a talk I gave at a meetup in my evening, it added technical insights as well as helped with the story line. That's the tracking issue: https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/3754 https://gitlab.com/gitlab-com/marketing/corporate_marketing/... We will continue to iterate, and have a retrospective on what we can improve from the lessons learned today. Thanks for your feedback.