dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.6K
active users

#BoosterConf

0 posts0 participants0 posts today
njan<p>Awww! We will have our <a href="https://chaos.social/tags/MotionSickness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MotionSickness</span></a> related Accessibility workshop "tomorrow" (Friday at 9am =.=) at <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a>... and sessionize, the software they used for speaker relations, generated this cute banner to share.<br>Many 90s-web-vibes &lt;3</p><p>Also we finally agreed on a hashtag for all things regarding motion-sickness-safe websites: <a href="https://chaos.social/tags/PukeLessWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PukeLessWeb</span></a>. </p><p>Waaaay shorter than our old workshop hashtags :)</p>
Markus 🌱:fosse:<p>Eg har ikkje sett den sjølv, og har ikkje planar om det, men det ligg video ute av innlegget mitt!</p><p><a href="https://www.boosterconf.no/2025/program/wednesday/5_lightning_talks/kongesalen_1/speaking-your-mind-the-why-and-where-and-when-and-what-and-how/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">boosterconf.no/2025/program/we</span><span class="invisible">dnesday/5_lightning_talks/kongesalen_1/speaking-your-mind-the-why-and-where-and-when-and-what-and-how/</span></a></p><p><a href="https://skvip.lol/tags/Booster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Booster</span></a> <a href="https://skvip.lol/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> <a href="https://skvip.lol/tags/Bergen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bergen</span></a> <a href="https://skvip.lol/tags/Konferanse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Konferanse</span></a> <a href="https://skvip.lol/tags/TeamWork" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TeamWork</span></a> <a href="https://skvip.lol/tags/Communication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Communication</span></a></p>
elzapp 🐧☁️<p>Isn't it strange that the only thing we're not supposed to be agile about, with agile frameworks, is the way of working and the framework itself? </p><p><a href="https://social.vivaldi.net/tags/boosterconf25" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>boosterconf25</span></a> <a href="https://social.vivaldi.net/tags/boosterconf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>boosterconf</span></a></p>
njan<p>Oooh, a misplaced email situation has been cleared up now it's official, that my colleague and I will hold our (prevent) motion sickness accessibility workshop at <a href="https://chaos.social/tags/boosterconf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>boosterconf</span></a> (March 26-28) in Bergen. :yayblob: </p><p>This conference seems so thoughtful and friendly. A conference that is truly relevant for the WHOLE team, not just the devs. I like this approach a lot and am now very excited.</p><p>I've never been to Norway, though, so there's a lot to duckduckgo. 💜</p>
Markus Tacker<p>I've published my photos from this year's wonderful <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> here: <a href="https://photos.coderbyheart.com/album/boosterconf-2023" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">photos.coderbyheart.com/album/</span><span class="invisible">boosterconf-2023</span></a></p>
Markus Tacker<p>My summary blog post about <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> 2023 in <a href="https://chaos.social/tags/Bergen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bergen</span></a> 🇳🇴 is online: <a href="https://coderbyheart.com/boosterconf-2023" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">coderbyheart.com/boosterconf-2</span><span class="invisible">023</span></a></p><p>I have also added the videos of the talks I've attended, because all of the recordings are already up on Vimeo.</p>
joep schuurkes<p>Had a great time at <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> this week!</p><p>Some of the things that made it great:<br>- interesting workshops and experience reports<br>- relaxed atmosphere<br>- excellent tea and coffee (as in: great loose leaf tea and specialty coffee from a Chemex)<br>- very affordable tickets (2000 NOK ex VAT) if you have to pay for yourself.</p><p>Thank you to the organizers, speakers, and attendees!</p>
Markus Tacker<p>Thanks to the <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> organizers and team, that was a blast!</p>
Markus Tacker<p>Daan van Berkel closes <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> for this year.</p>
Markus Tacker<p>Finally he points out to watch out for potential causes this approach can fail:</p><p>1. "Bad" decisions (there are none really)<br>2. Old guard == New guard (not giving room for others to make decisions)<br>3. Off-the-grid decisions (teams not using the process)<br>4. No trust</p><p>This is the detailed blog post for this talk: <a href="https://martinfowler.com/articles/scaling-architecture-conversationally.html" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">martinfowler.com/articles/scal</span><span class="invisible">ing-architecture-conversationally.html</span></a></p><p><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> <a href="https://chaos.social/tags/AnybodyArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AnybodyArchitecture</span></a></p>
Markus Tacker<p>In the draft phase the team pulls in advice from all affected parties and document this advice.</p><p>All of this effort gets synchronized in weekly meetings of the Architectural Advice Forum.</p><p>It's important to track progress of ADRs to have an eye on those ADRs that get stuck.</p><p><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> <a href="https://chaos.social/tags/AnybodyArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AnybodyArchitecture</span></a></p>
Markus Tacker<p>In his session at <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> <span class="h-card"><a href="https://twit.social/@ahl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ahl</span></a></span> talks about how architects can change their behaviour to not keep teams back, but to enable them making their own architecture decisions. <a href="https://chaos.social/tags/AnybodyArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AnybodyArchitecture</span></a></p><p>He proposes The Advice Process:</p><p>"Anyone can make any decision But before doing so they must: seek advice from all affected parties &amp; people with expertise in the matter."</p><p>But how to keep people from making bad decisions? Use ADRs to document the decision to be made and iterate on it.</p>
Markus Tacker<p>- a lot of consumers wanted access to Gigabytes of data, and transferring this via <a href="https://chaos.social/tags/GraphQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GraphQL</span></a> creates a huge overhead.</p><p>So it turned out that it a traditional REST API would have been a better choice, both it would be easier to maintain with a smaller team, and it's a more established technology that would scale better for this specific project.</p><p><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>
Markus Tacker<p>Now for the downsides:<br>- it introduces a bunch of new and complex concepts for implementing it properly <br>- from a client point of view it can be challenging to build clients that need to retrieve a lot of deep, nested data<br>- Many users often want spreadsheet exports, that's hard to match from a nested structure<br>- Because of the complexity the internal adoption of the new API was not a full success, which is a good indication that it's not an optimal solution</p><p><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>
Markus Tacker<p>The goal was to provide public access to the data they collect, and in 2018 when they need to pick a new technology it looked like a good choice, addressing the shortcomings of REST.<br>The initial evaluation and internal tests went quite well, and even though there was some hesitation because it was uncertain if it was the right choice over REST, it was decided to continue with the approach.<br>It was easy to model the API according to the business domain. And they went on to launch it.<br><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>
Markus Tacker<p>Pål Thomassen (<a href="https://www.linkedin.com/in/p%C3%A5l-thomassen-03354212" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linkedin.com/in/p%C3%A5l-thoma</span><span class="invisible">ssen-03354212</span></a>) now shares his bad experience with GraphQL for building an API for traffic data at Statens Vegvesen.</p><p>He starts with a basic introduction to <a href="https://chaos.social/tags/GraphQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GraphQL</span></a>. The bug advantage he mentions is that it is great to document the contract between server and clients, and there are many tools that can generate consumer code.</p><p><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>
Markus Tacker<p>They used Facebook Prophet because it can account very good for seasonal and holiday events (and it's open source).</p><p>Unfortunately he did not share how successful this project was in the end.</p><p><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>
Markus Tacker<p>Marius Aleksander Olavsrud (<a href="https://www.linkedin.com/in/marius-aleksander-olavsrud-812a4617a" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linkedin.com/in/marius-aleksan</span><span class="invisible">der-olavsrud-812a4617a</span></a>) explains how he and his team used Machine Learning to reduce the number of wasted breads at a Norwegian supermarket chain.</p><p>Building a ML solution that works requires the right data. However that often is not there. Make sure to get the input data right.<br>The implementation is only half of the project. Don't underestimate the effort needed to change their processes according to the findings.<br><a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>
Markus Tacker<p>Final day of <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a> and I am starting with a session on API Design from Hege Dreiem (<a href="https://www.linkedin.com/in/hege-dreiem-0186982" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linkedin.com/in/hege-dreiem-01</span><span class="invisible">86982</span></a>).</p><p>She talks about the challenges of designing a ticket booking API for the Norwegian railway.</p><p>It's important to design an API that gets used by many clients that you don't control to be open for extensions from the start. </p><p>Developing a ubiquitous language is important in the beginning to develop an understanding of what the API needs to express.</p>
Markus Tacker<p>My hotel has an umbrella renting station.<br><a href="https://chaos.social/tags/Bergen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bergen</span></a> <a href="https://chaos.social/tags/BoosterConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoosterConf</span></a></p>