6
4 Comments

Working on a blog post - need developer advice

I'm working on developer blog post that lists tips and tricks in regards to pull requests, and how to squeeze more benefits out of them.

Here it is so far: https://dogger.io/blog/getting-the-most-out-of-your-pull-requests

Do you guys have any suggestions on what to add to the list? Do you know of any cool GitHub apps or similar that enhances the pull request experience, or perhaps just some cool neat tricks?

Edit: I want to make it clear that the list is far from complete. I want to make it into a huge list of resources that are available to everyone. Right now, my own product stands out, but that's not what I want the end result to be like.

on August 29, 2020
  1. 1

    This reads pretty clearly like a thinly veiled attempt at talking about the service you're offering, there really isn't much about getting the most out of pull requests. If you want to talk about your service, just say it and make the article about how your service can make working with pull requests better.

    1. 1

      Maybe it wasn't clear: The blog post is far from done. I plan on turning it into a huge list of resources for everyone to use. That's the whole point. Of course it is thin right now.

      What stands out is obviously my own product, but that's not what I want the end result to be. I want the blog post to be helpful, which is why I asked for help and ideas to add to the list.

      It seems to be like you're just saying what has already been stated, without helping me constructively.

      Do you have any ideas for things to add on the list that would make the list larger?

      1. 1

        No, sorry, I don't. Personally, I think this blog post should probably just stick to how your product should be used. I believe developer advice should come from a place of experience. Since you're outsourcing ideas for the post here, maybe the blog post you want to right just isn't the right one. You can search google and add a ton of stuff to the list, but can you stand by the claim that it helps one get the most out of their pull requests without seriously using it? IMO, probably not. Stick to what you know, it makes better content. Good luck.

        1. 1

          I have a lot of ideas myself that have not been added to the list. With 15 years of experience, it's not like I don't know a few things.

          What I was hoping for was a friendly and welcoming community that would gladly help making a list of things to add. I thought that could maybe be fun, hearing from other people.

          But perhaps I should have fully completed the list from my own ideas first to avoid redundant suggestions. That's good advice. I didn't think that one through.

          I already have a blog post about my product. I'm looking to build some SEO value and potentially help a few people along the way. I don't really see how that was worthy of such a negative response.