Let's scaffold a Web App
yeoman.io
yeoman.io
HOWEVER a "scaffold" doesn't really teach you how to use OAUTH to authenticate with Facebook, handle sending emails (welcomes, password resets, etc.) or even how to really build something. Instead I'm a big fan of working site examples:
Drywall: http://jedireza.github.io/drywall/ Hackathon-starter: http://hackathonstarter.herokuapp.com/ Skeleton (Mine): http://skeleton-app.jit.su/
You get all the scaffolding + real working code for all the basic site functions. You then build from there.
Thanks a lot!
I enjoy using generators btw.
Larger LOB, or public facing apps require more thought and planning to ensure that they get the job done right.
What's wrong with creating an app generator that spits out enough stuff to get you going on a certain app?
If I don't have to spend 15 minutes making a bunch of small changes and additions every time I make a new project then I will be more likely create more projects.
It's part of the reason why building a SOA is painful. If you have 25 services that means you need to start 25 new apps. It might take 20 hours of boilerplate garbage that you have to do just to start developing the business logic.
With generators you can turn that into almost no time at all, you would be bound by how fast your hard drive can write the files to disk or how fast you can pull things from github.
Btw I also use generators for public facing things. Why? Because typing 1 command which generates 6-7 files and also gets me going on what needs to be replaced is a lot faster than starting from absolutely nothing.
It doesn't matter if I end up replacing 100% of the view code or 90% of the controller code. Also if I feel like I will be doing a lot of CRUD'ish things in similar ways then I will spend 15 minutes once up front and create custom generator templates for that specific project.
It's nice to be able to type 1 command out and get a fully working scaffold with your custom theme and changes already applied complete with elastic search integration and faceted navigation, etc.. I do this all the time when applicable.
Maybe you were joking, but to call editing an index.php file a scaffold is scary (although highly profitable for me!)
Is it really? Personally, I've found that many of the projects which hired those sorts of developers either have little budget to start with, or have little budget left for a 'version 2' or 'clean up version 1' effort, because they spent most of it on the earlier garbage. Certainly plenty of work available to do that sort of clean up, but it doesn't strike me as 'highly profitable' on the whole.
Again, I only do these projects as moonlighting, this isn't my primary source of income. People contact me to fix their sites based on referrals and they know my rate before they contact me. I don't go out of my way to scour craigslist/odesk/whatever for jobs.
And actually, for most cases, yes using a framework is a better choice for nearly any skilled team with PHP: it's too easy to get it wrong, and now you have a massive security breach. See any exploit database for examples.