bry | 5 years ago | on: Show HN: InstructionPad – Centralize your teams' “how-to” guides
bry's comments
bry | 6 years ago | on: Show HN: Simple Group Email Discussion Lists
Making group collaboration easier seems like a win no matter what.
bry | 9 years ago | on: Brilliant Jerks Cost More Than They Are Worth
bry | 11 years ago | on: Layers – A simple WordPress site builder
bry | 11 years ago | on: WordPress 4.0 is out
bry | 12 years ago | on: Terms of Service update
bry | 13 years ago | on: [] are like Facebook
bry | 14 years ago | on: Microsoft's Azure cloud down and out for 8 hours
We have an Azure CDN backed by a Compute Instance, and zero official notice from Microsoft about this still. I've learned more about the problem from news articles than the company that provides the service. Fortunately we haven't finished migrating the rest of the site to Azure. No emails from them, nothing. Not even a tweet on their official @WindowsAzure account. Frustrating.
bry | 14 years ago | on: Steve Blank's new book - The Startup Owner's Manual
bry | 14 years ago | on: Steve Blank releases updated book
Essentially he wants people to be able to use it as a workbook, and not as a quick read (if that's even possible).
bry | 14 years ago | on: Steve Blank releases updated book
bry | 14 years ago | on: Ask HN: Oops, I just sold my startup to a piano company. Now what?
Unfortunately, that's not only an east coast thing. It seems to be related to the size of the company. The larger the company, the more they seem to feel/act that way :/
bry | 14 years ago | on: You're a developer, so why do you work for someone else?
Perhaps I gave up too soon, but I've moved on. I'm well into my new project, which is certainly not sexy, but I'm excited about it.
bry | 14 years ago | on: You're a developer, so why do you work for someone else?
bry | 14 years ago | on: You're a developer, so why do you work for someone else?
When I wrote the article, it was essentially me expressing my thoughts about how anyone if they want to (because not everyone does) CAN build something and start their own business, even without substantial capital. The barrier to entry is so low (comparatively speaking) that if you want to go out on your own as a developer, it is entirely possible. The post was meant to be encouragement to those who are interested, not sensational (although I did make some generalizations) :)
I actually built the original thing I discussed in the article (a service to manage Boy Scouts), and it got some great reviews and initial interest, but then the Boy Scouts wanted me to pay huge fees to license the term "Boy Scout" or use anything even resembling any of their trademarks. I decided to let that go and build something that does not piggyback on any other organization. That's what I'm working on now.
A year "lost" is a long time, but I haven't given up. I haven't lost anything other than time, since I was bootstrapping it and building it on my own time in the evenings. I won't be happy until I am doing my own thing. I'll post a follow-up with what I've learned and what has happened over the past year to anyone who is interested.
bry | 14 years ago | on: Good startup teaser page design? Opinions?
Looks great. Needs a little more substance (just a little).
bry | 14 years ago | on: Ask HN: any good alternatives to Pivotal Tracker?
bry | 15 years ago | on: Three of the top Anonymous leaders allegedly captured in Spain
bry | 15 years ago | on: College is a waste of time
bry | 15 years ago | on: Safari extension to hide Bitcoin stories on HN
I like to think of “how to” guides like recipes for how to do something specific to your team. This site helps you create and organize them.
Background: I’m a software engineer, and more recently a software engineering manager at one of the FAANG companies (I’m not mentioning which one just to retain a tiny bit of anonymity). My point, though, is that even at huge established companies, having one place to share your team’s “how to” guides isn’t easy. My company has a huge internal wiki. It’s awful. Search sucks, and it’s like the Wild Wild West — no structure at all.
Some teams/companies try to solve this with “Knowledge Base” software, but I think what we need is a little simpler. Knowledge Bases are great for things like general information, strategy docs, and collaborative efforts… but not so much for straight-forward how-to guides (AKA SOPs or checklists).
At my current and all of my previous companies, we’ve always struggled with how and where to document our how-to guides/SOPs/checklists or whatever you want to call them. This grew out of my own need and I’m hoping to make something of it if other people find it useful too.
What I’d love feedback on:
1. Does the idea resonate? Does it apply to you and your team?
2. Does the messaging on the site make that clear?
3. I know it’s still pretty basic, but does it provide enough value right now to be considered an MVP that people might pay for?
4. What did you like?
5. What’s missing?