What to do, What to do

[swatts]

Hello Comrades in Coding

I hope all your wires are straight and true.

I have come back from Austin with a list of things to write about and come back from my vacation with an urge to purge my things to do list.

So in the spirit of full disclosure here's my current list of things to write about, with a brief synopsis.

Diary of a week in the life of....

I thought it might be interesting to scribble down my working week, perhaps we can compare and contrast.

Management Attitudes to LabVIEW

I've been witness to various instances where ill-equipped engineers are thrown at a project and not monitored in any way... explores why this is so.

People - Getting them to work together

Starting to think about team-based software development and how it may work out, the issues and egos etc etc.

Controversial thoughts on reuse

I have reached a conclusion (for SSDC) about re-use and how the dynamic is somewhat different if the speed of development is high.

Informal paths to software process

What are the easiest routes to a decent process, also will discuss process design techniques.

Open Source System Reference Designs

This is my big idea of the moment (it seems as if I'm the only one as usual).

Multi-Developer Teams - Subcontractor Method

I briefly touched on this in my presentation, I'll expand the idea.

Mindworks

Constructionism (learning theory)

The problem with software is people!

ranty rant rant rant, I love people really.

Requirement Zero

I've touched on this, will expand and add jokes and examples

Hire a Consultant or Not?

Recent events have pushed this up my list, some dos and don'ts

A few of these will involve more work than the usual 20 minute brain-dump so it may go quiet.

Are there any you would like me to do? If so the comments are the place to vote.

I can also do requests (stop writing stupid blogs on LabVIEW for example)

Much Love

Steve