Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Although this is more of general question but it will extremely helpful for newbie like me to get the benefit from more experienced people on stackoverflow. I have read the ColdBox wiki ColdFusion best practices. I have searched same for the CFWheels but couldn't find the same. So I was wondering what are the best practices while using CFWheels framework?
This is too broad of a question for StackOverflow, but I can recommend that you watch these screencasts:
DBMigrate Create Operations
ColdRoute Plugin
Series: Basic CRUD Operations
Using DBMigrate to generate your database is a great way for team-based development. And ColdRoute adds so many nice conventions for routing that it affects how I do development in the controller layer in some big ways.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I am working in a microservice architecture ( my first one ), in Golang, and I find myself duplicating Models definition over several services.
What can I do to avoid this?
I can only think to implementing a shared library with all my model definitions but I can't evaluate pros and cons. Can you tell me about other ways to solve this issue?
The idea you already mentioned can't be that wrong. When you have a set of services sharing the same models, it can be a good idea to extract these models into an own package/module.
We decided to do this in a Java-Project a few months ago and it made things a lot easier. Especially when your services are decoupled used some type of messaging/streaming, you absolutely have a set of common entities they need for communication.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I want to build a website with a chat. The chat should have a calling option,stickers,smiley faces.Which language would you suggest and why?
I`m thinking about ruby on rails or node.js
I am also thinking to find someone who maybe have experience in the
area, but i am not sure what kind of developer would suit me best.
Language choice depends on how many hours you want to spend on development and further support.
Node.js is a simple and fast option if you want to build a working prototype. If you want to build something with a future advance (in order to solve such issues as scalability) and you have more time you can look at Golang and similar languages.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
stackoverflow community. I'm new here and I just started learning how to code in ruby with the goal of making a twitter widget maker. Do I need to learn any other languages to make it work?
Thanks a lot in advance,
Ghilia
Do you know any html, css, or javascript? These are essential in creating just about any custom web content.
Also, have you considered following along on some youtube tutorials?
Here are some that really helped me out in using different rails gems when I was starting out:
https://www.youtube.com/watch?v=7-1HCWbu7iU&list=PL23ZvcdS3XPLNdRYB_QyomQsShx59tpc-
And finally, Michael Hartl's tutorial :
https://www.railstutorial.org/book
Hartl actually builds a twitter app. Incredible tutorial but it can take months. He uses very little external libraries. This is considered one of the best web application tutorials ever made.
Good luck!
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
i am new to the web and i understand that MVC is very important to web development. I'd like to do a project that could help me understand the MVC.
Plus, I also can't clearly understand what it is actually. i mean i can't find any good lesson or article that describes to the n00b. so if you guys could help me in that matter too that would be most appreciated.
Thanks in advance.
Start with CodeIgniter. It is a great MVC framework written in PHP. While you build a site in it, you can look at the code and learn how it works.
But remember, as with each design pattern, using it should not be a goal per se. Using a design pattern can help you find and build good generic solutions, but you shouldn't feel too bad if it doesn't work out exactly as you'd like. You'll learn and do better (or differently) next time and you're always free to skip or alter the pattern. It's just a tool.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I want build an application by using the framework.
the application contains two parts: the Back-End and the Front-End.
Everybody who have experiences can suggest me which ways should I do?:
Develop the Front-End first Or Develop the Back-End first
Or give more tips on the start up project?
thanks
I usually start with the backend to get the major functionality implemented, but even so, it's pretty much inevitable that the frontend and backend will have to be developed at the same time at some point in the project.
People can say what they want about separating presentation and functionality, and that's a good principle, but the reality is that the presentation influences the functionality and vice versa.
You might get the backend mostly written, and then you make the frontend, but you will probably decide to change some things and end up working on both together.