Skip to main content

Good and bad habits

Craig Bailey pointed over to this older post by Paul Stovell - Craig's comments on the matter (speaking as a software manager) are just as insightful as Paul's and it reminds me of a recent discussion I was having with a colleague on our FoxPro projects. Paul's triangle diagram is wonderful - you have Resume quality code, production quality code and then prototype quality.

We typically set up a variety of milestones to go through projects, regardless of how small the project may be - and yet invariably, something can jump up - not unlike what's described in BugBash today - and thus throws the entire milestone process into a state of flux. "You have to get this done" or "help this person out" and at the end of the day, time isn't being taken to go through the various steps of the milestones.

We spec'd out a piece of work for an outsourcing resource recently and after reviewing the phase 1 and phase 2 milestones, the comment was "well, why not do it all in one piece?"

Sure, if you've got 10 separate pieces of code to write, why not write them all and THEN review them? (anyone care to guess why?)

We recently wrote up a series of coding guidelines for our outsourcing resources that we use as our primary code review (I mentioned a similar concept in an earlier post) - but one of the milestone steps we always try to incorporate both ways is simply a basic review. While you may not have time to do a proper code review, when handing off work to any resource, it's always useful just to have that "reality check", both on the phone and via shared screens.

One of the challenges? We're all in different locations. We use a variety of tools for this - none seems to do the job properly.

Anyone else face this problem? How do YOU deal with it?

PaulStovell.NET » We are what we repeatedly code

Powered by ScribeFire.

Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…