6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
2.7 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/7d10fcb2-b368-48ab-996b-7c9fafcf68ed | use automatic programming | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
use automatic programming — Database Administrator
For a Database Administrator (DBA), 'use automatic programming' isn’t about becoming a full-stack developer, but leveraging tools to automate repetitive database tasks. Think scripting common administration procedures – user creation/deletion, backup scheduling, performance monitoring checks, even basic schema changes. Instead of manually running SQL commands or GUI clicks for each instance, you use tools that generate those actions from defined specifications (like configuration files or templates). This could involve PowerShell DSC (Desired State Configuration) to enforce database server settings consistently across environments, or using scripting within database management systems like SQL Server's SQLCMD and T-SQL to automate tasks.
Typical daily work where this shines includes automating routine maintenance windows – generating scripts to rebuild indexes during off-peak hours, checking disk space utilization and alerting if thresholds are met, or creating reports on database growth trends. Tools often used include scripting languages (PowerShell, Python), configuration management tools (Ansible, Chef, Puppet), and the built-in procedural languages within the DBMS itself (PL/SQL for Oracle, T-SQL for SQL Server). Good DBAs don't just run these scripts; they version control them, document their purpose, and build in error handling & logging.
A common pitfall is trying to automate everything at once. Start small with well-defined, repeatable tasks. Overly complex automation can become brittle and difficult to maintain. Another issue is neglecting security – ensure generated code doesn't inadvertently introduce vulnerabilities (e.g., hardcoded passwords). Also, remember that 'automatic' doesn’t mean ‘hands-off’. You still need to monitor the automated processes for failures or unexpected behavior.
What good looks like: a DBA who can quickly provision new database instances with pre-defined configurations, automatically respond to performance alerts by running diagnostic scripts, and consistently apply security patches across all databases – without spending hours manually executing commands. This frees up time for more strategic work like capacity planning, performance tuning, and data modeling.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).