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

2019-06-27<\/a>: Learning to manage my own expectations: When I show people new software, I don\u2019t expect them to like it just because we put so much work into it. They will rightfully be skeptical, ask hard questions, care for how hard it will be to adapt their way of working. UX is king.<\/p>\n\n\n\n

\n\n\n\n

2019-06-21<\/a>: \u201cUndocumented features\u201d are pretty common. How do we call the opposite \u2013 features that are documented but aren\u2019t actually implemented in the software?<\/p>\n\n\n\n

\n\n\n\n

2019-06-19<\/a>: Excellent move by @woodwingsoft<\/a> to publish all #WoodWingXperience<\/a> conference videos and presentations via their #DAM<\/a>: https:\/\/xperience.swivle.cloud\/<\/a> Now if only the @swivledam<\/a> \/ Elvis DAM portal UI supported deep links to assets\u2026<\/p>\n\n\n\n

\n\n\n\n

2019-06-19<\/a>: The joys of \u201cagile\u201d development: \u201cI have a suggestion regarding the SQL schema you proposed yesterday\u2026\u201d \u201cIT’S TOO LATE TO CHANGE IT. I ALREADY CREATED THE (empty, tiny) TABLE (on the development server)!\u201d<\/p>\n\n\n\n

\n\n\n\n

2019-06-19<\/a>: It\u2019s sad that @Blendle<\/a> stops selling individual articles. If I\u2018m interested in a special topic which ten different publications write about once a year, and they\u2018re all subscription-only, how can I read these articles? https:\/\/www.niemanlab.org\/2019\/06\/micropayments-for-news-pioneer-blendle-is-pivoting-from-micropayments\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-06-18<\/a>: I use this (free, > 50 megapixel) image to test zoom functionality in #DAM<\/a> systems: https:\/\/commons.wikimedia.org\/wiki\/File:Small_bodies_of_the_Solar_System.jpg<\/a> What\u2019s your favorite (publicly available) large test image?<\/p>\n\n\n\n

\n\n\n\n

2019-06-18<\/a>: Developers may argue to \u201ekeep it simple\u201c. But once they implement (or even just plan) complexity, they are emotionally attached to it and will resist \u201emaking it simpler than it was\u201c: \u201eWe might need it later\u201c, \u201ekeeping that feature does no harm\u201c, \u201enever change a running system\u201c\u2026<\/p>\n\n\n\n

\n\n\n\n

2019-06-16<\/a>: I\u2019m currently learning \u201cGit Flow\u201d \u2013 I guess I have to spend a few semesters at Hogwarts to learn all the git spells\u2026 This cheat sheet helps a little: https:\/\/gist.github.com\/JamesMGreene\/cdd0ac49f90c987e45ac<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-06-16<\/a>: Sorry @Canto<\/a>, but I\u2019m going to unsubscribe from your English blog https:\/\/www.canto.com\/blog\/<\/a> \u2013 you keep posting very shallow \u201ccontent\u201d on a daily basis. I assume you\u2019re writing for Googlebot, not for actual humans interested in #DAM<\/a> or your products.<\/p>\n\n\n\n

\n\n\n\n

2019-06-12<\/a>: \u201cAnd so we compromise on schedule, or quality, or on the pace of our days. We compromise on our standards, on our expectations and on what matters right now. You can\u2019t produce without compromises.\u201d https:\/\/seths.blog\/2019\/06\/100-compromises\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-06-06<\/a>: At work, variety can boost creativity and problem-solving skills: Switch between screen, paper and whiteboard. Work alone, then collaborate with different people. Don\u2018t always meet in the same room. Go outside for a walk to think \/ talk things through.<\/p>\n\n\n\n

\n\n\n\n

