Don't. Waste. Time.
humbledmba.com
Don't. Waste. Time.
1–10 of 75 posts
Re: Don't. Waste. Time.
#2The one thing that I do think is important though is business cards. We got business cards before we even got 1 line of code written. It just seems like an established way to exchange info at events more so than using "bump", I think.
Re: Don't. Waste. Time.
#3Re: Don't. Waste. Time.
#4Good article. "Outsource all over the place" is so important. Pay some expert for a few hours of work that would take you a week (ie: healthcare). The one thing that I do think is important though is business cards. We got business cards before we even got 1 line of code written. It just seems like an established way to exchange info at events more so than using "bump", I think.
Note that communicating with such expert sometimes can take more time and be more frustrating than if you did this yourself. It's not all black and white.
Re: Don't. Waste. Time.
#5Good article. "Outsource all over the place" is so important. Pay some expert for a few hours of work that would take you a week (ie: healthcare). The one thing that I do think is important though is business cards. We got business cards before we even got 1 line of code written. It just seems like an established way to exchange info at events more so than using "bump", I think.
Pay some expert for a few hours of work that would take you a week (ie: healthcare). Note that communicating with such expert sometimes can take more time and be more frustrating than if you did this yourself. It's not all black and white.
Re: Don't. Waste. Time.
#6Re: Don't. Waste. Time.
#7Good article. "Outsource all over the place" is so important. Pay some expert for a few hours of work that would take you a week (ie: healthcare). The one thing that I do think is important though is business cards. We got business cards before we even got 1 line of code written. It just seems like an established way to exchange info at events more so than using "bump", I think.
Pay some expert for a few hours of work that would take you a week (ie: healthcare). Note that communicating with such expert sometimes can take more time and be more frustrating than if you did this yourself. It's not all black and white.
The expert often knows how to communicate more effectively than a non-expert would anticipate, because she has seen all the common issues before. That's what expert means. When a non-expert encounters a problem for the first time it always feels like a uniquely strange and complicated new thing. But more often than not an expert will listen to you describe your problem for two minutes, reach into a drawer and pull out a standard design that fits 85% of your use case, adjust the settings on the five standard knobs to cover another 10% of your use case, and then focus on the remaining five per cent... or, perhaps, just deliver the solution to you and let you tinker with the remaining five per cent.
It's hard to appreciate this process until you've been through it several times in different contexts. Because one of the things that non-experts are not expert at is: Knowing what the experts can do for you. Telling the difference between a problem that benefits from lavish amounts of personal attention and one that can be solved in ten minutes by someone for whom your problem is a daily routine and who knows just what to ask.
Re: Don't. Waste. Time.
#8Where does "blogging" and "submitting your own writing to HN" fall on the wasting time list?
Re: Don't. Waste. Time.
#9I might be wasting time writing code when I can best contribute by taking care of 'overhead' so my team isn't blocked - there's an anecdote here somewhere of the PM who would buy coffee for the team so the team can focus on producing code - or i might be wasting time taking care of 'overhead' that doesn't matter yet (planning the optimum office layout) when I can best contribute by writing code.
To know whether or not you're wasting time, you have to know what makes one work "fake" and the other "good", and my list may be vastly different from yours.