Ask HN: How do you gents make blueprints for your web application idea? | Hacker News Reader

Ask HN: How do you gents make blueprints for your web application idea?

4 pointsmikenwani8 comments

I have to take over the Ruby on Rails code for a startup idea that I agreed to be a part of. It was done by a developer hired for a month from odesk (he didn't do much; lots of arguing and disappointment from my partner; it wasn't my idea to get this guy and this was all before I got on board).

I've yet to truly examine this guy's code, and to be honest I have a fear that I'll come across something I don't understand. I'm trying to get serious about this idea and to take on building it, so I was hoping I could get some expert opinion on how one should map out their website idea's functionality? Any specific diagramming software? Or just tons of pencil and paper?

Thank you.

View on HN

"you gents" is an absolutely awful way to address this query.

To answer the question: a sharpie and lots of paper.

Why? And admittedly I do prefer the idea of just lots of plain, large printing paper and a sharpie. I just wanted to verify that people more professional than me like to do this method also

Thanks for engaging on it.

There's a much larger conversation going on, about the role of gender in technology. Two of the core topics are 1) the presence (or lack) of women in computer science / web development, and 2) the respect given to the women who are present.

Even if it was unintended, directing a question on an open board to "gents" suggests one of two things: 1) there are only men here; 2) even if there are women here, I'm not interested in their insights. The first is false (HN does have women, and would be improved with more). The second is disrespectful and would also lead to a poorer results set.

I'm sure there was no disrespect intended on your part. Indeed, I'd believe you were trying to make the question more respectful.

Either "How do you make blueprints for your web application idea?" or "How should I make blueprints for my web application idea?" would carry the exact same intended payload, while removing the gendered language issues.

As a follow-up to my earlier point, I'd really recommend the 37 Signals blog and the writings from Amy Hoy. Just about anything from their back catalog will be helpful as you map out your ideas, and as you make sure the product you build is actually something people will want.

My use of "gents" was actually a third result: I mean any kind person that wants to chime in, man or woman. I was just being playful.

But I understand that that word couldn't mean anything but a synonym for "men" on the internet, so that shouldn't have been used, my bad.

And thank you for the referral, I'll definitely be reading their blog posts now.

Here is my process:

1. Talk with the business stakeholder to understand all of the functional requirements (read: things he/she can't live without and nothing regarding colors)

2. I then use Balsamiq to quickly create some low fidelity mockups

3. I then export every action into a PNG and use http://marvelapp.com to add animations between pages

4. Show to the business stakeholder to see if this fits all of their functional requirements

This process typically takes about 2 days

Thank you!

Stop diagramming an just jump into the code...

Knowing what I'm building (as much as possible) before I start building produces better (more stable/flexible) code. I wouldn't suggest trying to build a foundation w/out knowing what's going on top of it

Reply on news.ycombinator.com