Blogging my programming/discoveries

[VinylxScratches]

Hey guys,

I am asking for advice. I'd like to start a blog on stuff I do throughout work. A lot of the stuff I try to solve is not on the internet or is sprouted out there in pieces.

Would you think it's credible for myself to have a blog? If so, should I host it myself or just use a blogspot account?

I feel that if I host it myself, it's more credible?

A lot of my stuff is powershell and c#, but I also do bash and Linux stuff too....

What do you guys think?

 

[Markbnj]

Having a blog has worked out well for me. I set it up about five years ago when prospective employers began googling people to obtain information, and my goal was that when my name was entered into google my site was the first result. On it I mostly write about specific programming and general technology issues, and I have links to demo programs for Silverlight, jquery, and whatever else I've worked on. Having the site has figured positively in my last two hires.

As for hosting it yourself... if all you want is the space to write stuff in, then a blog account makes a lot of sense. If you want to be able to host files and demos, and have more control over server options and the database, then a hosting account makes sense. Mine costs me $12.95/month and it's more than worth it.

 

[DaveSimmons]

Just be careful not to post anything that your employer wants to keep confidential.

I've done a bit of work with Win32 that might interest people, but I can't really post about it because it would help existing and potential competitors. Even describing the problems without giving the solutions would be too helpful.

 

[Wyndru]

Just be careful not to post anything that your employer wants to keep confidential.

I've done a bit of work with Win32 that might interest people, but I can't really post about it because it would help existing and potential competitors. Even describing the problems without giving the solutions would be too helpful.

This. My current employer owns every bit of code we write. It sucks too, because I've written a lot of code that would help me throughout my career should I choose to leave, and I don't think I can bring the code with me legally.

 

[Markbnj]

This. My current employer owns every bit of code we write. It sucks too, because I've written a lot of code that would help me throughout my career should I choose to leave, and I don't think I can bring the code with me legally.

I am almost never in the position where I can't blog about an algorithm or technique, but I always rewrite the code to both isolate the point of interest, as well as obfuscate the original context.

 

[VinylxScratches]

Don't need to worry about any of that. It's mainly scripting and stuff like that. A lot of it is general Active Directory interactions via Powershell.