Why Another Developer Blog?

Home » General Topics » Why Another Developer Blog?
Words: Why Not on a yellow background

Why, after more than 30 years as a developer, have I decided to create a blog?

First and foremost, a blog is a form of communication with other interested parties about subjects that are mutually of interest. I wouldn’t dream of disabling comments like some companies do, all forms of feedback are greatly appreciated and they are an important part of the blog/conversation.

Secondly, if I spend all day trying to work something out, usually this goes into my private wiki so I can refer to it if I ever need to come back to it. I would like to share this information with you. Also for me, the detail gone into on the blog will help cement my understanding and also allow me to refer back diary style on my developer life.

I have put a lot of effort into being a developer and doing the best I possibly can. I would like to share this knowledge and my reading list with you.

Finally, I would like to help developers with less experience (lets face it, even experienced developers have difficulty keeping up to date with everything; there is always lots to learn even about something you work with often, so I might know about some things that you don’t and vice versa).

This blog is going to have a bit of something for everyone, beginners and experts alike. If I spend what I consider to be excessive time finding or working something out, its a candidate for this blog so I can help others save time.

Thanks for reading, I’ll do my best to make this blog a useful resource for you.

Regards

 

Philip Johnson, Jan 2015

 

About Phil

I have been working as a software developer since 1983. This blog could have been called "From Fortran 77, C and Cobol to C# in 20 (not so) easy years", but it doesn't sound quite right somehow. Besides I'm talking about what's happened since 2003, not before!

Leave a Reply

Your email address will not be published.


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">




Top Posts & Pages

Categories

Recent Posts

Recent Comments

Archives

Blogroll

  • Mike Cohn's Blog
  • Scott Hanselman's Blog
- mike@mountaingoatsoftware.com

When estimating in story points, teams should think in terms of ranges and rounding up. Here’s why. [...]

- mike@mountaingoatsoftware.com

Batman would make the perfect Scrum Master. Once he eliminates crime in Gotham City, I plan on offer [...]

- mike@mountaingoatsoftware.com

It can sometimes be a challenge to get people to attend and then participate in sprint reviews. Here [...]

- mike@mountaingoatsoftware.com

The standard “As a...I...so that…” user story template has stood the test of time. Here’s why each o [...]

- mike@mountaingoatsoftware.com

From helping teams understand the boundaries of self organization to creating safety around things l [...]

- Scott Hanselman

There's some interesting stuff quietly happening in the "Console App" world within op [...]

- Scott Hanselman

As I've mentioned lately, I'm quietly moving my Website from a physical machine to a numbe [...]

- Scott Hanselman

I'm quietly moving my Website from a physical machine to a number of Cloud Services hosted in A [...]

- Scott Hanselman

I'm doing a quiet backend migration/update to my family of sites. If I do it right, there will [...]

- Scott Hanselman

Technical Debt has a way of sneaking up on you. While my podcast site and the other 16ish sites I ru [...]

Meta