2019-06-04<\/a>: \u201eAs ever in DAM, I get the sense that the buy-side is way ahead of the sell-side in terms of their thinking \u2013 and getting increasingly frustrated at having to endlessly explain the basics of what this means and the implications it entails.\u201c – @daydreamuk<\/a> https:\/\/digitalassetmanagementnews.org\/features\/henry-stewart-dam-ny-2019-attendee-feedback\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-30<\/a>: To the nice ways to visualize UI interaction flows \u2013 see https:\/\/blog.prototypr.io\/ux-flows-and-why-theyre-so-confusing-26670b9089d4<\/a> \u2013 I\u2019d add a \u201cstreet map\u201d approach: A click that\u2019s required = traffic light, a choice to select = junction or roundabout, text input = toll booth etc. Routing algorithms could calculate travel time.<\/p>\n\n\n\n

\n\n\n\n

2019-05-30<\/a>: I learned that @Tamedia<\/a> has a \u201cPUX\u201d team \u2013 \u201cProduct & User Experience\u201d: https:\/\/www.tamedia.ch\/en\/group\/product-user-experience\/overview<\/a> They seem to be doing a great job. Maybe we should hire them to help us design our apps?<\/p>\n\n\n\n

\n\n\n\n

2019-05-29<\/a>: Hans Fermont of PubliQare talks about their PQCloud offering https:\/\/publiqare.com\/pqcloud\/<\/a> , helping customers get started quickly with Elvis, Enterprise and related tools running in the \u2066@awscloud<\/a>\u2069 cloud. #WoodWingXperience<\/a><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\n\n\n\n

2019-05-29<\/a>: The Elvis DAM workflows at @CiplaRSA<\/a> rely heavily on status metadata, says @SvanHeerden<\/a>. The screenshot shows Webhook-triggered emails on status change. Full customer story: https:\/\/www.woodwing.com\/inspiration\/success-stories\/cipla-south-africa<\/a> #WoodWingXperience<\/a><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\n\n\n\n

2019-05-29<\/a>: Anybody else doing @woodwingsoft<\/a> Elvis DAM integrations in #PHP<\/a>? Let\u2019s talk about sharing (and maybe \u201copen sourcing\u201d) code! #WoodWingXperience<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-28<\/a>: NEXT runs two large Elvis clusters. @russpierpoint<\/a> explains why \u2013 hi-res production and Web site delivery requirements are pretty different\u2026 #WoodWingXperience<\/a><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\n\n\n\n

2019-05-28<\/a>: Some of these \u201eOld DAM\u201c problems sound familiar\u2026 Jason Braker of @nextofficial<\/a> describes their journey from Cumulus to Elvis. #WoodWingXperience<\/a><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\n\n\n\n

2019-05-28<\/a>: Developer: \u201cNo problem if that feature doesn\u2019t work, nobody\u2019s using it.\u201d Guess what happens next\u2026<\/p>\n\n\n\n

\n\n\n\n

2019-05-28<\/a>: Fast-paced, detailed demo by Sean Keefe of PubWorX of their @woodwingsoft<\/a> Elvis \u201cPhoto Portal\u201d. Instead of the built-in \u201cRequest upload\u201d button, they collect metadata via Google Forms, automatically create an Elvis \u201cshare link\u201d & send email to the photographer. #WoodWingXperience<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-28<\/a>: \u201cConnect the product and the customer at the emotional level\u201d: @cliffcrosbie<\/a> talks about retail\u2019s path to customer experience, including hiring for attitude \u2013 \u201cpeople who really want to work with the customer\u201d. Can we learn from that in our IT departments? #WoodWingXperience<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-28<\/a>: Collaboration is a recurring topic at #WoodWingXperience<\/a>: comments, image annotations, collaborative editing\u2026 @creativecloud<\/a> building a @MicrosoftTeams<\/a> integration seems like the right approach; collab built into a single application doesn\u2019t help people collaborate across tools.<\/p>\n\n\n\n

\n\n\n\n

2019-05-28<\/a>: Interesting @Tamedia<\/a> workaround for InDesign documents taking longer to load when the editorial system runs in the cloud: Move the InDesign client application into the cloud, too, using @awscloud<\/a> AppStream. #WoodWingXperience<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-28<\/a>: Marco di Bernardo of @Tamedia<\/a>: The biggest challenge is usability \u2013 getting all the different tools to work together well, so people don\u2018t avoid using them. #WoodWingXperience<\/a><\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\n\n\n\n

