Why?
That extra nudge of accountability to achieve even a small step on your IH journey each day.
To join in:
01 Share your epic (a big chunk of work with a meaty objective) you'd like to complete by the end of July.
02 Share what you accomplished yesterday.
03 Share what you commit to accomplishing today.
04 COMMNET on AT LEAST ONE fellow hacker's progress and give them an IH Point for their check in. Let's get in there with the encouragement/feedback!
Optional:
05 Share your Work In Progress to underscore your accomplishments.
Then tune in the tomorrow to share how you did on your own tasks!
#daily-stand-up
July
DONE:
This sets the stage for the full fledged on-boarding and use pipeline.
TODO:
Progress feels good. My time-boxing experiment feels right, so I'm going to continue with that.
I haven't had threadbase.io long, and I know I can limp it along, it pays for itself and then some, but I'm finding I have neither the time nor the expertise to give it the attention it needs to really grow. Might just need a technical partner with more Rails experience than I. I think I'm perhaps better suited to the people side than the code side on that project. Thoughts?
KUDOS:
@KeithBrink great EPIC. Great opportunity to expand your addressable space.
WIP:
AutomatedAPI.com
Sounds like you're spending a lot of your time doing development, so even though you may be more suited to the people side, you certainly have competence on the code side that will only grow as you invest more time there.
I wouldn't give up on that too early, especially if you don't have someone in mind right now. Finding a good partner and working with that partner will take a lot of work that you might as well just invest in yourself and your technical abilities.
Fair enough. That was my first instinct actually.
I can definitely pick up rails but only if I toss out some other bigger ideas. I'm a .NET native software engineer, so that switch feels a little odd.
EPIC
YESTERDAY
TODAY
Do discovery callsWIP: Envoy
KUDOS
@nlowell on getting REAL market feedback on the pricing page. Empower the customers to rip that page apart to the best insight to move the business forward!
@Aadhi welcome back!
01 - soft launch: Have the base application/library, documentation (both manual and API), and build tools publically accessible. Have license terms and sales flow (either contact or direct payment gateway) on the site.
02 - done: 1/3 of the sbt build plugin milestone.
03 - Goal today is not to have an off day and complete current milestone of the sbt build plugin.
04 - props to @KeithBrink for getting front end tests working. That, at least used to be, very challenging.
05 - what used to require the boilerplate:
now requires:
which is certainly shorter
EPIC FOR JULY
Complete 42 pieces of content for evergreen launch. Includes:
4 Facebook ads for two funnels (4 of 4 completed)3 Landing pages (3 of 3 completed)YESTERDAY
Definitely stalling on the damn home page.
TODAY
Time box home page. Two hours. Done.
KUDOS
@jpusateri Being on-call for Threadbase.io.
On-call is my least favorite thing ever.
I prefer a root canal :P
Feel your pain on being hung up on the home page. I eventually just resolved to ship something and the iterate till it looked "acceptable" haha.
Epic
Add eBay support to AZLabels
Yesterday
Today
July Epic
Moving a little slower than I like on the code pieces, might need to re-trajectorize
Yesterday
Today
Kudos
PENDING
Work in Progress
Announcr
01 EPIC
Complete market research & commit (scoped MVP) on an idea for August
02 Accomplished Yesterday
03 Accomplishing Today
Other Notes
I'm back! It's been a crazy month. Between personal emergencies and travel, I have done 0 for the past two weeks. But, I was able to enjoy the time off without worrying about the lack of shipping - which is good.
That being said, I did end up doing a few more customer calls on the road + a lot of thinking about what I'd heard. As of now I have ~3 ideas that I need to flesh out. So looks like rest of July will be lots of research and mapping out an MVP for the idea I'd like to pursue.
It's good to be back folks - missed reading through everyone's updates / progress :)
Looking forward to seeing what you come up with!
I'm curious, how are you directing this research to find a product?
I've never approached product design from a position of not having a generally formed idea to begin with.
It's a good question. I definitely have ideas running around in my mind about what I think remote co's would want. All those are based on my experience working in a ~100 remote co., but I had no way to tell if they were local or general problems that remote teams face.
So I started by doing some customer interviews - usually ~30min calls where I'd listen to remote leaders talk about the things that annoy them re: operating a remote co.
From those calls I got three general problems that I could tackle. Surprisingly, only one confirmed a problem I knew existed - two did not. The two I didn't know about also involve legal work to parse.
So right now I'm trying to research:
For each problem.