3 ms·
Hi, I wrote the blog post last week, and decided to publish it on Monday. https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/77170#note_534558211 ht
by dnsmichi 6y ago
Hi, I wrote the blog post last week, and decided to publish it on Monday.
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/77170#note_534558211 https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...
The title was chosen poorly, and the blog post did not reflect on its intentions. For that, I deeply apologize.
The experience and first time with Heroku is my raw impression, also the fact that I am a backend developer who is learning frontend and web apps.
It is a hard lesson learned today, although I am here for it. Iterate and improve, listen to feedback, and learn.
Sytse helps with his expertise and vision on the 5 minute production app, responding here to help. He is not to blame at all, I truly appreciate his guidance and thoughtful responses.
- yayr 6y agothanks @dnsmichi for taking responsibility quickly. personally, I think competition is what drives the web tech forward and I appreciate the openness gitlab brings to both the technology and the process you are using. The blog post process you have linked demonstrates this very well. Btw, I dig your flame emoji :-D
- lambda_obrien 6y agoI hope they give you a nice bonus for trying to fall on the sword so honorably, but even if no one else read your post before you posted it then that's still a leadership failure, frankly.
- ZephyrBlu 6y agoI just want to say that I think most (If not all) of the vitriol is not directed towards you, but GitLab itself. A guy linked a bunch of GitLab tickets in another comment showing that you went through the proper process and had multiple other people approve the post, so I think there wasn't much else you could personally do.