{"id":2127,"date":"2019-09-30T00:00:00","date_gmt":"2019-09-29T22:00:00","guid":{"rendered":"https:\/\/www.strehle.de\/tim\/?p=2127"},"modified":"2025-09-04T16:51:14","modified_gmt":"2025-09-04T14:51:14","slug":"tweets-2019-q3","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2019\/09\/30\/tweets-2019-q3\/","title":{"rendered":"Tweets 2019 Q3"},"content":{"rendered":"\n

2019-09-20<\/a>: It\u2019s always a people problem: Every glaringly obvious software architecture mistake, every coding style inconsistency, every weird choice of programming language or tool has a story to tell.<\/p>\n\n\n\n

\n\n\n\n

2019-09-19<\/a>: More pixels are always better! For the first time, I have three monitors to work with:<\/p>\n\n\n\n

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

2019-09-17<\/a>: Caring about appearing strong, and being right, only proves your insecurity and lack of interpersonal skills. You are missing out on the deeper relationships, and better collaboration, that come with showing vulnerability, admitting your faults, revealing what you don\u2018t know.<\/p>\n\n\n\n

\n\n\n\n

2019-09-12<\/a>: A single paragraph of documentation would have spared us many hours of software archaeology: This feature in the old system, what exactly does it do, and for what purpose? (I hope we\u2018ll do a better job of documenting the new system.)<\/p>\n\n\n\n

\n\n\n\n

2019-09-06<\/a>: \u201cWhen we see passionate people at work (at a chess tournament, a brainstorming session, writing a play or counseling), we have trouble imagining doing it for six hours in a row, never mind eight.\u201d https:\/\/seths.blog\/2019\/09\/two-kinds-of-9-to-5-job\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-29<\/a>: That special form of \u201eagile\u201c where developers work in sprints but users don\u2018t get to test the software for months, let alone use it.<\/p>\n\n\n\n

\n\n\n\n

2019-08-28<\/a>: Today I learned about the difference between the ?: (shorthand ternary) and ?? (null coalescing) operators in #PHP<\/a>: https:\/\/www.designcise.com\/web\/tutorial\/whats-the-difference-between-null-coalescing-operator-and-ternary-operator-in-php<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-28<\/a>: Da kommt Arbeit auf uns zu: \u201eWir m\u00fcssen Workflows und Abl\u00e4ufe synchronisieren: \u00fcbergreifende Themenplanung, Planung f\u00fcr das Heft, tagesaktuelle Planung f\u00fcrs Digitale, gemeinsame Textproduktion, Bild-Workflows, Dokumentation und Layout\u201c https:\/\/devspiegel.medium.com\/ein-jahr-projekt-orange-was-wir-geschafft-haben-dc2cbcd58c4f<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-28<\/a>: Our #DAM<\/a> system doesn\u2018t enforce metadata entry during upload because we have no time to waste in a \u201ebreaking news\u201c situation. Of course this means more work later \u2013 and metadata is not only missing for \u201ebreaking news\u201c photos\u2026<\/p>\n\n\n\n

\n\n\n\n

2019-08-25<\/a>: \u201eWhen you pull someone away for one day to fix a bug or help a different team, you don\u2019t just lose a day. You lose the momentum they built up and the time it will take to gain it back. Losing the wrong hour can kill a day. Losing a day can kill a week.\u201c https:\/\/basecamp.com\/shapeup\/2.2-chapter-08<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-25<\/a>: \u201eTwo-week cycles are extremely costly due to the planning overhead. The amount of work you get out of two weeks isn\u2019t worth the collective hours around the table to \u201asprint plan\u2018 or the opportunity cost of breaking everyone\u2019s momentum to re-group.\u201c https:\/\/basecamp.com\/shapeup\/2.2-chapter-08<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-24<\/a>: \u201cAnybody can suggest expensive and complicated solutions. It takes work and design insight to get to a simple idea that fits in a small time box.\u201d https:\/\/basecamp.com\/shapeup\/1.5-chapter-06#ingredient-2-appetite<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-23<\/a>: Project management as information management: a seemingly infinite loop of distributing and gathering information (from users, managers, vendors, IT) and turning it into documents (requirements, specs, tickets, plans, status updates, meeting notes)<\/p>\n\n\n\n

\n\n\n\n

2019-08-22<\/a>: In case you didn\u2019t know: Using a single unlicensed image online over a couple of years can cost as much as buying and implementing a mid-sized #DAM<\/a> system. #ROI<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-22<\/a>: Me: \u201cHow do I call this Web service?\u201d Dev: \u201cHere\u2019s the Javadoc.\u201d Me: \u201cHow *exactly* do I call this Web service, do you have a curl example? The Javadoc documents nothing except parameter names and types \u2013 what information am I to provide?\u201d<\/p>\n\n\n\n

\n\n\n\n

2019-08-17<\/a>: Vielleicht sind iFrames nicht \u201cder heilige Gral\u201d, aber ein guter Artikel: https:\/\/www.heise.de\/ratgeber\/iframes-der-heilige-Gral-bei-verteilten-Webanwendungen-4496075.html<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-15<\/a>: This excellent blog post by @juantreminio<\/a> helped a lot on my journey to understanding Docker \u2013 now my containers run on Linux as well, not just on my Mac: https:\/\/jtreminio.com\/blog\/running-docker-containers-as-current-host-user\/<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-08-14<\/a>: Why spend so much time discussing other people\u2018s faults? I\u2018m more interested in what I\u2018m doing wrong \u2013 because that\u2018s what I can change.<\/p>\n\n\n\n

\n\n\n\n

2019-08-09<\/a>: I\u2019m the bottleneck\u2026 What am I doing wrong when developers implement features I specified faster than I can write new specs?<\/p>\n\n\n\n

\n\n\n\n

2019-08-06<\/a>: My favorite new feature in today\u2019s @woodwingsoft<\/a> Elvis #DAM<\/a> 6.35 release: \u201cUpload and link\u201d<\/p>\n\n\n\n

\n\n\n\n

2019-07-12<\/a>: \u201cPublishers with a high rate of credit metadata have a CMS designed to keep them \u201calive\u201d (that is, not to delete them). Very few are in this case: @SPIEGELONLINE<\/a> is the best example.\u201d \u2013 @imatag<\/a> https:\/\/www.imatag.com\/blog\/state-of-image-metadata-in-news-sites-2019-update<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-07-12<\/a>: \u201eIt\u2019s important to keep a cool manner and a bit of a poker face. We don\u2019t want to shut down an idea that we don\u2019t understand. On the other hand, showing too much enthusiasm right away can set expectations that this thing is going to happen.\u201c https:\/\/basecamp.com\/shapeup\/1.2-chapter-03<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-07-11<\/a>: Family tech support: Replaced a slow, crappy, noisy Windows laptop with a (used, relatively cheap) Mac mini (with SSD). It\u2019s like night and day: Fast, silent, safe, beautiful.<\/p>\n\n\n\n

\n\n\n\n

2019-07-10<\/a>: \u201cWe\u2019re not into waterfall or agile or scrum. We don\u2019t line walls with Post-it notes. We don\u2019t do daily stand ups, design sprints, development sprints. No backlogs, no Kanban\u2026\u201d I can\u2019t wait to read it all. Thanks for making the book available for free! https:\/\/basecamp.com\/shapeup<\/a><\/p>\n\n\n\n

\n\n\n\n

2019-07-05<\/a>: \u201eErz\u00e4hlt den Menschen, wie m\u00fchsam Innovationen wirklich entstehen, wie weh Ver\u00e4nderungen tun k\u00f6nnen. Erz\u00e4hlt den Leuten, dass es Arbeit ist.\u201c https:\/\/www.manager-magazin.de\/unternehmen\/artikel\/digitalisierung-macht-den-leuten-nichts-vor-a-1275558.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

2019-09-20: It\u2019s always a people problem: Every glaringly obvious software architecture mistake, every coding style inconsistency, every weird choice of programming language or tool has a story to tell. 2019-09-19: More pixels are always better! For the first time, I have three monitors to work with: 2019-09-17: Caring about appearing strong, and being right, only […]<\/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-2127","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\/2127","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=2127"}],"version-history":[{"count":14,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2127\/revisions"}],"predecessor-version":[{"id":2198,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/2127\/revisions\/2198"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=2127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=2127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=2127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}