Pete On Software

RSS Feed

Archive for 'Business of Software'

Winners and Losers

Gold Trophy, labeled for reuse from WikipediaI was listening to James Altucher’s interview with Shane Snow this morning and some of their discussion reminded me of something that Ron Carter (former podcast guest) is fond of saying. It is a quote that I try to remember and live by, so I thought that I’d share it here.

Winners take the blame when something goes wrong and give (or share) credit when things go right. Losers look to assign blame when things go wrong and hog the credit when things go right.

That’s applicable in so many areas of life. Think about the quarterback who goes before the press after a loss and says that he made the wrong read or that he has to play better when the real problem was that his receiver ran the wrong route or his offensive line was a sieve. However, on victory day that same quarterback is praising the offensive line’s protection and the play calling and the receivers’ exceptional skill.

That is the same model that we should seek to have. Don’t worry that you aren’t going to get your proper credit. If you did a great job, your teammates will know your role. And they won’t forget that you helped them shine, too. More than that, though, they’ll respect you for not throwing them under the bus when things go wrong.

This isn’t just about success and failure in a team environment. When a loser fails on solo endeavors, he’ll look to blame society, his equipment, the government, his family, his parents, whatever. Anything but turning the gaze inward and looking to see how the failure can be an opportunity to learn and grow and improve.

Winners take responsibility. Winners share credit. Winners learn from mistakes. Be a winner.

Podcast Episode 17 – Going Independent

Going IndependentIn Episode 17, I talk about what it takes to go independent as a software developer. After taking a moment to give all of the provisos that I’m not an expert offering legal or financial advice, I spend this episode talking about what my journey has been like. How did I come up with a name? How did I find work? What about health insurance? What about rates? I cover all of that and more in this episode.

While this episode is certainly not exhaustive, I do try my best to talk about what I had to go through while becoming an independent developer. There are a lot of little things that I had to tackle that were unknown to me before I took the plunge. And the fear of that unknown kept me from moving forward for a long time. I hope that some of what I’ve shared in this episode will encourage anyone who is looking to start out on their own.

Links Mentioned in this Show:

SCORE

Dublin Entrepreneurial Center

Michael Eaton’s Deep Fried Bytes Episode Announcement

John Sonmez’s Course

John on .Net Rocks! and on The Polymorphic Podcast

You can also subscribe to the podcast at any of these places:
iTunes Link RSS Feed Listen on Stitcher

In addition, my podcast is available on DoubleTwist, Swell, and the Windows Marketplace.

Thanks to all the people who listen, and a special thanks to those who have rated me. I really appreciate it.

Listen here:

Podcast Episode 11 – Ron Carter on Being a CIO

Ron CarterThis week’s podcast was pretty fun. I interviewed someone that I know very well, someone who has taught me more about business and the business of software than any other person, Mr. Ron Carter. Ron is a CIO of a healthcare services company and held many roles in the past: consultant with major firms, developer, DBA, and architect, among others.

Ron has a track record of successfully delivering product after product, across many verticals in both the public and private sectors, for a tech industry where the failure of large product projects has become a punchline. Needless to say, Ron has a wealth of experience to share and I’m excited to have him on the show.

We talk about what it takes to be a CIO of an organization. Looking forward as a career path, we cover the role of CIO and the skills and knowledge that developers would need to reach the role. Other topics include team building, building trust, advice for new CIOs, and remote work.

It was a great interview, definitely give it a listen!

Podcast Episode 09 – My Interview With Craig Schwartz

Craig SchwartzIn episode 9 of the Pete on Software Podcast, I interviewed Craig Schwartz. Craig is the owner and principal at Gecko Jones, a marketing and product management company whose main goal is helping your organization to reach the next level.

It was kind of interesting how I even got the interview. In Episode 6 of the podcast, I reviewed the Choose Yourself book by James Altucher. I tweeted out the podcast and James was kind enough to RT me. On that show, I put out a call for ideas or volunteers for interviews and Craig stepped up. That is the power of social media at work right there!

In the episode, I talk to Craig about product planning and marketing. We not only talk about how to know if you have a viable product and how to promote it, but we also talk about self-promotion and how to get along better with the “creatives” over in marketing.

If you haven’t already listened, check it out. It will definitely help you be a more well-rounded developer!

Decision by Procrastination

Decisions, DecisionsToo many times I see indecisive people put off making a determination because they are too scared to make the call. However, as the Rush song goes, “If you choose not to decide, you still have made a choice”. If you put off making a decision long enough, you end up with the status quo or the decision of least resistance.

I do know someone who uses that to their advantage and allows certain decisions to be delayed, knowing that they will ultimately not get made, and that the hare-brained plan will end up never taking off.

Don’t let that be you. Don’t live your life on the path of least resistance.

There is something to be said for making sure you have enough information to judge wisely, but more often than not indecision is about fear. Consider the data, think about the options and tradeoffs, include your experience and the experience of those on your team, and “shoot the three”.

« Older Entries   Recent Entries »