Hit enter to search or ESC to close
tl; Doctor: Despite the fact that there are more resources out there to learn how to accomplish what you want to achieve within WordPress, it is less common to find someone who is facing the same problem under similar constraints.
Write about your work. Include the problems you are solving, and the thought process that goes into solving them. Although you may be describing a general problem, you may be describing them from your point of view.
Long before I got into developing WordPress, I decided early in my career that I wanted to have a public notebook of my work, the problems I faced, and how I solved them in the context of my situation.
I was No Preconceived notions that I am going to write about something unique. I mean, by the time I started blogging, people were doing the same thing for a long time. In addition, people have been programming and discussing their work on bulletin board systems, or IRCs, for a long time.
But the point was not to try to share something new. The point was to create a public notebook of my experience as a programmer.
At first, I was inspired by people who had come before me. This includes big players like Joel Spolsky and Jeff Atwood, and other smaller players that I’d find while Googling (pre-Stack Overflow) for solutions.
Second, I have always found that I learn best not only when I approach a problem but when I express it in my own words. It helps to reinforce what I’ve done, why, and to provide the reasoning behind it (other than) It just works!) Sometimes clarifying a solution helps to highlight the problems with it.
Third, before I disable comments – which is another post entirely – it would also help to foster a valid discussion on what to improve there. (remember, this was before Twitter was mainstream and people could publicly praise or shame you for such things ).
Absolutely. This not only helped me develop the habit of writing regularly but also helped in creating in-office presentations with which I felt more comfortable talking about a given topic.
Since I already explained this in writing, I was able to put together presentations for my colleagues that would explain what my team has done and perhaps share our solutions for other teams to use (and its Adverse).
it eventually worked its way into me becoming more comfortable speaking
This eventually gave way to me:
Again, much of the above is going to be a topic for an upcoming post.
i have already given tl; Dr And I’ve already shared the benefits I’ve gained from writing, but here’s the thing: There’s more to be lost than just writing about what you’re doing.
It doesn’t matter that someone else has already written about the same topic. It doesn’t matter if the problem is resolved Some by someone else. that does not matter How The problem was resolved.
Sharing your work publicly provides immeasurable returns on what it can do. Again, no one has solved your problem in the same exact context as you have.
You have something to offer and you have something to gain. It’s a great thing to do for you and everyone who follows what you’re doing (or for those who drive-by your posts via Google or DuckDuckGo).
All that said, I won’t make up the whole picture when you could be wrong Doing Share your work publicly. And I’m not talking about publishing bad packages or releasing bad code to the public. I’m talking about writing about things that are such an opinion that it can generate social collateral damage in the process.
This is one of the biggest mistakes I’ve made in my writing and it’s one of the mistakes I’ve worked hard to avoid. But it is so much talked about that it deserves its own post.
Since I don’t think one should blindly write about one’s experiences (especially when it comes to negative May come from), it also seems appropriate to share what you see.
And that’s what I’ll discuss next.
About the author