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 8 years ago.
Improve this question
I am currently reading "REST in Practice", which is getting a bit long in the tooth by technical book standards (2009), but it came highly recommended to me as a book that still has a lot of pertinent information for today's world. One of the topics that has particularly caught my interest is the use of Atom feeds to publish events.
Reading the chapter focused on Atom got my very excited to look into replacing the home-grown/custom solution the company I work at has developed to solve the same problem (delivering a feed of events over a RESTful API)...however, I started doing some follow up research and found that development/interest in the various Atom libraries out there (like Apache Abdera and ROME) seem to suffer from dwindling community interest.
Is Atom still being used for this purpose (event feeds), or has another solution come into favor?
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 8 years ago.
Improve this question
I know this as been asked but couldn't find an answer that I understand...
Some people told me about the main thing are sagas, but it doesn't look such a big advantage to make me spend my bucks on NServiceBus when I already have MSMQ....
That's a little bit like asking "why do I need ASP.NET MVC when I already have HTTP?"... a little tongue-in-cheek, but still with a lot of truth in it.
NServiceBus gives you message serialization, a sensible threading model, routing, and several ready-to-use messaging patterns out of the box.
MSMQ gives you... message queues! And a fairly complicated API with many low level options that give you no real pit of succes...
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
I'm currently working on an enhancement for a commercial utility that involves annotations with respect to LeadTools v13. In terms of LeadTools, it would appear that most things start off with the raster object, but without documentation for V13, it's somewhat of a challenge to make heads or tails of how to proceed in terms of reading the annotation files in.
If anyone has any code examples for such an old version, any help would be appreciated.
LEADTOOLS support don't have online documentation for this old version of LEADTOOLS. However, our help files shipped with the toolkit includes code examples for most of our functions including the annotations functions. You can find our help files in the following folder:
[LEADTOOLS 13 Folder]\Help
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
What is the best way to write the system requirement specification. Definition is given to me. project scope is very heavy.
Which model should i approach to get the detailed requirement from the client ?
Which are the common mistakes while gathering information from client and writing specification ?
Help appreciated.
First of all, you have to have a background in requirements engineering. As a start, look at the Volere templates, that help to organize the requirements in a meaningful way. The authors (the Robertsons) have written a book "Mastering the Requirements Process" (ISBN: 978-0321419491), but there are of course a lot of other authors.
There are a lot of techniques to get requirements from the customer, and it depends on how the customer behaves, in which area he is under way, and how much experiences he has there. It is not possible to give here any advice.
I don't think that there is a list of common mistakes that could help you in any way. Get an experienced requirements engineer, and follow his steps.
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 8 years ago.
Improve this question
I currently use Kile to edit LaTeX documents. I don't like kile for a couple of reasons so I was thinking of trying to learn how to use texmacs. I have been through a tutorial for emacs which I am now getting to grips with. The documentation for texmacs and auctex are pretty weak in terms of explaining how to install and how to use those things. A quick google search didn't show up any friendly "how-to"s on this topic. Are there any resources you can direct me to?
I'm a bit puzzled by your question. I use Emacs+Auctex on Windows, Linux and OS X machines and have never had any problem installing them. I'd suggest heading to http://www.gnu.org/software/auctex/ and following the instructions. If you have any more specific questions post again.
sorry I can't help you with TeXmacs, I just wanted to note that this program isn't under active development for quite some time now. If you look at the homepage the copyright notice is until year 2003!
If you are looking for a more GUI oriented LaTeX editor I can recommend LyX. Emacs+AucTeX is of course wonderful, but it has a certain learning curve.
However if you plan to learn Emacs or are using it already, than you should definitely go for it!
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
Developing software solutions which already exist and are available for re-use (either commercial or open-source). AKA "re-inventing the wheel".
Same as above, but your solution being broken. AKA "re-inventing the square wheel".
Developing solutions for problems which do not exist.
Again, I'm interested in a more formal approach, e.g. TRIZ
Doing some research beforehand (1) and investing in solid software architecture (2,3) usually helps :)
When you're planning to develop something you always need to calculate the benefits of doing some and the things like the ROI.
You could read more about this in Agile Estimating and Planning by Mike Cohn
Local Market Research
Internet Research
Google Metrics (Seeing what the Google Count is)