Hey, Adjutant Staff!

[Woz 1st MRB]

I've got a project that I have been working on that will hopefully automate some of the adjutant duties. However, I would like to speak with someone who works in that office about how some of the process works, as well as discuss what would be most helpful.

Please reply here if this sounds interesting to you and you have the time to schedule a vent meeting to iron some requirements and features out.

Also, if you are familiar with MEAN stack (MongoDB, ExpressJS, AngularJS, NodeJS) or DOM scraping with Cheerio, Request and Node, and feel like contributing, please do not hesitate to chime in and we can work out a collaboration.

Thanks,

S. Woz

[Goodwin 1st MRB]

Interestingly enough, I was considering doing something similar - although not with Angular (yuck); just going to use a nice PHP framework.

I feel Angular just is more complicated than it needs to be (apparently, I am not alone) I'll admit, I don't know much about node besides it looks really cool - I haven't had a chance to play with it yet.

I was considering Laravel 5 - basically automating most of everything (including the creation of post markup depending on task performed).

I'm interested to see how this plays out - let me know if you need help!

[Woz 1st MRB]

Interestingly enough, I was considering doing something similar - although not with Angular (yuck); just going to use a nice PHP framework.

Be honest, is that because you favor PHP over other frameworks?

Angular is perfectly fine for small scale applications, and has no issues with scalability in large ones if engineered properly. (Just like PHP)

I feel Angular just is more complicated than it needs to be (apparently, I am not alone)

It does come with all the features packaged, but it is very simple to get an app running. You basically have routes defined for your app, and DI your controllers for those routes into the app (or lazy load with requirejs), and then DI your services (directives, factories, services, etc.) into the controllers. The person who wrote that article is probably miserable to work with, and probably hates angularjs because he was required to use it on a project it wasn't suited for. Similarly, I have a bad taste in my mouth with Ruby, but only because the project at work that is using it is a nightmare.

I'll admit, I don't know much about node besides it looks really cool - I haven't had a chance to play with it yet.

I was considering Laravel 5 - basically automating most of everything (including the creation of post markup depending on task performed).

I'm interested to see how this plays out - let me know if you need help!

Now is a perfect chance to play with it! I'm not entirely familiar with this stack, but I am interested in experimenting with it and taking my findings into the professional world. I'd love to do some PHP since I have done that in the past and it also seems to be your specialty, but since Node takes the place of Apache in this stack, it doesn't seem like it would fit in too well. As far as automating goes, I'm also trying out Yeoman for creating endpoints and services. Here is the website that the default generator first makes. You can extend it pretty easily with one line commands that then prompt you for required information.

I mainly picked this stack to see what doing javascript for the whole stack would be like. I'm not sure how good of a fit MongoDB will be. It will be my first time using NOSQL technology. My research seems to point to NOSQL being good for data that might be incomplete (like that of web scraping), and the fact that it is essentially stored JSON will make it mesh very well with javascript.

Once I speak to an Adjutant to get the ball rolling on requirements, I will get a project started up and maybe we can explore this framework together!

What are Laravel's main features? I hadn't heard of it until you mentioned it just now.

[Goodwin 1st MRB]

I'm resurrecting this from the dead.

Why?

I'm curious - did this ever happen?