A to Z Software Development Roles

Search This Blog

Software Development Roles: Skill Attributes Visualisation

This 3D scatter plot visualises various software development roles based on three key skill attributes:

  • Project Timeline (x-axis): Representing the spectrum from project start to project end.
  • Focus Orientation (y-axis): Spanning from people focused to technology focused roles.
  • Thinking Style (z-axis): Differentiating between operational thinking and strategic thinking.

Each marker represents a distinct role, with its position indicating the relative emphasis on each of these attributes. Use the chart to explore how different roles balance these skills. How one person in a 3D space could assume another role nearby in the space.

Click the "Reset Chart View" button to reset the chart to its default view.

Click the "Set Y and X Front View" button to set the chart to see Y on the left and X on the bottom.

Click the "Set Y and Z Front View" button to set the chart to see Y on the left and Z on the bottom.

Interacting with the 3D Scatter Plot:

Zoom:

  • Mouse Scroll: Scroll the mouse wheel up and down to zoom in and out.

Rotate:

  • Click and Drag: Click and drag on the plot to rotate it in any direction.
  • Right Click and Drag: Right-click and drag on the plot to pan it left, right, up, or down.

Reset Chart View:

  • Reset Button: Click the "Reset Chart View" button below the plot to reset the view to its default position (Y axis left, X axis bottom, and Z axis depth).

Explore:

  • Hover: Hover over a data point to see additional information about the role it represents.

"A" for Accessibility Specialist. Software Development Roles: A to Z

An Accessibility Specialist is responsible for creating and implementing accessibility solutions to ensure that software products are inclusive and accessible to users with disabilities. They collaborate closely with the development team to integrate accessibility solutions into code and provide training to employees on effectively using accessibility features.

Personal Story: I first encountered accessibility and the Web Content Accessibility Guidelines (WCAG) in the late 2010s while working on a patient healthcare product intended for use by everyone in society. The product needed to be accessible. Google had just released Lighthouse in Chrome’s Developer Tools, which proved to be an excellent tool for providing developers with insights into accessibility and other key areas. We also used other WCAG tools and text-to-voice tools to test our accessibility, along with Apple's accessibility features. Final Thoughts on Accessibility: Your product requires accessibility because: 1. It broadens the audience that can use your product. 2. It is a legal requirement under New Zealand law. Interesting Accessibility Fact: The first version of the WCAG was published in 1999.


By

Popular Posts