Keep a programmers/developers journal and try to write something in it every day. A technical blog works as well. The important thing is to write about the technical decisions you make like:
- Why you designed a class in a particular way
- The implications of an architecture decision
- The development process for a particular algorithm or method of which you are proud.
There are many other things you could write about, but focus on the technical and try to make it easy to understand.
When you feel comfortable writing for yourself, you can publish your journal as a blog, and look for feedback.
Just like coders learn to write better code by programming at the edge of their ability/comfort, writers learn to write better by writing at the edge of their ability.
The style guide suggestions by other posters are good, but the best in my opinion remains Strunk & White, The Elements of Style. They even have a badge named after it here on SO.