software solutions / project leadership / agile coaching and training
SERVICES
SOFTWARE SOLUTIONS
I have over 15 years of software development experience on several different platforms (.NET, Ruby, JavaScript, SQL Server, and more).
I recognize that software is expensive,
so I'm always trying to find ways to speed up the software development process, but at the same time
remembering that high quality is essential to building software that stands the test of time.
PROJECT LEADERSHIP
I have experience leading and architecting large Agile software
projects and coordinating all aspects
of a project's lifecycle. Whether you're looking for technical expertise or someone
to lead all aspects of an Agile project, I have proven experience from multiple projects
in different environments that can help make your project a success.
PROCESS COACHING
Every team and every situation is different, and I believe that processes and tools should be applied with common sense. I've spent the last 10+ years working on projects using Agile and Lean concepts in many different environments, both in leadership roles and as a practitioner doing the work. I can help you develop a process that works best in your organization, not just apply a prescriptive process.
Have any questions? Contact me for more information.
PRESENTATIONS
|
From Stir Trek 2017
|
|
|
Iteration Management - Your Key to Predictable Delivery
From Stir Trek 2016 and QA or the Highway 2015
|
|
|
From CodeMash 2016, QA or the Highway 2014, Stir Trek 2012
|
|
|
The Business of You: 10 Steps For Running Your Career Like a Business
From CodeMash 2015, Stir Trek 2014, CONDG 2012
|
|
|
From Stir Trek 2013, DogFoodCon 2013
|
|
|
(presented with Brandon Childers, Chris Hoover, Laurel Odronic, and Lan Bloch from IGS Energy) from Path to Agility 2012
|
|
|
From CodeMash 2012 and 2013
|
|
|
(presented with Paul Bahler and Kevin Chivington from IGS Energy)
|
|
|
From CodeMash 2011
|
|
|
An idea of how to make JavaScript testable, presented at Stir Trek 2011. The world of JavaScript frameworks has changed greatly since then, but I still agree with the concepts.
|
|
|
A description of how test-driven development works along with some hands-on examples.
|
|
|
From CodeMash 2010
|
|
|
From CodeMash 2010
|
ABOUT ME
I am a software developer in Columbus, OH, specializing in software solutions, project leadership, and Agile coaching and training in a wide range of industries and environments. Find out more here...
Resume
Twitter: @JonKruger
GitHub
LinkedIn
Send me an email!
RSS
Comments RSS
Search
Team-based organizations vs. role-based organizations
Impostor syndrome is bringing us down
A WFH Retrospective
Moving past the monolith, Part 8 – Planning ahead
Moving past the monolith, Part 7 – Splitting up your client-side applications
Moving past the monolith, Part 6 – Using package managers to share common code
Moving past the monolith, Part 5 – Minimizing sharing between modules
Moving past the monolith, Part 4 – Using the Service Object pattern
Moving past the monolith, Part 3 – Think about how you share data
Moving past the monolith, Part 2 – Separating your data
Moving past the monolith, Part 1 – Organizing your code into modules
Moving past the monolith
Leaving the comfortable
There’s more than one way to change the world
JavaScript Fatigue is a thing, get used to it
Understanding the strengths of others (and yourself)
Statically typed Ruby? Don’t call me a heretic
Don’t break stuff
Encouraging innovation
Twitter: @JonKruger
GitHub
Send me an email!
RSS
Comments RSS
Search
Recent Posts
Wanted: Technical problem solversTeam-based organizations vs. role-based organizations
Impostor syndrome is bringing us down
A WFH Retrospective
Moving past the monolith, Part 8 – Planning ahead
Moving past the monolith, Part 7 – Splitting up your client-side applications
Moving past the monolith, Part 6 – Using package managers to share common code
Moving past the monolith, Part 5 – Minimizing sharing between modules
Moving past the monolith, Part 4 – Using the Service Object pattern
Moving past the monolith, Part 3 – Think about how you share data
Moving past the monolith, Part 2 – Separating your data
Moving past the monolith, Part 1 – Organizing your code into modules
Moving past the monolith
Leaving the comfortable
There’s more than one way to change the world
JavaScript Fatigue is a thing, get used to it
Understanding the strengths of others (and yourself)
Statically typed Ruby? Don’t call me a heretic
Don’t break stuff
Encouraging innovation
One gotcha that I ran into recently was cancelling an AddNew(), and a blank row was still in the BindingList. The workaround to this is calling the CancelNew method from ICancelAddNew, which the BindingList implements.
Matt Casto — March 12, 2007 @ 11:54 am
Getting the most out of .NET data binding…
You’ve been kicked (a good thing) – Trackback from DotNetKicks.com…
DotNetKicks.com — April 24, 2007 @ 1:56 pm
Nice. Definitely saved. Couple questions/points:
Your person object isn’t thread safe; you should always assign your event to a temp variable, then check that variable to see if its null prior to invoking the event.
Why would you want to explicitly implement IDataErrorInfo? Is it in case your Person object already has an indexer that isn’t listed in the code at the top?
mcgurk — April 24, 2007 @ 2:20 pm