Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Last year I received two "Technical Support Incidents" in the iPhone developer program, but when I went to renew I found that I would lose them. I have another two for this year, but I'm not really sure about the kind of problems that can be solved by using them.
What kinds of questions are the best use of these Technical Support Incidents? What is the kind of problem I can use them for? What do you receive when you use them? Thanks.
Technical Support Incidents are for when you need code level support for a project you are working on. If your code is hanging up on certain pieces of hardware, or you need help diagnosing a bug in your system, then you can contact the Apple Engineers to help with the particular problem you are having and they will help to resolve the issue.
Notice this is different from a bug in Apple's systems, which is what the bug reporter is for. This is when you need help from Apple to track down a solution to a problem you are having in your code.
I have personally never used it, and with sites like SO, doubt I will unless I hit one of those one in a million edge cases where I code myself into a corner.
More information is on Apple's website.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 days ago.
Improve this question
I hope someone can help me out here. I came across the website https://pebblely.com/ and was really impressed by their ai generated backgrounds of product photos. They have an AI-powered feature that allows users to upload an image and have the background automatically generated.
I am curious to know more about the AI technology behind this feature and was hoping someone could shed some light on the subject. Specifically, I would like to know:
Which AI technology is being used for background generation on https://pebblely.com/?
How does Plebbley.com integrate AI into their product photo generation process?
i tried using the dall e api for product photo generation but this did not work out well since the ai is modfying the actual product aswell.
Then i came across plebbley.com and saw it work perfectly fine.
I think i can only be a combination of stable diffusion and dreambooth since uploading images on stable diffusion is not supported.
Any information or insights would be greatly appreciated. Thank you in advance for your help!
thanks a lot!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am in the market for a raspberry pi or alternative. I've done quite a bit of research but I can't find a raspberry pi alternative that is both more powerful, but also has the same community and add on options. So, can anyone suggest an alternative?
Note:I want one for recreation, I.E. building a robot arm, but I also want to run a low scale server.
Thanks in advance!
I love following #cnxsoft on Twitter and his blog at http://www.cnx-software.com/.
I suggest you to go to his blog and see tags like http://www.cnx-software.com/tag/development-board/ there is every week at least one new board with more and more powerful processors and lower prices... Find one that fits your needs(OS, Pins...)
I'm also not sure why this is marked with tags like "xamarin-studio" :)
I am not sure if this is the right forum, the scope seems too broad. So don't be surprised if this is closed as offtopic.
Can you say what alternatives you have looked at so far?
Try looking into the following and see if they fit your requirement :
http://arduino.cc/en/ArduinoCertified/IntelGalileo
http://beagleboard.org/black
I think you are thinking of the bananapi, or the hummingboard.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
It sounds strange, but that's what I need. An effective way to document a Scrum project.
I agree that it's a waste of time to produce User Stories and a Requirements Documents.
But sometimes we need to have the vision of how the software currently works.
How do you do that? Do you know some best practices or case scenarios on this?
Thanks
The short answer is this: you can write anything you want or need to about any project, Scrum or otherwise. Scrum doesn't tell you how to document, but it doesn't tell you not to. The way you document is in itself irrelevant to Scrum.
That said, if you need to understand how the software currently works, a document will not help you. Documentation often lies. If you're trying to understand how the system works, a document will only tell you what people think or want to believe is the truth.
What you should consider, is to use executable specifications and Test Driven Development to prove that what you believe the software does is actually true. automated tests combine documentation, examples and regression tests all into one offer.
There are several kinds of documentation that can help you. It depends on your context which ones you need, and at what detail level. You could also use a tool such as MOOSE to create project specific visualizations of your software at all levels. Some simple documents are:
A story map
Gherkin style high-level features and scenarios
If you've tracked your product backlog items through completion, including acceptance criteria for each you should be able to point to the list of completed product backlog items as documentation. Everything you've programmed should be associated with a PBI, so the completed PBI's document your project.
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
Can anyone give advice, or point to any guides, on how to manage a community of open source software developers in writing api documentation?
A typical, unmanaged, starting point for most projects is to have a project wiki where anyone can freely create pages, add content to existing pages, edit existing content etc. The problem is that, despite people's best intentions, the wiki can easily end up being a disorganised, poorly written, incomplete, written in disparate voices etc etc.
So, what to do to improve the quality of the documentation?
I suspect a key ingredient is clear editorial/style guidelines, something similar to http://en.wikipedia.org/wiki/Wikipedia:Encyclopedic_style#Information_style_and_tone. Can anyone point to an example of such a guide tailored specifically to software apis?
Are there any other practices that people have found useful? E.g. form a core team of editors and accept that most documentation that gets added by the community will most likely need to be 'strongly edited'?
The short answer, that the solution is social/human and not technical. The way to get good documentation for any project is to have someone with time, in charge of doing high level organization for the documentation, and then being involved in the development and user communities to ensure that the documentation remains up to date and continues to address the problems and confusions that users typically have.
Community projects have accepted that you need point people (i.e. "managers," for aspects of the project like "translation," and "release," and for various components. The same thing needs to happen for documentation.
As for tools, Sphinx is really great though it's not "wiki like," exactly you can use whatever version control system your project is comfortable with to store documentation and configure your web server to rebuild the documentation following commits/updates/pushes. Which has always worked just fine for any project I've worked on/with.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Perhaps if I make the my documentation better I could spend less time supporting developers and more time developing myself:
I develop a critical platform used by 10 other developers and 50 end users. The developers are of mixed ability ranging from domain-experts to relative beginners. Since I'm one of the people who know how the core platform works support requests from other developers usually go via me.
Our documentation is the usual sort of descriptive stuff any mature project will have: We have a large wiki containing details of all the usual operating procedures plus extensive API documentation.
Unfortunately it does not cater well for "how do I fix " type questions:
Would it be possible to make some interactive fault diagnostic documentation that puts users through a standardized fault-finding routine. The documentation would ask users a series of questions, and depending on the user's input would tell them what to do... it would be a very simple expert system, or possibly a documentation state-machine.
The idea would be to help newbies think more methodically about diagnosing faults in this complex system.
My question:
Are there any free tools intended to implement this kind of user-experience? I'd rather not hand-roll this. There must be some kind of framework for interactive help & documentation.
Has anybody implemented this kind of system before?
If you just wanted to have a flowchart/stat-machine thing where the user moves from the start point to a set of possible solutions by answering questions, then you could probably implement this as a set of wiki pages, where the possible responses to questions on one page are links to other pages.
This solution relies on being able to represent the answers to questions as links, which isn't going to work if the information is more form-like. For example, suppose one question is "What brand of graphics card do you have?" where the answer is one of 300 possible options. In this case it's going to be tiresome to create the links :)
If the developers are asking too many questions then I would suggest making them research the question themselves and come up with an answer, then double-check with you instead of encouraging them to ask you every time. It's much easier to ask somebody else than to find the answer yourself, but they're never going to learn if they don't look for themselves.
If the users are asking a lot of questions then you may need some user interface improvements. Try putting hints in the application itself at the top or bottom of the screen maybe.
For both groups of users a wiki can help.
a FAQ in your wiki
if an error happens too often, try preventing it or output a more useful error message (like "if this happens, the likely cause is that...)