Live data from Hacker News

I'm writing a book: "JavaScript Application Design: A Build First Approach"

bevacqua.io

1–10 of 20 posts

Re: I'm writing a book: "JavaScript Application Design: A Build First Approach"

#2
Interesting. I'll be one of the first to buy (does pre-order include early editions of the book?).

I tried out continuous design when trying to learn and build with Angular and CoffeeScript for the first time...and I loved it...made me want to quit Rails development entirely. I still don't know much about grunt except how to copy-paste the commands to set things up, but more insight on how this all works, plus best practices, is a winning topic for me.

Re: I'm writing a book: "JavaScript Application Design: A Build First Approach"

#3
post #2

Interesting. I'll be one of the first to buy (does pre-order include early editions of the book?). I tried out continuous design when trying to learn and build with Angular and CoffeeScript for the first time...and I loved it...made me want to quit Rails development entirely. I still don't know much about grunt except how to copy-paste the commands to set things up, but more insight on how this all works, plus best p…

Pre-order includes early access to chapters as they are released. The program kicks off with 3 chapters which you can start reading right now, and then one additional chapter will be released each month.

If you go for the print book too, you'll get a physical hard copy as well when the book goes to print.

Glad you're thinking of buying it! :-)

Re: I'm writing a book: "JavaScript Application Design: A Build First Approach"

#5
This is a fantastic idea. I've been using a version of this process to build a client-side app over the past few months and have found it to be a huge improvement over my previous approaches.

Looking forward to seeing what suggestions the author has for making my process even better. :-)

Re: I'm writing a book: "JavaScript Application Design: A Build First Approach"

#7
edit: I could see this being just a good general approach to development. Like a concrete how-to on doing continuous delivery from day one.

I've even started using grunt with a C++ project I'm working on, and if I make sure that from day one I can start up from a new machine:

   % grunt init
... my life is better.

It's interesting, grunt is a nice "automation layer", as opposed to a build tool. I'm now using it to automate my build setup. Having that extra thing to bring it all together into one command makes it all so much easier.

Re: I'm writing a book: "JavaScript Application Design: A Build First Approach"

#9

edit: I could see this being just a good general approach to development. Like a concrete how-to on doing continuous delivery from day one. I've even started using grunt with a C++ project I'm working on, and if I make sure that from day one I can start up from a new machine: % grunt init ... my life is better. It's interesting, grunt is a nice "automation layer", as opposed to a build tool. I'm now using it to autom…

What makes grunt better than the alternatives?

Re: I'm writing a book: "JavaScript Application Design: A Build First Approach"

#10
post #5

This is a fantastic idea. I've been using a version of this process to build a client-side app over the past few months and have found it to be a huge improvement over my previous approaches. Looking forward to seeing what suggestions the author has for making my process even better. :-)

I am in the dark, the pasge describes a build tool, what's the fantastic idea here? What is your build doing. or do you mean simply build vs using an ftp server? sorry if this sounds weird, but the blurb explains nothing new, and nothing which cannot be done waaaaay better.
Post reply on HN