This is a really amazing endeavour! Great job! I really like Coded and Electro Bounce. A couple questions: Could you provide some more details about individual projects (frameworks used, any source info)? Also, how long on average did you spend on each project? Finally, what's your favorite project?
I was spending an average of 10 hours a day, every day on the 180 Websites project. For YumHacker, I was working on that full time for about 6 months or so. We've been working on Zube for about 1 year now full time.
Thank you! Electro bounce is one of my favorites as well :)
180 websites is mostly Rails backed. The first 68 pages are served out of the public folder and almost everything else was done with Rails. The last week is all done with Node.js.
YumHacker uses Rails as an API on the backend, and Backbone,js for the front end.
I had a lot of fun working on the 180 Websites project. It was grueling at times but pushing something live everyday was super satisfying. My favorites are Electro Bounce, How We're Feeling and Elevations.
I love working on Zube now. It's awesome to be able to make a product that helps developers.
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.
I am deeply encouraged by your article. Surprisingly! I was thinking of doing the same thing prior to reading your article, which is, as part of my 100 day of code challenge to build a website every day and GitHub it. I guess the reason for my procrastination is being afraid of using GitHub, my lack of javascript knowledge & I barely know any design. Your input is definitely helpful! I really want to start being proficient in those areas mentioned. Also what learning resource would you recommend for javascript front & back end, web/application design, UX design and better grips on Github!
Hello, great job, I started following you first a few months back. My questions are,A: if you had to start all over again, what would you do differently. B: how did you decide on what to build each day in those 180 days. Last and this is the most important, I think learning by doing is the best way, is there a way where your experiences could be optimized for a newbie, where he/she could start from day one, build something and learn a specific part of a technology, and all the way to the end.
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.
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.
During the project I had to travel from San Francisco to Pennsylvania for family obligations. I managed to do a pretty good job of keeping my coding schedule up while flying and spending time with my family, but I ended up having to stay up pretty late to finish each day's website.
By the end of the trip I was really burnt out but I still needed to crank something out on the flight home. I had an idea for a site where you could enter a few hexadecimal color codes and the screen would transition between them. It seemed totally easy in my sleep deprived state but when I started working on it on the plane I totally floundered.
When I finally got back home to my apartment in SF, it was 9pm and I had virtually nothing to to show for my day's work. Also, I was now freaking out. I didn't know how I was going to be able to push up anything!
I took a look at what I originally wanted to do and what little I had done and realized if I reigned in my scope a bit, I could get a website out before I completely lost my mind. I pared it down to just two colors and cut out all the bells and whistles and just barely managed to get it out the door. And then I had a very, very nice sleep.
YC recently started a new program called YC Fellowship. We're in the second cohort now. It's an 8 week program for early stage companies that you can participate in remotely. They describe it as a lighter version of YC core.
qrv3w|10 years ago
jenniferDewalt|10 years ago
jenniferDewalt|10 years ago
180 websites is mostly Rails backed. The first 68 pages are served out of the public folder and almost everything else was done with Rails. The last week is all done with Node.js.
YumHacker uses Rails as an API on the backend, and Backbone,js for the front end.
Zube uses Node.js and Backbone.js.
Edit: Here's a blog post I wrote after finishing the 180 Websites project that talks more about that. - http://blog.jenniferdewalt.com/post/62998082815/after-180-we...
jenniferDewalt|10 years ago
I love working on Zube now. It's awesome to be able to make a product that helps developers.
jenniferDewalt|10 years ago
nickpsecurity|10 years ago
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.
redmaverick|10 years ago
What's your take on Jira? How is Zube different from others?
JonthueM|10 years ago
fazkan|10 years ago
arvinsim|10 years ago
jenniferDewalt|10 years ago
alexkwan|10 years ago
jenniferDewalt|10 years ago
cosecantt|10 years ago
jenniferDewalt|10 years ago
petepark|10 years ago
yishanl|10 years ago
jenniferDewalt|10 years ago
By the end of the trip I was really burnt out but I still needed to crank something out on the flight home. I had an idea for a site where you could enter a few hexadecimal color codes and the screen would transition between them. It seemed totally easy in my sleep deprived state but when I started working on it on the plane I totally floundered.
When I finally got back home to my apartment in SF, it was 9pm and I had virtually nothing to to show for my day's work. Also, I was now freaking out. I didn't know how I was going to be able to push up anything!
I took a look at what I originally wanted to do and what little I had done and realized if I reigned in my scope a bit, I could get a website out before I completely lost my mind. I pared it down to just two colors and cut out all the bells and whistles and just barely managed to get it out the door. And then I had a very, very nice sleep.
RafiZ|10 years ago
jenniferDewalt|10 years ago
idoivri|10 years ago
gyoza|10 years ago
jenniferDewalt|10 years ago
You can read more about it here - https://fellowship.ycombinator.com
aby002|10 years ago
[deleted]