Live data from Hacker News

How I Built 180 Websites in 180 days and became a YC Fellowship Founder

zube.io

11–20 of 31 posts

Re: How I Built 180 Websites in 180 days and became a YC Fellowship Founder

#11

Great passion and commitment! I am curious how you became confident in javascript and rails in a short period of time? Did you read books?

Thank you! I did a lot of Googling. Each day I would break down what I wanted to do into small components and start researching. I used sites like Stack Overflow, Mozilla Developer Network and CSSTricks to find answers and a lot of trial and error to get things working. I also used Michael Hartl's Rails Tutorial to get up and running with Rails.

Re: How I Built 180 Websites in 180 days and became a YC Fellowship Founder

#13

Hey everyone! I'm happy to answer any questions. AMA!

Inspiring stuff! What's your take on Jira? How is Zube different from others?

JIRA is a great tool but it's hard to set up and for small teams it can be overkill. We built Zube to provide an Agile workflow right out of the box so you can get up an running right away.

Zube is also deeply integrated with GitHub and everything is synced both ways in real time. So even if some of your developers want to stay in GitHub, everything is still up to date.

Re: How I Built 180 Websites in 180 days and became a YC Fellowship Founder

#16

Hey everyone! I'm happy to answer any questions. AMA!

Great work and fun article. You sort of already answered my question about how repeatable this is outside web development. I think having resources like StackOverflow solving most common issues and the field not having a lot of depth (barrier to entry) were critical. Might be a tad more difficult to do, say, secure systems software or hardware this way.

Determination, practice, and one-milestone-at-a-time are my main takeaways here. This benefits any field. Strange enough, it especially benefits high-assurance software because the stuff takes so much time and analysis companies might pull out financially or FOSS people loose focus/hope. INFOSEC guru Paul Karger promoted turning a big project into a series of intermediate, useful deliverables to maintain morale and provide short-term revenue from licensing/sales of intermediates. Seems same for learning, too.

Re: How I Built 180 Websites in 180 days and became a YC Fellowship Founder

#18

For someone who struggles with the design side of making websites, this is inspirational. I guess the takeaway here is just to practice, practice, practice.

Thanks! Yes, repetition is super helpful. Before starting a new project, many artists will go through a 'research' phase where they'll make quick iterations of ideas over the course of days or weeks. That's part of where the idea for the 180 Websites project came from.

Re: How I Built 180 Websites in 180 days and became a YC Fellowship Founder

#19

Earlier quoted context omitted.

Inspiring stuff! What's your take on Jira? How is Zube different from others?

JIRA is a great tool but it's hard to set up and for small teams it can be overkill. We built Zube to provide an Agile workflow right out of the box so you can get up an running right away. Zube is also deeply integrated with GitHub and everything is synced both ways in real time. So even if some of your developers want to stay in GitHub, everything is still up to date.

To me, this two-way sync'ing is the killer feature of Zube (from my short usage so far), along with its Trello-like card metaphor for issues as a value-added layer.

Just having the real-time filtering on issues is a huge win. Change a filter, see your updated list. Excellent.

Re: How I Built 180 Websites in 180 days and became a YC Fellowship Founder

#20
post #19

Earlier quoted context omitted.

JIRA is a great tool but it's hard to set up and for small teams it can be overkill. We built Zube to provide an Agile workflow right out of the box so you can get up an running right away. Zube is also deeply integrated with GitHub and everything is synced both ways in real time. So even if some of your developers want to stay in GitHub, everything is still up to date.

To me, this two-way sync'ing is the killer feature of Zube (from my short usage so far), along with its Trello-like card metaphor for issues as a value-added layer. Just having the real-time filtering on issues is a huge win. Change a filter, see your updated list. Excellent.

Right on!
Post reply on HN