What Works – Increasing Code Quality While Staying Lean

Update: the video of this session has been posted. And we’ve started to publish the original blog posts this was based on, along with things we’ve learned since: What Works.


A big thanks to everyone who came to my DevCon session, and especially to those who asked questions! It was great getting to share some of the things that have made a big difference for SeedCode–I really hope you found it useful.

As I mentioned in the intro, this came out of a series of blog posts we wrote as KC was joining the company. We wanted to capture what was unique here (and what was working) so that we could pass that on to him, and we ended up with this pretty cool playbook for how we go fast. A recording of the session should be up soon. In the meantime, you can find the slides on the FileMaker Community or on Slideshare.

Here’s the way the talk was described on the conference site

Session Description

FileMaker lets you build new apps quickly and modify existing solutions just as fast. But if you’re occasionally missing deadlines, accumulating unbillable work or shipping bugs, you’ll learn six techniques to dramatically increase quality while working quickly.

In this session, learn what’s proven to work for SeedCode when delivering both large custom projects, as well as quick little mods. Importantly, these are techniques you can implement without hiring new staff and without slowing down.

Recommended Background

This is a not a technical session, and the techniques here apply to in-house developers, solo developers, and folks running larger firms. In fact the smaller you are, the more impact these kinds of efficiencies can make.

Session Objectives

• Break deliveries into smaller pieces to reduce the cognitive load (and risk) for developers AND customers

• How recording short (< 3 minute) videos makes the mental shift necessary for QA while reducing turnaround time for customers validating your work

• Simple strategies for recording “technical debt” as you go, so you can jump into cold projects much more quickly.

• Why documenting your dev decisions creates a path from the customer’s use cases to the code that addresses them


Update: Video Posted

FileMaker posted a recording of the session here. The video doens’t show me (thankfully) just the screen and audio, but it works. Enjoy!

Featured Posts

Follow Along

Stay up to date with the latest news & examples from SeedCode

4 Comments

  • Dan Shockley

    I believe this session will have the most dramatic impact on improving our team’s work. One of the best sessions at DevCon this year. Thanks for making the materials available, and I’m looking forward to having the video so the rest of my team can see it.

  • I’m sure all will become clear when the Devcon video is available, but I’m a little impatient. This looks like an excellent session and I wish I could have seen it. Can you offer any more details on the video portion of the discussion? Are they stored in the client’s solution? Do you put the on the web somewhere (Unlisted YouTube perhaps)? I used the method one time and found it helpful, but at your suggestion I’m considering making it a practice. Many thanks!

    • seedcode

      Thanks for asking. The videos are short: 3-5 minutes. The app we use to record uploads them to our server automatically at the end of recording, so it’s super easy for us. (The videos are public but with an obscuring url.) We then email the video to the client along with a short note. For recording we use http://screencast-o-matic.com and https://www.monosnap.com/
      Hope that helps!

  • Damian

    Feeling guilty about almost doing something ‘more technical’ on what was actually the most important session from Devcon. Our in house bug tracking piece of c* is now on the way to the bin.

Leave a Reply

Your email address will not be published. Required fields are marked *

Check out some of our other posts ...

New Week Views in DayBack for FileMaker

You can now expand DayBack’s week views to show two or three weeks at a time. We’ve been using this internally in beta mode for a few weeks, and it’s very helpful to see what’s coming up next week while navigating this week’s work. Find tips on how to work with these new views on the DayBack blog.

To-Do Lists in FileMaker – New in DayBack Calendar

Now create and manage FileMaker to-do lists directly from the Unscheduled Items sidebar in DayBack Calendar. Our latest extension brings to-do behavior to any FileMaker table. Like unscheduled items, this behavior is based on a new checkbox field in your table, so some or all of your records in the table can be treated as to-dos. Mark your to-do’s done as you complete them, or drag them into the calendar to schedule time to work on them. See it in action here: Customize Your To-Do Lists This extension was designed to be pretty a scaffold onto which you could build your own, more specific to-do behaviors by customizing the action itself or the FileMaker scripts tha manipulate events. Here are some ideas to get you started. Add To-Do Lists to Your FileMaker Calendar If you haven’t already enabled the unscheduled sidebar along DayBack’s right edge, you can learn how to turn that on here: unscheduled items in DayBack. Then, download the custom action and learn how to configure it here: To-Do Lists in DayBack Calendar.

Improved Resource Selection

We’ve made some big changes to how you filter and assign resources when editing events in DayBack. These changes will make it much easier to work with large numbers of resources, especially for folks assigning multiple resources to the same event. Watch a video of the new behaviors and learn more here: Adding Multiple Resources to an Item. If you haven’t looked at your resource field mapping in a while, here is how you set that up: Mapping the Resource Field in FileMaker. Please get in touch if you have any questions about this; we’re here to help.

Suggesting Appointment Slots

Show Available Slots that Match Multiple Criteria Schedulers often look for gaps in their schedules to find the open resources for each opportunity. But sometimes, gaps don’t tell the whole story. You may have invisible criteria like skill-matching, cleaning requirements, or multiple resources to schedule at once. Or you may be on the phone with an opportunity and must suggest available times as quickly as possible. In these cases, DayBack can suggest the best slots that match all of your requirements. Scheduling Criteria Are Often Invisible In the movie above, schedulers can see openings for the two technicians, but they can’t easily see if the required rooms and equipment are free at the same time. While DayBack can show different types of resources simultaneously, as the number of criteria increases, it can be hard for schedulers to see everything at once and still make good decisions. Our customers often have rules that constrain when an otherwise open slot can be scheduled. Here are some of the invisible criteria we’ve built out for customers: Because DayBack is highly scriptable, it can scrub open slots against a variety of criteria to render just the slots that fit all your requirements. When multiple slots match, DayBack can even rank them so you can present the most ideal slots to your clients first. You Have to *See* Slots in Context to Make the Best Decisions Many scheduling apps present possible appointments as a list of dates and times. Without showing more information about each slot, schedulers can book days too tightly, always suggest the same providers first, or create huge gaps in some provider’s schedules. Ranking slots can help, but we’ve found that highlighting ideal slots alongside existing appointments gives schedulers the information they need to make the best decisions. We’ve seen schedulers quickly offer to split appointments or to slightly change services when they see available slots in the context of other appointments, trainings, vacations, and breaks. Getting Started We customize the recommendation of slots for each deployment as part of DayBack’s implementation packages. Please get in touch if you think DayBack could make a big impact on your team.

COMPANY

FOLLOW ALONG

Stay up to date with the latest news & examples from SeedCode

© 2024 SeedCode, Inc.