Bloggers reflect on what drives them to hit the “Publish” button time and again.
When you grow up surrounded by addiction you take notice. You see things in others and in yourself that some people might miss. You learn quickly that addiction is not always black and white. A lot…
Procrastination – Writer’s are often experts. #amwriting #writinglife #writingtips
One of the more popular blog topics targeting writer discusses why writers procrastinate.
One recent blog asked whether perfectionism caused writers to procrastinate. At last count there were 171 comments on the blog. Many agreed perfectionism to be an issue and offered advice, the most popular to write the draft and let the revision stage improve the manuscript. Easy to say, hard to apply, isn’t it?
For me and I expect a lot of writers, perfectionism never factors into the equation because some of us can’t even get started. Now that is true procrastination.
The reason (to me) is simple. Sitting down to work on a writing project, whether it is an outline, a first draft, or revising an existing project, means you have decided to commit a block of time to essentially create something from nothing. Many writers fail because they realize that block of time can be…
View original post 1,076 more words
As an application development manager, I spend a good deal of my day thinking about technical debt. Some people think the concept of “technical debt” didn’t exist in Waterfall projects, but it’s really been around since the beginning of code — the difference is back when, we weren’t doing it on purpose. Now we’ve always seen some debate, going way back, with folks arguing messy code can’t count as debt; however, just like a financial debt, whether you applied for a loan or got hit with a big speeding ticket, you still have to pay it (often out of finite funds).
As part of our Agile journey, my teams are currently learning new ways to address technical debt. It won’t do a bit of good to clean up the current debt if you don’t also put your debt on a diet to reduce the rate of accumulation of new debt. That’s like taking out a new credit card to balance transfer and pay off another card… and then maxing out that card again!
Technical debt, having become my main focus recently, is what I’ve been invited to speak about at the DevNexus 2017 conference in Atlanta February 22-24. I spoke at this conference in 2015 and I’m so happy to be coming back. I will still talk a bit about my passions, Agile and User Experience, but the main focus this year will be on the technical, and often political, side of Agile.
Many Agile teams have a hard time managing technical debt. Like foundational stories, technical debt stories often get pushed to the bottom of a product owner’s priority list. It seems like we fight a constant battle between dealing with our mess and wanting to deliver the sexy new feature. Some of the items I’ll cover include:
- What technical debt is (and what it isn’t)
- Good and bad sources of technical debt
- Techniques to reduce the production of more debt
- Creating a debt reduction value proposition for product owners and customers
- In-sprint options for dealing with debt (and foundational stories)
The conference sold out last month, so it’s too lake to get tickets. However, as part of the overall presentation, I’ll add some content on technical debt here. If anyone would like a specific question answered, please feel free to contact me.
Vulpes Libris, Latin for “Book Fox,” is a literary hub where a collective of bibliophiles talk about what they read, and publish interviews, reviews, and other bookish treats.
In case you missed it – Post on timelines from Jack Strandburg @jackstr952 #writingtips #amwriting
Every writer develops their stories in different ways. Some outline, some write from scratch and let the characters develop and the plot emerge as they write. Others might draft three or four chapters before they decide it’s time to step back and determine the flow of the story.
I’ve tried all of the above and other approaches, but always come back to, and finally settled on outlining. My “ideal” story will be mapped out with all questions and issues resolved before I write the draft. Of course, that’s in a perfect world.
Regardless of the approach you use, at some point the chronology of the events in the lives of your characters will need to be validated. Most, if not all stories involve background events for your main characters, which may or may not be included in the final version. But these events are important because you want to ensure…
View original post 915 more words