PostIts (Messages)
| Thumbnail | PostIt | Date | Balance | Answers |
|---|---|---|---|---|
|
RDF and Cosmos DB
Can I use Azure Cosmos DB as a triple store for semantic web RDF data? |
2018-01-26 | $0.00 | 0 | |
|
JMESPath check it out
http://jmespath.org/ Send all answers that come to your mind |
2016-12-18 | $0.00 | 0 | |
|
Protocol Buffers
message format https://developers.google.com/protocol-buffers/ |
2016-12-18 | $0.00 | 0 | |
|
Null Pointer Exception
Why can't the compiler tell me which object or property is actually null? It would help me a lot. |
2016-07-29 | $0.00 | 0 | |
|
what is the csproj.csdat file for
http://stackoverflow.com/questions/33431221/what-is-the-csproj-csdat-file-for |
2015-11-13 | $0.00 | 0 | |
|
MoSCoW
The categories are typically understood as:[3] Must have Requirements labeled as MUST are critical to the current delivery timebox in order for it to be a success. If even one MUST requirement is not included, the project delivery should be considered a failure (note: requirements can be downgraded from MUST, by agreement with all relevant stakeholders; for example, when new requirements are deemed more important). MUST can also be considered a backronym for the Minimum Usable SubseT. Should have Requirements labeled as SHOULD are important but not necessary for delivery in the current delivery timebox. While SHOULD requirements can be as important as MUST, they are often not as time-critical or there may be another way to satisfy the requirement, so that it can be held back until a future delivery timebox. Could have Requirements labeled as COULD are desirable but not necessary, and could improve user experience or customer satisfaction for little development cost. These will typically be included if time and resources permit. Won't have Requirements labeled as WON'T have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, WON'T requirements are not planned into the schedule for the delivery timebox. WON'T requirements are either dropped or reconsidered for inclusion in later timeboxes. (Note: occasionally the term Would like is substituted, to give a clearer understanding of this choice). |
2015-11-13 | $0.00 | 0 | |
|
Add tags to Wortraum
Just quick fix to evaluate later. Add new Knoten to 'Inhalt der Nachricht' |
2015-09-11 | $0.00 | 0 | |
|
YaCy: dezentrale Suche im Internet
Die Besonderheit von YaCy ist aber, dass es sich mit den anderen Benutzern, die ebenfalls eine YaCy Suchmaschine betreiben, verbinden kann. So entsteht ein vollständig dezentrales Peer-to-Peer Suchmaschinennetz welches mit der Anzahl der Nutzer skaliert. Diese, von der Gemeinschaft der Nutzer betriebene Suchmaschine ist nicht zensierbar und speichert auch kein Nutzerverhalten an zentraler Stelle. Das Erreichen von Informationsfreiheit durch freie, dezentrale Suchsoftware ist auch ein Projektziel. |
2015-05-31 | $0.00 | 0 | |
|
Git branch changes
I have a clean git checkout, my local master branch.<br /> I created a new 'dev' branch on top of it.<br /> There I started with several feature branches.<br /> Then I wanted to merge <i>down back to dev</i>. <br /> But there were <b>uncommitted changes!</b> I never touched this branch. <h2>How comes?</h2> Please provide me with possible explanations, answers, ... |
2014-10-24 | $0.00 | 0 |
|
Full Document PostIt please
Offer this communication logic for all kind of documents. Research paper as well as blog articles |
2014-09-19 | $0.00 | 0 | |
|
|
Coole Muhle!
Auf der Seite kann man ein eigenständiges Windowsprogramm (.NET 2.0) herunterladen. Damit lassen sich viel intuitiver die Nachrichten verwalten und Markierungen erstellen:<br /> <a href="http://agent.oli-it.com/" >http://agent.oli-it.com</a> |
2006-03-14 | $0.00 | 0 |
|
NOTRUF 0190 110
fick gleich los |
2000-07-15 | $0.00 | 0 |