2019-05-28<\/a>: While @woodwingsoft<\/a> \u201ehas grown from traditional publishers, 65% of the customer base already is from brand management \/ marketing\u201c, says @paterson_ross<\/a>. Coping with diverging requirements will be a major product management challenge. #WoodWingXperience<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-25<\/a>: I\u2018ll tweet my conference highlights (time and battery life permitting). The official hashtag is #WoodWingXperience<\/a> (according to the booklet). https:\/\/twitter.com\/woodwingsoft\/status\/1131103995508994048<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-24<\/a>: The new masonry view in @woodwingsoft<\/a> Elvis #DAM<\/a> 6.32 looks great:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\n\n\n\n

2019-05-24<\/a>: Content marketers won against librarians? Sad that @Widen<\/a> \u201cconsolidated\u201d the @digitalassetmgt<\/a> site, taking hundreds of #DAM<\/a> articles off the Web. 243 @PlanetDAM<\/a> links are now dead. They say they’ll restore selected articles. How about preserving them all?<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\n\n\n\n

2019-05-23<\/a>: I\u2019m new to @Docker<\/a>, but my first \u201ccontainerized\u201d Symfony 4 application was up and running in a few hours thanks to blog posts like http:\/\/geekyplatypus.com\/making-your-dockerised-php-application-even-better\/<\/a> and @phpstorm<\/a>\u2019s excellent Docker support\u2026<\/p>\n\n\n\n

\n\n\n\n

2019-05-23<\/a>: Excellent \u201cWebhooks with PHP\u201d talk by @lornajane<\/a> \u2013 that\u2019s where I learned about @ngrokapp<\/a>: https:\/\/www.youtube.com\/watch?v=kBlmEfljrn0<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-16<\/a>: On rights: \u201cWhat is or isn\u2019t usable is always based on the particular user and the context in which they want to use a piece of media. Also, it\u2019s not enough to show a journalist what they can and can\u2019t use; they need to know why a piece of content is ‚red‘ ‚green‘ or ‚amber‘.\u201d https:\/\/iptc.org\/news\/iptc-2019-spring-meeting-day-3\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-13<\/a>: Give me both the pros and cons if you want to convince me of something. There always are disadvantages. If you don\u2019t tell me about them, either you haven\u2019t thought things through, believe the hype, or you want to manipulate me.<\/p>\n\n\n\n

\n\n\n\n

2019-05-09<\/a>: \u201e\u2026 die Pl\u00e4ne f\u00fcr neue Workflows im Redaktionsalltag sowie Neuerungen in den zugeh\u00f6rigen Tools \u2013 von der Themenplanung \u00fcber den Texteditor bis zur Archivierung \u2013 zeigt ein Board \u201aEditorial Solutions\u2018.\u201c https:\/\/devspiegel.medium.com\/okr-teams-kollaboration-wie-wir-unsere-produkte-weiterentwickeln-1190ac3fc055<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-07<\/a>: From the @Medium<\/a> Terms of Service: \u201eWe can remove any content you post for any reason.\u201c https:\/\/policy.medium.com\/medium-terms-of-service-9db0094a1e0f<\/a> One more reason to go back to the good old personal, self-hosted website. https:\/\/twitter.com\/bennetttomlin\/status\/1125393833552949249<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-07<\/a>: Bad software quality is ultimately management\u2018s fault, not the developers\u2018: Intentional mediocrity (more quality != more revenue), firefighting mode (often due to over-promising salespeople), little interest in UX and users, neglect (not a strategic product, near end of life).<\/p>\n\n\n\n

\n\n\n\n

