Frankly, I really liked RubyMotion. It doesn't save you from necessity to learn Cocoa touch, but it just makes the experience much more interesting with Ruby. The whole process was very very simple.
I hope it will make things easier, or at least would server as a collection of code snippets "how to" :-) Let me know if you have any questions, or would like to have something beyond what you see there. Feel free to email me (http://alexeypro.com) or just simply contribute to the project.
Thanks!
Hard to say if it's a common choice. I've had few projects where Node.JS was the choice of backend, and MySQL was the database, because our frontend was PHP/static HTML/CSS/JS stuff. DB is not really important. Node.JS shines on the backend, and it doesn't really matter to what it talks to. MySQL can be decently fast, but you can as well use Node.JS solely with, say, Riak or Mongo, or just Redis?
In this "crud-bones" project I am use Redis as a cache layer, but you can use it as "storage" as well...
That's definitely something what I don't want to do. Not that it's bad, or something.. just it defeats the purpose of this app. The goal is to have some skeleton or base to start your own stuff. There is no reason to make it so flexible so it'll generate all that stuff. Besides, as you can see, my app works with Mongo or MySQL DB by simply changing ONE SINGLE LINE of the code. Which is kinda cool, I think. No ORMs, no special "preparations". A little bit work on the model class, and you are done.
Besides, I mentioned that already, we all know we are going to change this code for our own needs. So it needs to be simple, straightforward and interchangeable. That was my goal.
I am glad if you found it helpful, and happy I didn't sit on it.. yeah, it's far from been all shiny and polished, but the intention is to get basic Node.JS CRUD project up and running, so you can focus on actual project's goals, not (while simple but still time-wasteful) basic implementations. Especially if you need to wire together DB connections, Express, EJS, ...
Actually, I don't -- I am trying to keep the app extremely simple, and straightforward. I don't want new Rails app, neither want Java-style-framework. All of us are going to cut it back and forth to make to suit our next project needs, so why bother?
The switch between using Mongo and MySQL -- is just using different DAO -- https://github.com/alexeypro/crud-bones/blob/master/src/api-...
I kept the "interfaces" (yeah, not interfaces but contracts, 'cause JavaScript has no interfaces, but you know what I mean) same, and that makes the switch EASY.
In short-term plans I want to update README as for the deployment instructions to other Node.JS hostings, and probably throw some simple caching layer on top of Redis, and definitely some unit testing. Then it should be all set. Just basics to get me up & running with new backend effort :-)
Frankly, even those things are not necessary. They will make the app more complicated, but let's be honest -- we use Node.JS because it's lightweight and minimalistic approach, so why create an ugly-beast-which-does-it-all-its-own-way?
if you would spend few minutes of your time looking what Andrew Warner gives for free on Mixergy you'd probably never ask such stupid "serious" question.
Thanks for this valuable feedback! Want also to mention that if any of you will be hiring, or will need some help with screening -- use us! Register now (http://www.strawlink.com/referrer/hackernews) and you'll get your accounts credited right away. We will be turning off the new registration credits soon, but I want to say that if any of you will need Strawlink and will not have money to spend -- let me know -- [email protected]
I will do my best to help. As I mentioned before - Strawlink's goal is to help facilitate the screening process, and if we will learn how to do it better -- all of us will benefit. Everybody who create new jobs opportunities, and everybody who is looking for a job.
As for the Product Tour -- we'll try to "light" it up a little bit, so it will stand out on the page. Thanks for the advice!
As for the screening -- we've been talking to many recruiters, and usually they used the term "screening" as a process before the initial and face-to-face interviews. This is the step when it's only required to separate unqualified candidates from others. People just tend to submit resume even if they clearly are not a fit (by different research papers it states that more than 80% meet less than half of job requirements).
You may be referring to "criminal/drug screening" or "pre-employment screening" processes, which are more like verifying the information provided by the candidate.
But it's good you brought it to our attention -- we'll figure out how to put some "hint" about what we are actually mean by "screening" on Strawlink.
1) just answered it below (http://news.ycombinator.com/item?id=560420)
2) that's our priority, and we really need somebody, but being busy with the development/support we still have this problem
Actually, we figured out that $1 is pretty right price for the value we provide. We have more features in mind, and we are thinking about something like premium membership charge to enable them, so we can make some profit from there also.
But we do not want to raise the price. At the end, it's the service to _help_ people when they are hiring. We are targeting every single, even 1-2 people, company. When they need, say, Ruby or Java developer for their own particular needs, they want to be able not to waste time (they have business to run!) but simply to figure out the most important moments about all candidates. It may be years of experience, how well they know the language, which frameworks and databases did they use and how long, etc. Crawling through cover letters, resumes, etc. definitely can do the job, but it is nor time effective, neither money wise.
You always can find something cheaper than that! You may want something more expensive for the kids, but for healthy adults you can pretty easy get away with like $300-350 for both -- use sites like ehealthinsurance and others -- they can do comparison for you. Of course, if you have some medical conditions/etc. - that can be an issue, as then the cost of insurance will be sky high.
After all, yes, health insurance IS expensive, but you can find the cheaper options. But well, the same way you can think about your rent, groceries, etc. You have to have them, and you have to pay for that.
I don't think so. Again, it's only me, but did you try Spring/Hibernate with annotations? There is really not much sense for an experienced Java developer to jump into Groovy. I do not see it, really. Scala is good, as a language. Syntax is horrible, but some people adore it. ;-) Why Groovy? It's been around for a while. Sometimes it's all about momentum. I have doubts it will get another chance to shine with SpringSource or anything else. Just too many other options available around. Why not Jython/Django? Why not Jruby/rails? Still Scala/Lift. It's all in JVM.
I know couple friends who are using Java applications and combine nicely with Groovy/Grails, though, as for the trends -- it's loosing it's place. I hear more and more about Scala/Lift -- but personally do not like Lift. It's not ready for the prime time (in my opinion) -- very young and productivity not even getting close to PHP/Symfony or Ruby/Rails.
Why would you choose Grails? Scala does better integration with Java. JRuby works fine in container too. Is Groovy superior language? I have doubts. Just another one. Not too popular, even.
I do not think that there is something embracing in doing PHP coding, but I would choose Zend probably. Symfony's productivity is high, but performance - in many tests it goes beyond (slow by itself, we all know that) Ruby/Rails. Zend is good, but with more flexibility it gives more chances to make mistakes. ;-)
Enterprise applications mostly run with Java, no matter what. ;-)
I can hardly speak for everybody, but I know for sure: 1) life is too short just to work for nothing 2) shit happens 3) may be your business model need to be concentrated on profit now, less on investment
But it depends if you are interested in pure methodology, or you want to see some example of applying it in software/Web development with PHP/Java/RoR/...
From my experience, I found helpful next books:
"Test Driven Development: By Example" by Kent Beck
"Agile Software Development, Principles, Patterns, and Practices" by Robert C. Martin
"Agile and Iterative Development: A Manager's Guide" by Craig Larman
"Agile Project Management with Scrum" by Ken Schwaber
"Agile Software Development Ecosystems" by Jim Highsmith
Those are pretty "technology independent". Helpful to understand the idea. And the authors are respected and well known in the community of agile developers.
If you work with RoR (which is popular choice nowadays) you may find "Agile Web Development with Rails" by Dave Thomas and David Hansson interesting, but it does not cover "agile methodology" itself too wide. But it does give a good overview of practical usage. Anyhow, personally I still prefer to learn theory before practice, but many people see it working for them ;-)