{"id":2090,"date":"2020-06-30T00:00:00","date_gmt":"2020-06-29T22:00:00","guid":{"rendered":"https:\/\/www.strehle.de\/tim\/?p=2090"},"modified":"2025-09-04T16:50:08","modified_gmt":"2025-09-04T14:50:08","slug":"tweets-2020-q2","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2020\/06\/30\/tweets-2020-q2\/","title":{"rendered":"Tweets 2020 Q2"},"content":{"rendered":"\n

2020-06-29<\/a>: \u201cDon\u2019t use Event Sourcing unless you have a complex domain that has to deal with a lot of users working together on the same entities. [\u2026] Don\u2019t ignore NoSQL as an alternative. [\u2026] Don\u2019t use the domain events as a communication mechanism between domains or services.\u201d https:\/\/www.dennisdoomen.com\/2020\/06\/guidelines-event-sourcing.html<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-24<\/a>: Excellent, in-depth presentation of the @FinancialTimes<\/a> image workflow by senior dev Andrew Watkins, with a focus on image usage rights: https:\/\/www.youtube.com\/watch?v=Npo9EAODqnw<\/a> #DAM<\/a> (I hope one day I\u2019ll be able to hold a presentation with a slide named \u201cHow we solved the rights problem\u201d, too\u2026)<\/p>\n\n\n\n

\n\n\n\n

2020-06-23<\/a>: The @Brandfolder<\/a> product timeline is the most beautiful way to write a ChangeLog: https:\/\/brandfolder.com\/product\/timeline\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-23<\/a>: \u201cThe headless CMS promised the utopian ideal of all digital experiences under a single roof [\u2026]. But the reality leaves much to be desired. Developers have had to reinvent the wheel and rebuild editorial workflows and content processes that formerly came off the shelf.\u201d https:\/\/www.cmswire.com\/web-cms\/why-we-need-a-new-grand-compromise-in-content-management-systems\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-15<\/a>: \u201cWill employees spend the time and effort to associate documents, emails and events with topics? Even if employees do invest the effort, will they be able to apply topics uniformly enough? Will the topics defined by subject matter experts and knowledge manager be intuitive?\u201d https:\/\/www.cmswire.com\/knowledge-findability\/microsofts-project-cortex-wants-you-to-hire-a-knowledge-manager\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-18<\/a>: Nice article, providing context for the \u201cretrospective prime directive\u201d (\u201cwe must believe that everyone did the best job he or she could\u201d): https:\/\/www.emergn.com\/insights\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-16<\/a>: \u201cIdeally, the system will be advisory in-nature and will not block users from uploading duplicates (however strictly you want to apply that definition) but more makes them aware that there are other assets which are similar so they can make their own decision.\u201d https:\/\/digitalassetmanagementnews.org\/dam-education\/the-same-but-different-understanding-the-implications-of-duplicate-asset-detection-functionality-in-dam-systems\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-11<\/a>: You want to run your news Web site on the same tech that powers https:\/\/www.spiegel.de\/<\/a>? Now you can! Built by the amazing SPIEGEL Tech Lab team: https:\/\/devspiegel.medium.com\/polygon-wie-die-modulare-architektur-des-neuen-digitalen-spiegel-funktioniert-e6e8f90d7915<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-06-08<\/a>: I love learning new stuff, and a lot has changed in Web development, but somehow PHP on Linux remains my main programming environment since 1998 (PHP 3.0). Nice #PHP25<\/a> timeline: https:\/\/www.jetbrains.com\/lp\/php-25\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2020-05-29<\/a>: Note to self \u2013 how to run Nginx locally via Docker, serving the current directory as http:\/\/localhost:8080\/ : <\/p>\n\n\n\n

docker run -it --rm --name nginx-test --volume \"$PWD\":\/usr\/share\/nginx\/html:ro -p 8080:80 nginx<\/code><\/pre>\n\n\n\n
\n\n\n\n
2020-05-27<\/a>: It\u2019s always funny how, mere days before the launch of a project that\u2019s been going on for months, some stakeholders \u2013 who so far ignored all requests for input and feedback \u2013 wake up and request major changes.<\/p>\n\n\n\n
\n\n\n\n
2020-05-25<\/a>: \u201cThe relationships that are created by sharing, integrating, embedding and linking may be very difficult to migrate from one application to another.\u201d https:\/\/www.mediagraph.io\/blog\/software-independence<\/a><\/p>\n\n\n\n
\n\n\n\n
2020-05-24<\/a>: \u201c\u2018On our roadmap\u2019 is similar to the way young children will tell you that they intended to tidy their bedrooms or finish school homework etc. but haven\u2019t actually done it yet. [\u2026] The low risk assumption is that feature X will never exist in their product.\u201d https:\/\/digitalassetmanagementnews.org\/vendors\/three-fibs-that-some-dam-vendors-tell-and-how-to-deal-with-them\/<\/a><\/p>\n\n\n\n
\n\n\n\n
2020-05-20<\/a>: \u201cThe interesting thing is that for many top developers, their sharing mindset came before their success, and was the direct cause of it, not the result of it.\u201d \u2013 Ben James https:\/\/stackoverflow.blog\/2020\/05\/14\/the-most-successful-developers-share-more-than-they-take\/<\/a><\/p>\n\n\n\n
\n\n\n\n
2020-05-19<\/a>: I stuck with an outdated NetNewsWire version way too long \u2013 now I follow RSS feeds via @feedly<\/a> (to find content for @PlanetDAM<\/a>) and it works great. The search for feeds by Web site name is especially helpful.<\/p>\n\n\n\n
\n\n\n\n
2020-05-16<\/a>: Excellent, if slightly depressing, analysis by @daydreamuk<\/a>: \u201cThe DAM market right now doesn\u2019t offer a lot for anyone: users don\u2019t get tools they can get very enthusiastic about and vendors don\u2019t make very much money servicing them\u201c https:\/\/digitalassetmanagementnews.org\/opinion\/cloud-dam-nothing-going-on-but-the-rent\/<\/a><\/p>\n\n\n\n
\n\n\n\n
2020-05-10<\/a>: I misread \u201eThe Lord of the Flies\u201c as \u201eThe Lord of the Files\u201c \u2013 that must be a novel where an enterprise, left stranded without any librarians, evolves from information chaos to information systems so badly designed that terrible things happen\u2026<\/p>\n\n\n\n
\n\n\n\n
2020-05-03<\/a>: If you wonder how to name your #DAM<\/a> system \u2013 image archive? media bank? asset portal? \u2013 check out the dozens of labels collected by @Jesperfaurby<\/a>: https:\/\/filecamp.com\/blog\/what-to-call-your-dam\/<\/a><\/p>\n\n\n\n
\n\n\n\n
2020-04-27<\/a>: Fun office game: Let two colleagues write meeting minutes (for the same meeting). Compare.<\/p>\n\n\n\n
\n\n\n\n
2020-04-19<\/a>: During the last weeks, I learned how to do simple music notation with @musescore<\/a> https:\/\/musescore.org\/<\/a> (great, free software). Listening to a song and turning it into sheet music is a nice hobby, similar to solving a puzzle.<\/p>\n\n\n\n
\n\n\n\n
2020-04-11<\/a>: A spec that covers everything mentioned in this (good!) article would be perfect, but might not be a realistic goal. A good start is to document the feature before building it, with a rough outline of the technical implementation. https:\/\/stackoverflow.blog\/2020\/04\/06\/a-practical-guide-to-writing-technical-specs\/<\/a><\/p>\n\n\n\n
\n\n\n\n
2020-04-08<\/a>: I can now use a proper microphone (and guitar \ud83c\udfb8) in video conferences \ud83d\ude42 thanks to Apple MainStage + iShowU Audio Capture software (plus macOS\u00b4 built-in \u201cMulti-Output Device\u201d) and my Steinberg audio interface. Here\u2019s my setup:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"
2020-06-29: \u201cDon\u2019t use Event Sourcing unless you have a complex domain that has to deal with a lot of users working together on the same entities. [\u2026] Don\u2019t ignore NoSQL as an alternative. [\u2026] Don\u2019t use the domain events as a communication mechanism between domains or services.\u201d https:\/\/www.dennisdoomen.com\/2020\/06\/guidelines-event-sourcing.html 2020-06-24: Excellent, in-depth presentation of the @FinancialTimes […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[1],"tags":[],"class_list":["post-2090","post","type-post","status-publish","format-standard","hentry","category-weblog"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2090","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/comments?post=2090"}],"version-history":[{"count":2,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2090\/revisions"}],"predecessor-version":[{"id":2196,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2090\/revisions\/2196"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=2090"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=2090"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=2090"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}