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 2 years ago.
Improve this question
So a week ago I started learning Golang by my own. I wanted to make like a Google drive web application. I learned the basics but there is one thing that I don't understand: project structure.
I searched for information about how to structure your project but I finally got confused because some people say that I have to create something like: github.com/myuser and others that I have to create 3 different folders (bin, cmd and pkg).
Could anyone give me some hints about how to structure my web project? Help is much appreciated.
You can always start small with the MVC pattern. No need to make life anymore complex than it needs to be. I usually start with a models, controllers, views, assets, router, directory and a main.go file. The structure of a project isn't important. What IS important is that YOU can understand your code and know what each section and file does.
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 5 years ago.
Improve this question
If I wanted to create a small program, perhaps a calculator or something, what language would I use, and how would I implement it?
Very new to coding, especially with websites so sorry if it's a dumb question.
This is a very vague question with so few specifics that it could really be answered 1,000 different ways.
To get you started with your reading though, I would suggest you read up on the differences between server-side and client-side coding languages for the web. That will help you understand what languages you would want to use and for what reasons.
As a general rule though, most people would likely build a simple app like a calculator in javascript, as it doesn't require a lot of interaction with the server, doesn't utilize any data storage, and would run on the users machine rather than tie up resources on your server.
Happy learning, and if you want a lot of responses on this site, you should include more specifics in your questions. Such a broad question is very hard to answer with any sort of brevity.
You can start with HTML, CSS and Javascript. www.w3schools.com is a good source to learn HTML, CSS and Javascript.
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 5 years ago.
Improve this question
I've been developing a small database for my summer internship and I need to write a manual/documentation for it aimed at both users and developers for future use. Thing is...I have no idea where to start or what information to include. Many people I work with have no idea what databases can do so I need to keep it as simple as possible. The database is implemented in Access and I experimented with the database documenter but I think that is overkill. Is there some kind of documentation standard that I can follow or anything of that nature?
As a starter for ten, I'd have thought that the user documentation should be task orientated.
(i.e: How to achieve 'X'.)
In terms of the developer documentation, defining the meaning of any non-obvious fields in your schemas, how they're used and the relationships between different tables, etc. would be a good start. (I'm presuming your VBA code is well commented, etc.) You may also want to examine the existing "Documenting Visual Basic with Doxygen" question/answer.
Just straightforward english if you are explaining a process.
If you have a series of Macros do a document highlighting to code used in each macro and the order it should be employed. This could aid someone down the line if they are trying to automate the process.
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 7 years ago.
Improve this question
I am involved in a project which is meant to eventually become open-source and have a code contributor community. Is there any "right" way of doing this and what should/can I expect?
Thanks
There's a pretty good book on this topic, Producing Open Source Software by Karl Fogel, which is available for free online or in dead tree form if you prefer to read it that way. It would be hard to expand much on it in a single answer. Every project will, of course, be different, so I'd recommend reading that book, and then asking more specific questions about your particular project; answers will depend on the language and platform you use, how active an open source community there already is in your area, what your business model is, and many other factors.
I would recommand using Github or Google Project Hosting (subversion/mercurial), and of course use social media network to promote the project helps too.
You can start something like this - http://wxwidgets.org/develop/
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 9 years ago.
Improve this question
You can see lots of briliant ideas in Open source projects. How authors found these ideas whey they don't exist yet?
Should I learn software dynamics, history and trends(Nothing new under the sun?) for that?
I don't want to start another github project called "API to xyz". What should I do??
Scratch an itch. Find something that you feel is a problem or annoying and write some code to solve that problem. Chances are you aren't the only person who is affected by that particular problem.
I believe a lot of software projects, open source or not, start as someone identifying a demand and working to supply it.
Think you're not satisfied with wherever photo management apps you found. Starting (or forking an existing one) with your needs in mind is an option.
What kind of software you would like to use but can find one that suits you? If yours needs are more or less supplied by already existing applications, why not working on improving one you like most?
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 7 years ago.
Improve this question
I want to start an open source project, but my favourite project name was already used for a framework with the same goal. This project was never popular, there is nothing to download or executable, the project had only two active days with commits at Google Code and is dead since four years. In other words: the project is irrelevant but the name is in use at Google Code and ohloh (the same dead project). The .org domain would be available.
Would it be ok to reuse this project name?
4 years, just 2 active days? Get it and make it better then old dead one ;)
I would advise against it, even if it is clearly dead. Recycling old names can cause a great deal of confusion. Moreover, if the old project has been indexed, then searches for your project or for documentation for your project could accidentally turn up information related to the previous project. There are plenty of good names out there that haven't been taken. Better to brainstorm now than cause confusion later.