MastodonTech.de

flaeky pancako<a href="https://prsm.space/tags/solar" class="mention hashtag" rel="nofollow noopener" target="_blank">#solar</a> <a href="https://prsm.space/tags/diy" class="mention hashtag" rel="nofollow noopener" target="_blank">#diy</a> <a href="https://prsm.space/tags/iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#iterative</a>All progress here is iterative, currently waiting patiently for some components to setup the DC power system in the house , primarily for an led lighting system 😁

Rob Carlson :ally: :BLM:Here with Mansi for “<a href="https://epistolary.org/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> and <a href="https://epistolary.org/tags/Parenting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Parenting</a>”, some notes:- <a href="https://epistolary.org/tags/Iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#Iterative</a> development: adjustments and bug fixes as you go, for kids is Sleep, routines, feedback from reactions - Handling the unexpected: How do you handle <a href="https://epistolary.org/tags/exceptions" class="mention hashtag" rel="nofollow noopener" target="_blank">#exceptions</a> cleanly? How do you react to random kid behavior? - Debugging: <a href="https://epistolary.org/tags/test" class="mention hashtag" rel="nofollow noopener" target="_blank">#test</a> solutions until problem is solved, for kids there will be a solution eventually - Balancing <a href="https://epistolary.org/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#complexity</a>: Only when absolutely necessary, one step at a time for processes - Celebrate wins - When you solve, brag about it, when kids to the same congratulate them<a href="https://epistolary.org/tags/bcphilly" class="mention hashtag" rel="nofollow noopener" target="_blank">#bcphilly</a> <a href="https://epistolary.org/tags/barcamp" class="mention hashtag" rel="nofollow noopener" target="_blank">#barcamp</a>

David SabineMoments away from opening my Professional Scrum with User Experience course. (PSU)It's one of my favourite courses to teach. The material is important for everyone who attempts to blend <a href="https://mastodon.social/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UX</a> and <a href="https://mastodon.social/tags/Iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#Iterative</a>&Incremental <a href="https://mastodon.social/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> <a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a>.

Kristin (vis.social Admin)Some dancing starfish for today's <a href="https://vis.social/tags/inkyDays" class="mention hashtag" rel="nofollow noopener" target="_blank">#inkyDays</a> drawing. With my recovery from surgery, I can't really dance yet, but I'm dancing on the inside.Here's an in-progress shot.And that's a wrap for this month's daily drawings. In-progress and complete drawings for this month are now all posted for my supporters on patreon and kofi in this month's <a href="https://vis.social/tags/inkyDays" class="mention hashtag" rel="nofollow noopener" target="_blank">#inkyDays</a> posts: <a href="https://www.patreon.com/posts/101521238" rel="nofollow noopener" translate="no" target="_blank">https://www.patreon.com/posts/101521238</a> <a href="https://ko-fi.com/Post/InkyDays-April-2024-N4N0WEJT0" rel="nofollow noopener" translate="no" target="_blank">https://ko-fi.com/Post/InkyDays-April-2024-N4N0WEJT0</a><a href="https://vis.social/tags/ink" class="mention hashtag" rel="nofollow noopener" target="_blank">#ink</a> <a href="https://vis.social/tags/drawing" class="mention hashtag" rel="nofollow noopener" target="_blank">#drawing</a> <a href="https://vis.social/tags/art" class="mention hashtag" rel="nofollow noopener" target="_blank">#art</a> <a href="https://vis.social/tags/starfish" class="mention hashtag" rel="nofollow noopener" target="_blank">#starfish</a> <a href="https://vis.social/tags/seastars" class="mention hashtag" rel="nofollow noopener" target="_blank">#seastars</a> <a href="https://vis.social/tags/MastoArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastoArt</a> <a href="https://vis.social/tags/iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#iterative</a> <a href="https://vis.social/tags/GenerativeArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#GenerativeArt</a> <a href="https://vis.social/tags/wip" class="mention hashtag" rel="nofollow noopener" target="_blank">#wip</a>

Sönke SchwenkWe learned the business. We gained users, feedback, and experience. This led to new requirements — both functional and non-functional.Fortunately, we were able to build on our success.But to stay successful, we had to change the software.And you may need to as well. This is true iterative-incremental development.<a href="https://mastodon.online/tags/softwarearchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwarearchitecture</a> <a href="https://mastodon.online/tags/softwareengineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareengineering</a> <a href="https://mastodon.online/tags/iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#iterative</a> <a href="https://mastodon.online/tags/changedperpective" class="mention hashtag" rel="nofollow noopener" target="_blank">#changedperpective</a>

Sönke SchwenkEver felt like you did something wrong when you had to significantly improve your software?I certainly did.We had built a first version of the product. It solved our customers' problems. It created a business. It was paying our salaries and our bills.The feeling was wrong, not our work!The software was a success. Success changed perspective.🧵 <a href="https://mastodon.online/tags/softwarearchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwarearchitecture</a> <a href="https://mastodon.online/tags/softwareengineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareengineering</a> <a href="https://mastodon.online/tags/iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#iterative</a> <a href="https://mastodon.online/tags/changedperpective" class="mention hashtag" rel="nofollow noopener" target="_blank">#changedperpective</a>

Urs Enzler 🐉I see many software teams using user stories, making estimates, predicting how many of these stories fit into the next Sprint, and when a particular set of stories may be done. But what about getting feedback and reacting to it? Thinking that the first version of a feature will be great is ignorant. Get feedback, improve and iterate! Yes, now, estimates are useless. But your product will be useful to your users. <a href="https://tooting.ch/tags/PseudoAgile" class="mention hashtag" rel="nofollow noopener" target="_blank">#PseudoAgile</a> <a href="https://tooting.ch/tags/Iterative" class="mention hashtag" rel="nofollow noopener" target="_blank">#Iterative</a> <a href="https://tooting.ch/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#iterative