{"id":10753,"date":"2017-07-31T06:05:59","date_gmt":"2017-07-31T13:05:59","guid":{"rendered":"https:\/\/www.seedcode.com\/?p=10753"},"modified":"2017-07-31T06:05:59","modified_gmt":"2017-07-31T13:05:59","slug":"increasing-code-quality-staying-lean","status":"publish","type":"post","link":"https:\/\/seedcode.com\/increasing-code-quality-staying-lean\/","title":{"rendered":"What Works – Increasing Code Quality While Staying Lean"},"content":{"rendered":"

Update: the video of this session<\/a> 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>.<\/em><\/p>\n

\n

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\u00a0for SeedCode–I really hope you found\u00a0it useful.<\/p>\n

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<\/a> or on Slideshare<\/a>.<\/p>\n

<\/p>\n

Here’s the way the talk was described on the conference site<\/a>…<\/p>\n

Session Description<\/h3>\n

FileMaker lets you build new apps quickly and modify existing solutions just as fast. But if you\u2019re occasionally missing deadlines, accumulating unbillable work or shipping bugs, you\u2019ll learn six\u00a0techniques to dramatically increase quality while working quickly.<\/p>\n

In this session, learn what\u2019s 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.<\/p>\n

Recommended Background<\/h3>\n

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.<\/p>\n

Session Objectives<\/h3>\n

\u2022 Break deliveries into smaller pieces to reduce the cognitive load (and risk) for developers AND customers<\/p>\n

\u2022 How recording short (< 3 minute) videos makes the mental shift necessary for QA while reducing turnaround time for customers validating your work<\/p>\n

\u2022 Simple strategies for recording \u201ctechnical debt\u201d as you go, so you can jump into cold projects much more quickly.<\/p>\n

\u2022 Why documenting your dev decisions creates a path from the customer\u2019s use cases to the code that addresses them<\/p>\n

\n

<\/a><\/p>\n

Update: Video Posted<\/h2>\n

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