<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Luke Bashford on Medium]]></title>
        <description><![CDATA[Stories by Luke Bashford on Medium]]></description>
        <link>https://medium.com/@luke.bashford?source=rss-09654efa590e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YMkfUQek_vuZLM9fSNkUoQ.jpeg</url>
            <title>Stories by Luke Bashford on Medium</title>
            <link>https://medium.com/@luke.bashford?source=rss-09654efa590e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:00:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@luke.bashford/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Diary of a Mendix Developer: Part2 — How it’s going]]></title>
            <link>https://medium.com/@luke.bashford/the-diary-of-a-mendix-developer-part2-how-its-going-778ddcde8444?source=rss-09654efa590e------2</link>
            <guid isPermaLink="false">https://medium.com/p/778ddcde8444</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[client-relationship]]></category>
            <dc:creator><![CDATA[Luke Bashford]]></dc:creator>
            <pubDate>Mon, 06 May 2024 16:59:06 GMT</pubDate>
            <atom:updated>2024-05-06T16:59:06.818Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Diary of a Mendix Developer: Part2 — How it’s going</h3><p>Continued from <a href="https://medium.com/@luke.bashford/the-diary-of-a-mendix-developer-part-1-how-it-started-419389c64058">Part 1</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJVF85jDxaD17xFmW9tHrg.jpeg" /></figure><p><em>October 6, 2022</em></p><blockquote>This app has gotten very complicated over the past few months. We have gotten really good and taking some basic requirements from the SME and detailing them over a few calls to make sure we have handled every element of the story. I find it frustrating sometimes to have to do so much hand-holding when it comes to requirements so I’m going to talk to the PO and SME to see if they can give us better requirements in the future. Every time we sit down, it feels like we increase the scope by 150%…</blockquote><p><em>October 7, 2022</em></p><blockquote>I was going to talk about requirements this morning with the SME but they ended up doing it for me. They were looking at some of the past items we spent hours working through and want to change the way it works now that they have seen it running in the app. We built exactly what we had discussed but the team doesn’t seem to have understood the requirement documents. We had a long conversation about how we can draft up more detailed requirements, the SME is going to spend a lot more time on the details going into the next sprint.</blockquote><p><em>October 8, 2022</em></p><blockquote>We are coming up on our original target date for pushing to production but the PO doesn’t want to do so until we have some more recent features built and tested. We had planned on starting the push to production before the end of the year since we are going away for the holidays but I don’t think that’s going to happen now with these new requirements.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifErjCYz1zohqXygABv6XA.jpeg" /></figure><p><em>December 13, 2022</em></p><blockquote>New week, nothing much else to say. The client still wants us to push to production but has some features they are trying to get into that push. They just aren’t even finished yet let alone tested.</blockquote><p><em>December 17, 2022</em></p><blockquote>I thought we were finished with a very complex feature where we built a custom matrix of nested list views but now there has been a last-minute ask to add in a 5th layer right in the middle of everything else. This is going to be extremely difficult with all the custom styling we already implemented, as well as all the data source microflows feeding each layer.</blockquote><p><em>December 24, 2022</em></p><blockquote>We didn’t end up finishing the prod push before the holiday break, now I’m getting text messages from the client on Christmas Eve…</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCaX-911GfSfZp5Yf-1cBg.jpeg" /></figure><p><em>January 8, 2023</em></p><blockquote>Decided to skip pushing to production all together, SOW #2 has been signed and the project has been extended for another 3 months.</blockquote><p><strong>Let’s stop reading for now, time to analyze!</strong></p><p>For this set of entries, I’m going to talk about all of them as a whole because there are a few core ideas here that need to be talked about. We see in the October entries that the project is starting to slip out of everyone’s hands. The stories are obviously not detailed enough from a requirements level and neither the development team nor the client SMEs are doing a good job of managing expectations.</p><blockquote>it feels like we increase the scope by 150%…</blockquote><p>If it feels like scope creep, bloat, moving targets, whatever you want to call it… it’s time to stop and re-evaluate all of our goals here. On any project, one of the most important parts of planning a sprint is setting your sprint goals. The thing is, if you are setting sprint goals as something like “The goal for sprint 7 is to deliver the inspection matrix and the fillable PDF”, you are always going to fail to deliver. But why?</p><p>You will fail because a sprint goal should not be a set feature. Instead, it should be to add some amount of value to the project. Example: “In sprint 7 we want to increase user’s visibility of inspections on the job overview so they can more quickly see the overall progress of the project”. Do you see the difference here? A sprint goal is not a promise for something specific, but instead a guideline for where the efforts of each sprint will be focused. Suppose a sprint goal above were to be set up beforehand and the client came to you 4 days into this sprint asking, “Hey we need to make sure the fillable PDFs are ready before the end of this sprint”. In that case, we have a very clear way to let them know this needs to wait until the next sprint planning because it’s not relevant to the current sprint goal. Besides the fact that it wasn’t part of the planning in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oB4lIKcNNSQ3X8AQXZZOUg.jpeg" /></figure><blockquote>The client still wants us to push to production but has some features they are adamantly trying to get into that push</blockquote><p>This scenario is all too common, and something I think every developer runs into over and over in their career. A client understandably wants to see their application progress as quickly as possible, and a first push to production needs to be a culmination of all the sprint goals up to that point. However, what ends up happening is the ideal first push to production approaching creates this sort of shift in focus during the development cycle.</p><p>The client may notice a decrease in velocity in the weeks leading up to a production push because the dev team is shifting some efforts to data migration / documentation / environment configuration. What will happen here is the client will want the same level of feature progress with a production push squeezed in between, and this creates a moving goalpost for that production push because a feature developed a sprint before a production push should never be allowed in that push. You need to have a full UAT cycle for these new features before they can be considered for a production environment.</p><p>The takeaway here is to plan ahead for your sprint goals, but also for WHEN TO DELIVER THE VALUE! Building sprint goals around value is great, but only if that value <em>actually</em> becomes usable for the client. A successful sprint goal means nothing if it doesn’t become a reality for the client and their end users. Plan to realize the added value in regular increments, the more often… the better!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXL_gNn6IjwdR9J7YXkMLw.jpeg" /></figure><blockquote>I’m getting text messages from the client on Christmas Eve</blockquote><p>This is for everyone, set some boundaries! It’s completely acceptable for you to set up specific dates and times when you will be available for your clients and not be available outside of those hours. Sure, you want to deliver the best customer service and professionalism to your clients, but you absolutely can not sacrifice your well-being outside of working hours to satisfy a client who is budgeted for a set number of hours. If you want to have a working weekend relationship with the client, this needs to be discussed beforehand and a structure needs to be in place for weekend or after-hours contact methods and billing. Do not spend your time and energy on something that isn’t logged in the project budget.</p><p>This set of entries touched on some critical parts of a project but only scratched the surface. Send me an email if you have any questions or want to go into more detail about these ideas.</p><p><a href="/service/mailto:luke.bashford@kinetechcloud.com?subject=Medium+article+reference+keys">Email Me!</a></p><p>luke.bashford@kinetechcloud.com</p><p><a href="https://www.kinetechcloud.com/kinetech/the-diary-of-a-mendix-developer-part-1-how-it-started">https://www.kinetechcloud.com/kinetech/the-diary-of-a-mendix-developer-part-1-how-it-started</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=778ddcde8444" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Diary of a Mendix Developer: Part 1 — How it Started]]></title>
            <link>https://medium.com/@luke.bashford/the-diary-of-a-mendix-developer-part-1-how-it-started-419389c64058?source=rss-09654efa590e------2</link>
            <guid isPermaLink="false">https://medium.com/p/419389c64058</guid>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Luke Bashford]]></dc:creator>
            <pubDate>Wed, 21 Feb 2024 16:58:57 GMT</pubDate>
            <atom:updated>2024-02-28T19:36:29.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Diary of a Mendix Developer: Part 1 — How it Started</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lbJ7Lc9Q_b4pt7w2wooWeQ.jpeg" /></figure><p>In the following entries, you will read through the diary of a Mendix developer as they journey through a <strong>project from start to finish</strong>. As the reader, we can tell you that this project contained both triumphs, as well as tribulations. As you read, see if you can pick up on the indicators that signal the trajectory of this project’s journey. Within this series of entries lie <strong>invaluable lessons applicable to any Mendix engagement</strong>. I invite you to analyze these entries with a discerning eye, extracting actionable insights that could inform your own strategic approaches to Mendix development.</p><p><em>June 6, 2022</em></p><blockquote>Today I was told that I might get put on a client at the end of this week, pretty exciting stuff! What I know so far is that our sales team has scoped out for a 6-month engagement and the SOW looks pretty involved. Seems like there will be three of us working with this client to build them an app that essentially clones their existing application but makes it better along the way. We have a meeting tomorrow to go over the SOW items before we get started…</blockquote><p><em>June 7, 2022</em></p><blockquote>Just got off a 2-hour call with management… that was exhausting! I didn’t realize how complicated their business is, they generate so many different things in their current app based on all sorts of configuration. I spoke to my Sr. Architect to see what the best way to programmatically generate all the docs would be and it sounds like there may be a ton of backend logic to process any given set of requests. I’m going to see if the client can send me a dump of their database data to see what it looks like, maybe I can get a better idea of what we are up against here.</blockquote><p><em>June 8 2022</em></p><blockquote>Got an Excel dump of their data this afternoon and all I can say is WOW… This is a lot of very dirty data. I’m not sure they have any validation in their current application at all. At least we got the SOW signed this week though, we will be starting development this coming Monday! I think we have our work cut out for us over the next 6 months.</blockquote><p><em>June 13 2022</em></p><blockquote>Started development today and we are absolutely crushing it, we got the first sprint all planned out with about 40 points of stories and finished the login page and some of the basic navigation. The client decided they don’t want to provide any branding or UX/UI direction and instead trust our judgement to make it look nice after seeing the default Atlas UI. They said that looks so much better than what they currently have so “just make it look nice using those assets”.</blockquote><p><em>June 17 2022</em></p><blockquote>First week is going really well, we almost finished the 40 story points we set out to complete this sprint so we added in another 20 points going into next week to fill the sprint. We told the client that the sprint planning and estimates will fluctuate a little for the first few sprints till we can better understand how fast our dev team can complete story points. 40 seems like we were far too conservative with our estimate so lesson learned there, we will load up more points for sprint 2.</blockquote><p><em>June 24 2022</em></p><blockquote>This second week went very well once again, the client is loving our progress already on the app. We demoed the basic layouts and page features we finished this sprint and the client is very excited to get more built. Their SME had some great ideas to expand on the backlog items, we are taking note of these and putting them into related stories so we can pick them up as V2 items, or when we have remaining time to do so.</blockquote><p><em>July 8 2022</em></p><blockquote>Lost my diary last weekend… glad I found it today in the clutter on my desk. Sprint 2 was actually very frustrating because of all the changes the client wanted on the page designs. Their current app has a pretty complicated matrix to display their signoffs and we just used a Data Grid 2 to allow the user to filter and sort the data that way. They wanted it to look exactly like their current app so we had to re-do it with a pretty hacky set of triple-nested list views and some custom styling to make it look right. Really glad to have had a css expert step in to get the styling working on this, my first 2 attempts would be misaligned by a SINGLE PIXEL and it was driving me nuts. I’m so glad it’s Friday, got an hour back because the client canceled our sprint review — they had some issue to deal with so we are reviewing before sprint planning on Monday…</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D3fVbHrAH_Zm9osQVUs4ww.jpeg" /><figcaption>Let’s stop reading for now, time to analyze!</figcaption></figure><p>By now I would hope you have a few observations or insights just from these few entries above, some more concerning than others. Perhaps you are beginning to feel like this pug:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXCf6FRis_L_H5kNHO5-Mw.jpeg" /><figcaption>Comfy, yet slightly concerned.</figcaption></figure><p>Let’s quickly talk about some things that stand out to us:</p><blockquote>our sales team has scoped out for a 6-month engagement and the SOW looks pretty involved</blockquote><p>As a developer we seem to have been left out of the scoping process altogether. This developer saw the SOW and their first reaction was that it looks very involved. They later comforted themselves by saying they have 3 developers working on it and assumed it should be fine. Speak up if you think something seems off, having a discussion should be the bare minimum requirement when you have any indication of scope being inaccurate.</p><blockquote>I didn’t realize how complicated their business is</blockquote><p>Before even starting development, this should raise some concerns. We see this happen quite often in the low-code world where a client or delivery partner will gloss over the fine details of a project early on with the assumptions that the combination of rapid development and Agile methodology will fill in the gaps along the way. We know from experience that this just doesn’t work. Call it poor planning, scope creep, bloat, whatever you want… the fact of the matter is as soon as a developer sees signs of a project requiring more effort than the team initially thought, it’s time to start managing expectations and organizing the core scope of work in a way that delivers value at regular intervals without jeopardizing the overall goal of the planned SOW.</p><blockquote>I spoke to my Sr. Architect to see what the best way to programmatically generate all the docs would be</blockquote><p>Always use your network when dealing with problems you may not know the best solution to. The Mendix ecosystem is full of incredibly talented and experienced people. We are all better off spending less time trying to figure something out, and more time reaching out to see if someone can provide any advice to help us arrive at a solution faster and more efficiently.</p><blockquote>WOW… This is a lot of very dirty data</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WVcrVP-fBoMV3od6H2KFyA.jpeg" /></figure><p>This is something that can be VERY hard to plan ahead for, especially if you are working with a client that has a lot of non-technical people on the project. In a perfect world, all data would be validated and easily useable by a Mendix application. Breaking news! We are not in a perfect world and the clients that often need Mendix development are trying to solve this exact problem. At this point early in a project, when the data is immediately viewed as a potential issue, it would be wise to bring this up with your architect, and then set up some time with the client to plan around cleaning and migrating any data to the new application.</p><blockquote>The client decided they don’t want to provide any branding or UX/UI direction and instead trust our judgement to make it look nice after seeing the default Atlas UI</blockquote><p>You ever hear anyone say “CYA”… this is one of those moments. It is very easy to respond favorably to a client relinquishing control of UX/UI design, however you must document these decisions along the way. Giving a developer creative control is wonderful but far too often when it comes time to deliver a demo, the client will suddenly have very strong opinions about the design choices and work may need to be redone. Plan everything!</p><blockquote>Their SME had some great ideas to expand on the backlog items, we are taking note of these and putting them into related stories so we can pick them up as V2 items, or when we have remaining time to do so.</blockquote><p>A WIN! This is a fantastic approach to managing a backlog and putting feedback in a place where it doesn’t add any risk to the existing project. When a client gives feedback on deliverables, this feedback needs to be looked at as net new content, documented, and placed at the bottom of the backlog so as not to disrupt the progress towards delivering value to the client.</p><blockquote>Lost my diary last weekend… glad I found it today in the clutter on my desk</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nD2eWtNvJ7X8z9OxCP3Qyg.jpeg" /></figure><p>Stay organized — This goes for your product backlog, your email, and most of all your physical space. If you have junk all over your desk it’s a telltale sign that you are becoming stressed, disorganized, and careless. Take a few minutes each day to make sure that you set yourself up for success, especially if you are working from home. Your physical workspace affects you mental workspace and will be reflected in the quality of your work more often than not.</p><blockquote>They wanted it to look exactly like their current app so we had to re-do it with a pretty hacky set of triple listed list views and some custom styling to make it look right.</blockquote><p>OHHH, so NOWWWWW we have opinions!!! I think this was the clearest red flag out of these early entries. This dev was told they had creative freedom, they built a feature that worked, but upon delivery the client decided they didn’t want it this way and now we just wasted time and budget building something the client doesn’t like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i37pPX0le7nFQS6fGbbHMQ.jpeg" /></figure><p>How do we avoid this? Well, rewind a few entries and look at the other small gaps in planning. Any single item may seem insignificant enough, but together they paint a bigger picture. As experts, we can’t get complacent with our clients or the work we do. Everything that goes into a project matters, especially over a longer period. The project in this case was scoped for 6 months and already 3 weeks in we have seen a half dozen small problems that seem innocent enough. However, what are these going to look like 4 months from now… Always document decisions, stick to the planned requirements, and make sure any changes in scope are handled in a way that doesn’t add risk to the overall goal.</p><p>Look out for the next set of entries from this developer to see how things can go from good, to bad, to ugly… to good! Send me an email if you see any other topics of conversation from my article here, would love to chat about them or any of your current projects.</p><p><a href="/service/mailto:luke.bashford@kinetechcloud.com?subject=Medium+article+reference+keys">Email Me!</a></p><p>luke.bashford@kinetechcloud.com</p><p><a href="https://www.kinetechcloud.com/kinetech/the-diary-of-a-mendix-developer-part-1-how-it-started">https://www.kinetechcloud.com/kinetech/the-diary-of-a-mendix-developer-part-1-how-it-started</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=419389c64058" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 Items Every Mendix Developer Should Consider Owning]]></title>
            <link>https://medium.com/@luke.bashford/top-10-items-every-mendix-developer-should-consider-owning-5941d6dd27c6?source=rss-09654efa590e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5941d6dd27c6</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[top-10]]></category>
            <category><![CDATA[lifestyle]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Luke Bashford]]></dc:creator>
            <pubDate>Mon, 12 Feb 2024 20:49:41 GMT</pubDate>
            <atom:updated>2024-02-12T20:49:41.784Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Khs65xDA3GXj06bLu4D0gQ.jpeg" /><figcaption>10 Products you wish you would have owned sooner</figcaption></figure><p>Long before I was a developer, I was a massive nerd. Believe it or not, I still am! I have spent most of my life exploring the best tech and also exploring how to best take care of myself. These two things go hand in hand when it comes to being a Mendix developer. In this article, I will share with you the top 10 items <strong>I think add the most value to my life</strong> when it comes to sitting at a desk all day for work, while representing myself as an expert in my field.</p><p><strong>10 — Water Bottle</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bWaLvUP_rMtuzzCmj6OZiA.jpeg" /></figure><p>This is a simple one, stay hydrated! As a Colorado native I grew up around everyone carrying around their Nalgene water bottle everywhere they went, like a safety blanket for all the mile high residents. Without your water bottle you would be a dry, dehydrated, crusty monster…</p><p>Sipping cold water at your desk while you work is an easy way to avoid dehydration, reduce headaches, lower stress levels, and improve your mental health. Here are a few easy wins if you don’t have a water bottle already!</p><p><a href="https://www.hydroflask.com/">Hydroflask</a> — $40 | This is the best of the best for cold drinks, especially water. I have only owned 2–3 different Hydroflasks in the past 10 years cause they just last. Mind you they look pretty battered and bruised after 10 years but they are still completely functional.</p><p><a href="https://nalgene.com/">Nalgene</a> — $20 | Best bang for your buck. A Nalgene isn’t going to keep your water ice cold all day, but for a desk job and on the go it’s a no brainer and will last you a lifetime. I swear the party trick in high school was to throw your Nalgene into the air and see how high it would bounce when it hit the ground… these things are virtually indestructible.</p><p><strong>9 — Yoga Mat</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_tkshSwGCfA-GN-wOSD4bA.jpeg" /></figure><p>Please don’t stop reading here, I know yoga isn’t for everyone and I’m not recommending you take up Sunday morning yoga by any means. A yoga mat is more of a way to give some time and space to yourself a few times a week. Learn a basic yoga flow, or work on some full body stretches. Either of these practices will feel really good and yield 100x their cost to your overall happiness and health.</p><p>Recommending a yoga mat is extremely difficult. The only advice I can give you is to get something a tad bit nicer than you think you can get away with. It will be very tempting to get that $20 Amazon basics yoga mat online, however you will feel a lot more joy and motivation to use your mat if you get something a bit higher quality, which will last you a long time.</p><p><a href="https://www.manduka.com/products/manduka-pro-yoga-mat">Manduka Pro</a> — $150 | Do you hate money? Do you like expensive and luxury items? get the Manduka yoga mat, unless you are a sweaty beast like me. These mats tend to be a bit slippery when you have any moisture on you hands or feet, however they are thick and comfy and don’t move around easily. My spine would always cry when I had to do stretches or poses on my back, the Manduka gave me enough padding to survive. I do recommend doing the salt treatment you can find online if you do get one of these mats, makes it a little bit grippier.</p><p><a href="https://shop.lululemon.com/c/yoga-mats/_/N-8pj">Lulu Mat</a> — $85 | A lot cheaper than the Manduka but still amazing quality. Not nearly as thick and luxurious but will give you the grip and comfort you need for most stretching and yoga</p><p><strong>8 — Polyhedral Dice</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q9WibMikXVUFphe8u1YQhQ.jpeg" /></figure><p>NERD ALERT!</p><p>Welcome to the thrilling world of Dungeons &amp; Dragons, where each combat round ignites the imagination and tests the mettle of adventurers. As the Dungeon Master sets the scene and tension builds, players grip their D20 dice, anticipation electrifying the air. With every roll, fate hangs in the balance, determining the outcome of epic battles and shaping the course of heroic quests. Join us as we delve into the heart-pounding start of your adventure, where strategy, luck, and storytelling converge in a realm where anything is possible.</p><p>This is not JUST a recommendation to buy some dice, but rather a push to get into something social that doesn’t use technology or screens very often. Tabletop gaming is a fantastic way to scratch your engineering/developer itch outside of working hours, while giving your eyes and brain a break from all of the client and office engagements.</p><p><a href="https://dnd.wizards.com/">Dungeons &amp; Dragons</a> — $0-$10,000| The absolute leader when it comes to tabletop gaming. Endless possibilities for creativity and fun, and all of it is open source so you could technically get started without spending a single penny. Now you could also go hard into D&amp;D, start your own campaigns, buy or 3D print your own minis, collect hundreds of polyhedral dice, etc… Just give it a shot!</p><p><a href="https://www.catan.com/">Catan</a> — $60 | Settlers of Catan is the gateway to tabletop gaming for so many people around the world. This game is the smallest step up from the ride-along games of the 90s where you don’t make decisions, you just spin wheels and hope to win. Catan has strategy, bartering, laughing and crying, and will be an overall great experience for anyone new to tabletop gaming.</p><p><strong>7 — Blue Light Protection</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yXW9JhO2y2a-38UBCPFXmg.jpeg" /></figure><p>Now you probably thought I was going to tell you to go buy some blue light glasses… I’m not. I tried wearing them for years and years and never really felt a lot of benefit from them. The reality of it was most of my eye fatigue came from just staring at a screen that was the same distance away from me for 8 hours a day, and having that screen be VERY bright.</p><p>The best way I reduced my eye strain was to turn down the overall brightness of my monitor and follow the 20/20/20 rule:</p><blockquote>Every 20 mins<br>Look 20 feet away<br>For 20 seconds</blockquote><p>Seems simple right, but it helped SO MUCH! Another thing you can do if you are looking for a more aggressive way to soothe your eye fatigue is to install <a href="https://justgetflux.com/">Flux</a> on your work machine for FREE. Flux will adjust your screen brightness and color temperature based on the time of day where you live.</p><p><strong>6 — Dual/Triple or 4k Display</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rZ2mb5INcZU84XPvAVirQ.jpeg" /></figure><p>Ok… now we are getting into the REAL life-changing items in this list. Are you still working on a single monitor in 2024? If so, you are about 15 years behind all the cool kids. Double monitor setups not only increase the amount of visual desktop space you must work with, but also give you so much more flexibility with customizing your workspace. You can improve your responsiveness by having your Slack, email, and Teams windows on one screen, while your modeler and documentation are on another screen. You must tab through windows far less and can move from one task to another seamlessly.</p><p>Did anyone say triple monitors?</p><p>How about a 4k OLED? This is basically 4 1080p monitors all in 1 screen.</p><p>I won’t give any specific recommendations here, but I will caution you that anything over a single additional monitor often requires specific GPU hardware to run successfully. If you are using a work-issued laptop for development, a single external 1440p 120hz display is the best investment you can make to upgrade your digital workspace!</p><p><strong>5 — Mechanical Keyboard</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QgjFofNMyIY91C00EOpR8w.jpeg" /></figure><p>Welcome to another slippery slope of tech gadgets. I’ll keep this one short simply because the adventure of discovering mechanical keyboards is a joy in itself. A mechanical keyboard is one of those things that isn’t going to improve your typing speed or productivity, but it is something that will bring you so much JOY.</p><p>Imagine being a professional dancer for a moment, but you never invested more than the bare minimum in your dance shoes. Using a $15 Logitech keyboard for your daily work keyboard is about the same level of missed potential. Sure, it won’t make you a better dancer to get new shoes, but you will be more comfortable in better shoes, they will last longer, and they will [once again] BRING YOU JOY. Are you seeing a theme here? Everything I’m recommending has some impact on your happiness, the absolute most important part of anyone’s life, especially when balancing a demanding career like being a Mendix developer.</p><p>I will give you a gentle push in the right direction for mechanical keyboards, the rest of the research is in your hands (pun intended).</p><p><a href="https://epomaker.com/products/cidoo-abm098">CIDOO AMB098</a> — $120 | Built like a tank, incredible switches, very quiet, and customizable more than you will ever need. If you want to just take a leap here and trust me, buy this keyboard. You will be shocked at the quality of this mechanical keyboard for under $150.</p><p><strong>4 — Espresso Machine</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MBODeEg0UUHiI0kJQDjduA.jpeg" /></figure><p>I’m quickly realizing that the best things in life come at a price, and espresso is one of those.</p><p>Here is my anecdotal reason to buy your own espresso setup for you home.</p><blockquote>Drink coffee every workday<br>Go to Starbucks, spend $5 on a chai latte or whatever you drink<br>Do this for a year<br>250 working days per year = $1250 on coffee</blockquote><p>Instead, buy these two items instead <em>(Note: Refurbished versions of both of these are available online for about 40% off and are highly recommended. The components that wear out are easily replaced and a refurb unit is just as reliable as a brand new one)</em></p><p><a href="https://www.gaggia-na.com/products/gaggia-classic-pro">Gaggia Classic Espresso Machine</a> — $450 | This is the go-to entry level espresso machine on the market.</p><p><a href="https://www.seattlecoffeegear.com/baratza-sette-270-grinder">Sette 270 Coffee Grinder</a> — $400 | The grinder is far more important than the brewing machine, this grinder will last you decades and give you great control over your grind size for all sorts of coffee whether it be espresso, pour over, drip, etc.</p><p>Get some local beans from a roaster in your hometown and learn how to grind, tamp, and brew espresso at home! The process is a joy each morning and the coffee is 10x better than what you will get at any chain coffee shop.</p><p><strong>3 — Standalone Webcam</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qhzfXFr67l8GS-AId1C4aA.jpeg" /></figure><p>Look good, feel good, right? Let’s be honest, we have all been on a call with a client or a colleague and we all turn on our cameras to be as social as possible. There are always at least a few people who are using their laptop camera, on their lap, in a dimly lit room, showing us the not-so-professional looking underside of their neck or forehead. Judgement aside, there is a very simple way to represent yourself visually in a much more professional manner, and that is with a standalone webcam.</p><p>Logitech C920 — $70 | Just do it. The visual fidelity and field of view are far superior to any built-in webcam and will make you look so much more professional to your colleagues and clients! We are working in tech after all, why not show that we pay attention to the details here.</p><p><strong>2 — Standalone Microphone</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f6GDPPhZlzri8pCJWCQlRg.jpeg" /></figure><p>Absolutely nothing is more frustrating that trying to talk to someone online and not being able to hear them over the background noise or the distortion from their built in mic on their laptop.</p><p>I run a setup at my home office that is extreme overkill for development calls, however I receive so many compliments that my audio is always so clear and crisp, as if I’m sitting right next to someone. You don’t need to spend a fortune to upgrade your audio setup at home to improve your call audio quality by 300%</p><p><a href="https://www.logitechg.com/en-us/products/streaming-gear/yeti-premium-usb-microphone.988-000103.html">Yeti Microphone</a> — $110 | Sleek, effective, desktop mount, and USB compatible. No additional equipment is needed to start using this microphone other than some <strong>headphones to create a closed loop audio system</strong>, so you don’t get feedback from your speakers back into the microphone.</p><p>Any headphones you enjoy. The benefit here is that you can get a lot better headphone if you don’t have to worry about getting one that has a built-in microphone, this always lowers the quality of the audio drivers when they are part of the same piece of tech.</p><p><strong>1 — Ergonomic Chair</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8-B_CfF8I9YcJ-Xw5cudA.jpeg" /></figure><p>OK now you can stop reading, because I’m about to recommend the most expensive item on this whole list but arguably the most important.</p><p>You MUST have an ergonomic chair. Now hear me out cause I’m about to sound like your parents here. You are young right now and you could sit and build microflows while sitting on a stack on 15 pizza boxes all day and be perfectly fine. However, once you get into your 30s and older, you are going to start realizing that you are not so impervious to the long-term effects of sitting hunched over like a shrimp for 8 hours a day.</p><p>You can get a better and more ergonomic chair starting at about $300 for something reasonable. The industry standard though, starts with the Aeron.</p><p><a href="https://store.hermanmiller.com/office-chairs-aeron/aeron-chair/2195348.html?lang=en_US&amp;sku=100077411">Aeron</a> — $1400 | Now wait! Don’t go spending $1400 retail on these. Lifehack, look on your local online marketplaces and see if there are any up for sale secondhand. Oftem times tech companies will have purchased a hundred of these for their employees and now that working from home has caught on, they have huge inventories of “used” Herman Miller chairs at a fraction of the cost…. seriously if you are luicky you can find an Aeron for about $550, just make sure you research which size you need before getting one.</p><p><a href="https://store.hermanmiller.com/home-office-chairs/embody-chair/4737.html?lang=en_US&amp;sku=100147408">Embody</a> — $Arm-and-a-leg | Ok really? Yes I have this chair, no I didn’t spend this much on it. Yes it’s worth it. No you don’t need it.</p><p>What can we take away from all these recommendations? I feel like the overall message here is to focus on your happiness and the things that make your everyday life more enjoyable and sustainable. Don’t mistreat your body because you are simply charging it to the game, and don’t underrepresent your skill and expertise as a Mendix developer by using the most entry-level hardware to do your job.</p><p>DO BETTER!</p><p>Thanks for reading. Please reach out if you have any questions or want to talk about anything I listed above. It would make my day to chat with someone about mechanical keyboards for an hour ❤</p><p><a href="/service/mailto:luke.bashford@kinetechcloud.com?subject=Medium+article+reference+keys">Email Me!</a></p><p>luke.bashford@kinetechcloud.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5941d6dd27c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Why waste time build many association when few entity do trick?”]]></title>
            <link>https://medium.com/@luke.bashford/why-waste-time-build-many-association-when-few-entity-do-trick-b5603bcca6a8?source=rss-09654efa590e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5603bcca6a8</guid>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[data-management]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[domain-model]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Luke Bashford]]></dc:creator>
            <pubDate>Fri, 02 Feb 2024 03:49:33 GMT</pubDate>
            <atom:updated>2024-02-08T16:15:18.741Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Kevin Malone from The Office, probably</em></p><h3><strong>The Problem</strong></h3><p>So… you are being tasked with building a Mendix application where you need to be able to generate a large amount of data across many objects. Your domain model is a spiderweb of entities and associations, your microflows are starting to look like a multigenerational family tree, and updating any new parameters down the road feels like a daunting task. You could probably benefit from a system that can handle the configuration and generation of everything all at once!</p><p>Meet my good friend, the Reference Key!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*94yy4AIiWzLVdGZefyc9Ow.png" /><figcaption>“I can’t carry it for you, but I can carry you.”</figcaption></figure><h3>One Entity? Enlighten Me!</h3><p>One thing to understand first about the Reference Key is that it is not the same for everyone. It’s extremely loyal, follows the rules, and can be told to do anything with perfect understanding of the desired outcomes. You will need to use the Reference Key in unique ways depending on your situation, however the process and outcomes are largely the same.</p><p>With a reference key entity in your application, you have the freedom to set up everything possible beforehand, and any changes in the future require no additional development. If the application demands a new object to be triggered from a complex selection of entities, simply add an association from that object to the desired reference key</p><p><em>Are you still listening? Trust me, keep reading! It will all make more sense in about 3 mins</em></p><h3>The Solution</h3><p>Let’s start with an example: You are a construction manager starting a project to build a new skyscraper in NYC. You need to configure and generate a project that contains all of the required applications to construct this building. Each of these applications can be triggered by selecting some combination of services. You have been provided a comprehensive list of all combinations of services and applications, but there are a TON of if/then constraints for something being included or not.</p><p><em>If the agency of the service is this, and the job type is that, then the application is this and that… if the agency is this and the job type is the other that…</em></p><p>You get the point… Don’t start building a behemoth microflow that uses decision splits and rules to handle directing all of this logic traffic. Set up something on the backend that can perfectly execute everything with simple instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*AqYzkm8m8IQrEnJKMFBE3A.png" /><figcaption>The project wizard will select some number of services, which each have a reference key.</figcaption></figure><p>The domain model above shows a basic reference key setup. We have Reference Key objects in the database that point to each of the agency, jobtype, and worktype entities. At runtime we configure a Reference Key for every combination of those 3 items. These are our core reference items, <strong>there can only ever be a single reference key</strong> <strong>for any combination</strong> of the 3 determining entities. Each unique combination will be added to the database during runtime for access during user workflows.</p><blockquote>ReferenceKey1 — Agency:NYC, JobType:New Building, WorkType:Foundation<br>ReferenceKey2 — Agency:NYC, JobType:New Building, WorkType:Structural<br>ReferenceKey3 — Agency:NYC, JobType:Alteration, WorkType:Plumbing<br>ReferenceKey4— Agency:Transit, JobType:Garage, WorkType:Lighting</blockquote><p>Now when we select 10 services for this project, these services can already be linked to their respective reference keys at runtime (via an import or manual entry), giving us a single point of reference for any other object in the database such as applications or requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*adTroYIXKIrenMR2ZEsHEg.png" /></figure><p>At this point you have a base structure for configuring a single point of entry for all reference entities in the entire application that use the reference key associated items (Agency, JobType, WorkType). This saves you the trouble of having to have an association to these 3 entities from every entity in the app. You also have a very simple database retrieve to get the related objects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*qy4ojr7_fJuCNlv3Tp-8wA.png" /><figcaption>Retrieve all the Applications that share a reference key with a service on this project, simple!</figcaption></figure><p>The list of reference keys from the services on this project allows you to iterate through and retrieve any linked objects to create an inclusion of these for this specific project, applications in this example. Repeat this with any reference entity in the database to build out an entire project from the single reference key entity. The only lift from a development standpoint from here is setting up the retrieve or create logic on save of the project for each entity that has a relationship to the entities the reference key uses.</p><h3>How About a tldr?</h3><p>If you find yourself building a TON of associations to the same reference tables, consider using a reference key entity to marry everything into one place. This will allow you to point to a single object instead of many, and massively simplify microflow logic.</p><h3>Long Term Benefits</h3><p>Once you have this system in place, all of your workflows are scaleable and future proof. If you add a new application to your system, just point it to the relevant reference keys and everything will generate when it needs to. If you add a new entity to your database, such as permits, you would need to create the master table of permits and set up all of their corresponding reference keys, then add in the iterative logic to retrieve or create the permit inclusions in the workflow explained above. Once you have that, permits are ready to expand your project creation workflow with minimal effort from a dev standpoint.</p><h3>Ask Me Anything!</h3><p>Sometimes it’s easier to share ideas and content face to face, especially with some context around any given problem. If you ever find yourself at the end of this medium article and want more info, reach out! I would love to connect and talk about your app.</p><p><a href="/service/mailto:luke.bashford@kinetechcloud.com?subject=Medium%20article%20reference%20keys">Email Me!</a></p><p>luke.bashford@kinetechcloud.com</p><p><a href="https://www.kinetechcloud.com/kinetech/why-waste-time-build-many-association-when-few-entity-do-trick">https://www.kinetechcloud.com/kinetech/why-waste-time-build-many-association-when-few-entity-do-trick</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5603bcca6a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>