SShortSingh.
Back to feed

Overly broad training requirements block engineers from essential PLM access, creating shadow processes

0
·5 views

Engineers in regulated industries are often blocked from accessing Product Lifecycle Management systems due to expired training on irrelevant safety modules. This stems from companies assigning all training courses to all employees as a defensive compliance measure, rather than tailoring them to specific roles. For example, a software engineer can be locked out for missing a forklift safety course they will never need. This practice contradicts ISO 13485, which requires competence training to be appropriate to an employee's specific activities. The resulting delays and workarounds create shadow processes that can actually increase operational risk.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Tool detects hidden duplicate React copies that cause hook errors

A new command-line tool called onecopy helps developers identify duplicate React installations that cause 'Invalid hook call' errors. The tool addresses a scenario where npm ls reports only one version, but linked libraries or workspaces actually load separate copies from different directories. It works by tracing the actual file resolution path from each importing package's real location, grouping results by physical directory. The tool outputs which copies are being used, by whom, and the likely cause, and can be integrated into CI checks.

0
ProgrammingDEV Community ·

Developer details technical requirements for compliant data audit workbench

A developer writing for DEV Community argues that effective data audit systems should focus on creating immutable evidence pipelines rather than dashboards. They recommend capturing specific control events like access, export, and deletion in a hash-chained, append-only format to prove sequence integrity. Practical implementation requires object storage with write-once-read-many (WORM) locks and long retention periods, though this increases costs. The author also addresses challenges like handling high-throughput events and reconciling immutable logs with data erasure requests through technical patterns like salting personal data keys.

0
ProgrammingDEV Community ·

Hacktoberfest 2026 Weekend Challenge Offers Prizes for AI Projects

DEV Community has launched a weekend Hacktoberfest challenge where participants build a new project. The project must use open-source AI at its core to solve a real problem for a specific person. Submissions, which require a written post on DEV, are due by October 5 at 6:59 AM UTC. A total of $2,450 in prizes will be awarded to 17 winners, including one overall winner and 16 category winners for specific partner technologies.

0
ProgrammingDEV Community ·

Developer re-evaluates importance of test evidence over code metrics in AI era

A developer argues that test evidence, not just code coverage metrics, has become a crucial professional indicator of work quality. This shift in perspective followed a personal incident where a critical authentication bug was missed by unit tests but caught by a Docker-based test. The author notes that with AI-generated code becoming common, concrete proof of a system's reliability through field tests and failure reports is now more valuable. They have started publicly committing detailed test reports and failure lists to their repositories, which has led to constructive external audits and discussions.