Hm, for my new booklet ideas I haven't done any of this yet. For my first book though, I'd say I covered most of things to some degree, but none of it quite sticks.
For example, there are lots of books on general job advice, mine is specific for devs. There are plenty on technical interviews, mine covers the whole process and favors strategy instead of coding questions. People here on dev.to for example obsess about portfolios which I've got a chapter on and articles here and there as well.
I have a mailing list with engaged folk, but it doesn't grow. What it comes down to, I think, is some of my stuff could be refined to be more targeted, but I suspect I don't have a good outreach or way to attract people to me. Social media doesn't seem to work really well yet, and I get a trickle of people interested here despite having close to 2k followers.
Anyway, something is missing. I try not to get down on myself about it, more to learn and practice. The booklets were another try and way to apply some of my energy.
🇩🇴 I'm a Technical Program Manager and Content Strategist with an MSc in UXD. I help developers become better content creators and DevRel teams build robust content programs.
Gotcha! The reason I asked about the market research is cos I came across a similar title earlier this year: De-Coding the Technical Interview. I've seen at least one more on Twitter re: resumes for devs; don't recall the author. I did research prior to announcing both my eBooks just to get a sense of what was out there.
I just checked out your blog and you publish regularly (which is awesome!). Re: newsletter signups, a few comments: I hypothesize that the CTA you're using for the newsletter sign up on your site ("Join Now!") may not be clear enough to visitors; what are they "joining"? Common CTAs for newsletters are "Sign up" and "Subscribe", with the latter being the most correlated to newsletter signup activity (it may be worth running an A/B test on this). The good news is you have an engaged list, so there's probably ways you can ask your list for feedback on some of your ideas or just to understand their pain points. That way you'll be able to deliver something you know your target audience really wants or really needs.
I'll stop there, but I hope you keep going! It's a lot of trial and error but if you can find a way to make experimenting with different approaches fun it makes it easier to stick through it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hm, for my new booklet ideas I haven't done any of this yet. For my first book though, I'd say I covered most of things to some degree, but none of it quite sticks.
For example, there are lots of books on general job advice, mine is specific for devs. There are plenty on technical interviews, mine covers the whole process and favors strategy instead of coding questions. People here on dev.to for example obsess about portfolios which I've got a chapter on and articles here and there as well.
I have a mailing list with engaged folk, but it doesn't grow. What it comes down to, I think, is some of my stuff could be refined to be more targeted, but I suspect I don't have a good outreach or way to attract people to me. Social media doesn't seem to work really well yet, and I get a trickle of people interested here despite having close to 2k followers.
Anyway, something is missing. I try not to get down on myself about it, more to learn and practice. The booklets were another try and way to apply some of my energy.
Gotcha! The reason I asked about the market research is cos I came across a similar title earlier this year: De-Coding the Technical Interview. I've seen at least one more on Twitter re: resumes for devs; don't recall the author. I did research prior to announcing both my eBooks just to get a sense of what was out there.
I just checked out your blog and you publish regularly (which is awesome!). Re: newsletter signups, a few comments: I hypothesize that the CTA you're using for the newsletter sign up on your site ("Join Now!") may not be clear enough to visitors; what are they "joining"? Common CTAs for newsletters are "Sign up" and "Subscribe", with the latter being the most correlated to newsletter signup activity (it may be worth running an A/B test on this). The good news is you have an engaged list, so there's probably ways you can ask your list for feedback on some of your ideas or just to understand their pain points. That way you'll be able to deliver something you know your target audience really wants or really needs.
I'll stop there, but I hope you keep going! It's a lot of trial and error but if you can find a way to make experimenting with different approaches fun it makes it easier to stick through it.