AI-assisted software development & engineering.Independent evaluation of AI-generated code.
Describe what you want to build, fix or check. An engineer replies within one business day.
- ISO 9001 certified (DNV)
- Training eligible for BUR funding
- Engineers certified by Anthropic
- Member of the West Pomeranian ICT Cluster
- In business since 2012
This is what evaluating AI-assisted code looks like.
An evaluation starts with a sample of files or pull requests from your repository: each one gets a score against four criteria: correctness, security, maintainability and test quality. The result is a report with findings ranked by severity - like the one beside this text - and a walkthrough with your team. The service runs as a one-off or as continuous review, during the work and after release. This is not a tool: an engineer reads and evaluates the code, and findings land in your issue tracker, not in another dashboard.
Evaluation is one of the service areas at 23Minds ↓
01def get_user(req):02 uid = req.args.get("id")03 row = db.query(04 f"SELECT * FROM users WHERE id={uid}")05 tok = jwt.decode(t, verify=False)06 return row
AI training for leadership, product teams and engineering.
Programs for business, product and engineering teams: workshops priced per day, or a cohort program running over several weeks. The curriculum is built around your team's tools and the work they actually do. Exercises run on the team's own repositories and processes, not on generic AI examples.
AI Governance and EU AI Act Essentials
System classification, human oversight, rules for using AI.
Designing AI Use Cases That Reach Production
From an idea to a pilot with an end date and a decision.
Secure Coding with AI Assistants
Mistakes typical of assistant-written code, agent permissions, review rules.
AI-Assisted Development with Coding Assistants
Claude Code, Cursor and Copilot on your team's repository.
AI Literacy for Business Teams
Prompts for real work tasks, data you must not send, checking the answers.
Reviewing AI-Generated Code
What to check in a large AI-written change, and what blocks a merge.
Services
From code to production.
A working rhythm you can plan around.
- Week 1
Scope in writing
An intro call and an agreed scope: what you get, in what order, at what price. No commitment on your side.
- Month 1
The first tangible result
The first evaluation report, or the first working slice of the system on a preview. Findings land in your issue tracker.
- Quarter 1
A rhythm instead of pushes
Continuous review, retests after fixes, quality gates in your process. The team works with AI by agreed rules, not by feel.
- Year 1
The capability stays with you
Procedures, evaluation criteria and trained people are yours. 23Minds stays for the hard cases and for whatever changes in the tools.
Timelines are indicative and depend on scope; dates are set on the intro call.
Questions procurement teams ask.
Talk to an engineer.
Describe what you want to build, fix or check. A reply within one business day.