First feedback - 2 ideas to improve Laracasts/discuss
Hello everybody,
I discovered Laravel & Laracast one month ago, fantastic tools & community. I'm more sysadmin today than full stack dev, but it can change :-)
I share with you two ideas to improve Laracast/discuss
Too many people do not close their questions, and worse some open ~same post without closing the first one and even without any comment explaining the reason.
We cannot force sb to close a subject but we could tend to have less unsolved subjects by allowing only a limited number of unsolved posts per user.
What do you think of these ideas?
Other ideas?
Is there a place to send them? it should be good to have a place where users can vote on subjects in order to see the priorities.
Last but not least, as I go ahead, I write a script (bash) to automatize the construction of the basements of Laravel apps with different options (db type, global crud, ui type, auth or not, type of menu, tests, ...
It's also usefull for a newbie, like me, to move step by step and to be able to compare easily different options.
I have 2 questions :
Does sb know a similar project?
I have allready 2000 bash lines, not sure than it is the best langage, any idea?
@oxbir is an AI robot designed by jeff to test the patience of top contributors. After passing the test they attain the badge 'Suffers Fools'. @automica qualifies.
Some questions are unsolvable (they are just bad questions) and OP should not be coerced to select a best reply when there isn't one. Some platforms close questions, but there are definitely cases where people can contribute a new solution to an old question. This is useful for those searching for a solution in the future.
Personally I don't see an issue with the question being marked as unanswered. After a while you realise who the time wasters are and just leave them alone.
Last, I would not spend a lot of time on this. I build a new project every couple of weeks and I'm always starting from scratch with a different set of requirements and a rapidly changing landscape of available tools. I doubt you would see payback on your time.
@oxbir is not for me ... for the moment and a long while more
there is no bad question, or even bad question can have best answer like "this question should be reformulate lije this and see the new post ..." or ... in fact it's only some rules again I don't disagree with yours.
for the last point, it's my way of working, too long to remeber every thing, it's like writing personal notes of whatever doc you like.
@snapey thanks for the badge suggestion. I would really like that one.
I will always 'suffer fools' as I have had to self learn throughout my whole career (and have been a fool myself as @michaloravec once told me).
Very often the solution is easy once the problem has been correctly identified.
One my recent light bulb moments came from when http://xyproblem.info/ was posted earlier in the summer. (apologies as I cant recall who posted it). I recommend everyone to read it if they haven't seen that link before.
@sr57 in regards to your 'automize' I wonder if you have seen https://github.com/laravel-shift/blueprint ? This allows a means to build out an entire Laravel app by defining it in config. Might be a useful tool in your quest for rapid development.
Ref your point 2, your suggestion seems to indicate that the forum needs moderators. Its never had any, and I doubt will ever have. The person posting the bad question does not realise how badly structured their question is.
Communication is always a difficult art, I fully agree with you, good forum do not need moderator, but good rules, my sentence begins by there is no bad question.
What about the spam button on this forum? A (light) moderator :-)
OP should not be coerced to select a best reply when there isn't one.
Of course yes, but OP can write by themselves the best answer with the help of the community, and a best answer can be 'I reformulate my question ...'
Could you give me any hints as to what a good structured question should look like? e.g
Presumably going through what I'm trying to do.
What it is I think is going wrong along with errors run into.
What I have tried so far.
It would be helpful for those of us asking the questions as a reference, to make it as easy for the people that know this stuff and are trying to spread the knowledge.
@adam_anything I don't think there is 'absolute good' questions, some of us like short texts, others longer, other images, others examples .... we are human ... so with many differences*. But with examples from @rodrigo.pedra all of us can write better.
*For instance I understand @snapey when he prefers to not close a subject, but personally I prefer to close with comment and to re-open a new post that we can link to the first one if needed. It's 2 different first ideas and I'm sure that with more discussion and methodology **we can find a common solution.
**first it's to share a common pb and define it's urgent or not to work on it.
In this case there is no urgence and we have not define the pb :-)
That said, many people want quick solution and not approach to find the solution by themselves ...
Have read the first four and bookmarked them all to reference when I'm looking for help, that last one I will need some more spare time to read right the way through but will get to it.