2019-05-03<\/a>: Trying to establish a \u201c#DAM<\/a> Governance Council\u201d, as outlined by @jhorodyski<\/a> in this excellent article from 2014: https:\/\/www.cmswire.com\/cms\/information-management\/the-greatness-of-information-governance-025736.php<\/a> (Finding a good German name is hard. \u201cArbeitskreis Bilddatenbank\u201d?)<\/p>\n\n\n\n

\n\n\n\n

2019-05-03<\/a>: \u201cMetadata sources are connected through a unified graph.\u201d Let\u2019s do that! https:\/\/twitter.com\/lisagrimm\/status\/1124303059566329857<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-05-01<\/a>: \u201cWhen a journalist requested a picture for an article, the picture desk would find it, send it into the content management system, send the journalists the ID, and they would then put the image into the article.\u201d https:\/\/twitter.com\/fotoware\/status\/1123528787466039296<\/a> \/ https:\/\/www.fotoware.com\/blog\/the-financial-times-image-workflow<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-30<\/a>: \u201cIf you don\u2019t think mediocrity is rampant in the DAM industry, take another look at the software solutions that are available\u2026 We have an industry full of ‚good enough‘ software solutions, yet no absolutely amazing tools that seduce people into wanting to get content organized.\u201d https:\/\/digitalassetmanagementnews.org\/opinion\/david-diamond-interview-series-third-instalment\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-29<\/a>: Dear vendor, even bugs that haven\u2019t hit users yet are costing us – a lot of time (reproducing, documenting, testing fixes) keeping us from important project tasks, – and real money because we must pay your partner to report the bugs to you (your ticket system is partner-only) https:\/\/twitter.com\/tistre\/status\/1121684211063115778<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-29<\/a>: \u201eHere\u2019s an idea. A thought experiment. Start with the premise that the best approach is to ship nothing.\u201c https:\/\/twitter.com\/johncutlefish\/status\/1122734567268343809<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-26<\/a>: Our DAM system isn\u2019t even live yet, and we found 21 bugs in the product already. (These are the ones acknowledged by the vendor; they fixed 4 so far. We reported more \u2013 some were classified as feature requests, others still pending.) #QualityAssurance<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-25<\/a>: Outlook Safelinks https:\/\/support.microsoft.com\/en-us\/office\/advanced-outlook-com-security-for-microsoft-365-subscribers-882d2243-eab9-4545-a58a-b36fee4a46e2<\/a> are terrible for developers exchanging API or example URLs. To help me deal with them, I created a macOS Service (via Automator) that runs a PHP script which replaces the selected Safelink URL with the real one\u2026<\/p>\n\n\n\n

\n\n\n\n

2019-04-18<\/a>: \u201cThe present fear is that you are just going to design it wrong. All good DAMs are built on paper first, a combination of whiteboarding and excel documents\u2026 The second fear is just that people won\u2019t get on board with it.\u201d https:\/\/www.widen.com\/blog\/building-dam-systems-on-paper-robert-noble-widen-podcast<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-18<\/a>: If you\u2019re an unsatisfied customer, don\u2019t expect your vendor to change for the better. You may invest time and energy to escalate, force or cajole them into performing better \u2013 slightly, and not for long. Deal with, or quit, organizations lacking the drive to continuously improve.<\/p>\n\n\n\n

\n\n\n\n

2019-04-18<\/a>: Nothing is perfect \u2013 I\u2019m always aware of the imperfections of the stuff I build and do, and would rather improve it than defend the status quo. Here\u2019s a nice explanation of why not all people feel this way: https:\/\/seths.blog\/2019\/04\/make-things-better\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-17<\/a>: \u201eAutonomy for some people means implementing whatever solution they have in mind\u200a\u2014\u200athat looks fun to work on. It also means not being \u201adragged down by other people\u2018 or \u201ahaving to do lots of meetings\u2018.\u201c https:\/\/twitter.com\/johncutlefish\/status\/1118594764650110976<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-16<\/a>: Does anyone use @pixolution<\/a> together with @woodwingsoft<\/a> Elvis #DAM<\/a>? Duplicate detection and visual search would be a nice addition to our Elvis.<\/p>\n\n\n\n

