The Issue Of Low IT Literacy

Day 323 of writing every day.

With two more days after today before I move on to kitting, things are kind of laid back but there’s an air of unease as well. It looks like the two other people I’ve been working with up to now just aren’t very sure of themselves and maybe I’ve done more than just pull my own weight thus far. Two people are leaving for their kitting assignments as well tomorrow, so the room is going to be a lot roomier starting tomorrow.

Though we should be past the point of having to revisit the design of the system, things still needed to be worked out so the group is on the same page and everyone shares the same vision of what needs to be built. Maybe the differences in vision also stem from differing levels of skills and general experience.

Another issue that was brought up when we went back to the drawing board to hash out some issues was that the client is next to IT illiterate, so things have to be really dumbed down and any ideas the group came up with to try and handle a variety of situations should be set aside to make sure the design has the basics working first.

Of course, making the primary functions of the system work is top priority, but sometimes the other members get distracted with what could be improved rather than what’s actually wrong and might cause a problem. Designs can always be improved depending on what the goal is and what the client wants, but once something is designed, it should be completed first and the known issues tracked as development goes. That is unless the design is fatally flawed to begin with.

Anyways, there’s always something to be learned even if the team seems to be going in a loop at times rather than pushing forward. Sometimes just being patient and listening can lead to new insights even if the issue brought up should already have been resolved.

Thanks for reading!

Leave a comment

search previous next tag category expand menu location phone mail time cart zoom edit close