Skip to main content
DevHivesBlog

Search the blog

Find a post by title, tag or topic

FAQ

Last updated

Two overlapping speech bubbles, the larger one containing a question mark — DevHives Blog FAQ page illustration

Common questions from readers. If yours isn’t here, write to us at khanp4397@gmail.com.

How often do you publish?

Roughly every three or four days. The cadence matters less than the standard: we’d rather miss a slot than ship something half-formed, and we never publish to fill a gap.

Can I get notified when a new post is published?

We don’t have a newsletter yet. The RSS feed at devhives.in/blog/feed/ works in any feed reader, and each category has its own feed too — add feed/ to any category URL to follow just that topic.

Can I republish your posts?

Code samples in our posts are MIT-licensed — copy, adapt, ship. For the prose itself: quoting with attribution and a link back is fine; republishing a full post is not. Drop us an email if you have a specific case in mind.

Do you take guest posts?

Not at the moment. Every post on this blog is written by a DevHives instructor so the voice and accountability stay consistent.

Do you do consulting or 1-on-1 mentoring?

Our 1-on-1 work happens inside the DevHives course programmes. We’re not currently offering standalone mentoring or paid consulting through the blog.

I have a topic I’d really like you to cover.

Please tell us. We maintain an open topic list — reader requests carry real weight in what we write next. Email us with the topic and (if you can) what about it has tripped you up.

Is this blog the same thing as your training programme?

No — they’re related but separate. The blog is free and open to everyone. The training programme is paid, includes placement support, and is what we built first. If you want to know more, head to devhives.in.

How do I get my comment approved?

Be substantive (questions, disagreements, corrections — all great), be civil, and don’t link-spam. We approve manually, usually within a day. See the Editorial Policy for the full comment moderation approach.