\n\n\n\n

2019-04-14<\/a>: SimCity for macOS is on offer today \u2013 I bought it, hoping I can use it for software architecture visualization: \/tim\/weblog\/archives\/2016\/07\/31\/1595\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-12<\/a>: I love how the @IPTC<\/a> embraces #LinkedData<\/a>. (I\u2018m afraid they are light years ahead of the news \/ publishing industry and their software vendors.) https:\/\/de.slideshare.net\/slideshow\/iptc-new-taxonomies-ideas\/140310264<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-12<\/a>: \u201eMost news agencies‘ stories are processed in a [\u2026] format hostile to hyperlinks, processed by poorly standardized, slow-release-cycle legacy systems, with a human copy-and-pasting plain text more often than not part of this workflow.\u201c https:\/\/tfm.slides.com\/mvtango\/iptc-spring-2019#\/metadata-as-a-service-dpa-trust-project-iptc-spring-meeting-2019<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-11<\/a>: When you\u2019re coding, time flies by: I make use of that phenomenon to \u201eshorten\u201c long, boring train rides. This time, I built a graph for my \u201econtent registry\u201c project in Neo4j, and learned some Cypher along the way. (I \u2764\ufe0f that you can download the documentation for offline usage\u2026)<\/p>\n\n\n\n

\n\n\n\n

2019-04-11<\/a>: Nested, hierarchical collections \u2013 a great new feature in @woodwingsoft<\/a> Elvis #DAM<\/a> 6.30: https:\/\/helpcenter.woodwing.com\/hc\/en-us\/articles\/115002645166-Elvis-6-Server-Release-Notes<\/a> You can thank our photo editor staff for insisting on that functionality getting added to Elvis.<\/p>\n\n\n\n

\n\n\n\n

2019-04-09<\/a>: \u201eUnfortunately even today\u2019s DAM implementations commonly make the mistake of undervaluing user experience. Making the constantly evolving use cases intuitive to the users requires manual backend tweaks\u2026\u201c https:\/\/www.linkedin.com\/pulse\/dam-versus-content-services-magan-arthur\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-09<\/a>: Ich verstehe die Intention \u2013 wer Ver\u00e4nderungen schlecht plant oder kommuniziert, schiebt die Schuld gern auf \u201eAngst vor Ver\u00e4nderungen\u201c. Aber \u201ecognitive bias\u201c wie https:\/\/de.m.wikipedia.org\/wiki\/Status-quo-Verzerrung<\/a> oder https:\/\/de.m.wikipedia.org\/wiki\/Verlustaversion<\/a> sind nachgewiesen, es gibt diese Angst tats\u00e4chlich. https:\/\/twitter.com\/kpukall\/status\/1115128547197300737<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-08<\/a>: \u201cIf I\u2019m going to be promoting a product, that product has to be amazing.\u201d If you come across truly amazing DAM software, please let me know\u2026 https:\/\/digitalassetmanagementnews.org\/features\/interview-with-david-diamond-part-1\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-08<\/a>: Wow. Das sieht interessant aus \u2013 da w\u00fcrde ich sehr gern das Kleingedruckte lesen k\u00f6nnen\u2026 https:\/\/twitter.com\/eklde\/status\/1115272766540980225<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-04-02<\/a>: Interesting to see how a (once excellent) DAM system that has no clear ownership, little governance, and no development resources becomes more and more of a burden as requirements and expectations evolve.<\/p>\n","protected":false},"excerpt":{"rendered":"

2019-06-27: Learning to manage my own expectations: When I show people new software, I don\u2019t expect them to like it just because we put so much work into it. They will rightfully be skeptical, ask hard questions, care for how hard it will be to adapt their way of working. UX is king. 2019-06-21: \u201cUndocumented […]<\/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-2142","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\/2142","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=2142"}],"version-history":[{"count":17,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2142\/revisions"}],"predecessor-version":[{"id":2192,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2142\/revisions\/2192"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=2142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=2142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=2142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}