Software engineering
Designing, building and maintaining software that stays correct as it grows: services, interfaces, data stores and the code that connects them.
Software engineering
- What it means
- Applying engineering discipline to software: requirements, design, testing, version control and review, so that a system can be changed safely for years.
- Problem it solves
- Software that works in a demonstration but fails under real use, or that nobody can modify without breaking something else.
- Practical applications
- Business systems and internal tools
- Rewrites and modernisation of legacy code
- Technical design and code review
- Technologies and methods
- Git
- Automated testing
- Code review
- Design documents
- CI pipelines
- Potential projects
- A records-management system for an institution
- A staged migration of a legacy application to a maintained stack
Backend development
- What it means
- Building the server side of an application: business logic, data access, authentication and background work.
- Problem it solves
- The need for one reliable place where rules are enforced and data is kept consistent.
- Practical applications
- Web and mobile application servers
- Background job processing
- Integrations with payment, mail and identity providers
- Technologies and methods
- Python
- FastAPI
- PostgreSQL
- Task queues
- Docker
- Potential projects
- A booking service with payments and notifications
- A reporting service that aggregates data from several systems
Frontend and web development
- What it means
- Building what people see and use in the browser, with attention to speed, accessibility and behaviour on every screen size.
- Problem it solves
- Interfaces that are slow, confusing, or unusable on a phone or with a keyboard.
- Practical applications
- Organizational and product websites
- Web applications and dashboards
- Accessible forms and public services
- Technologies and methods
- HTML
- CSS
- JavaScript and TypeScript
- Astro
- Tailwind CSS
- Potential projects
- A content-driven website with a publishing workflow
- An accessible data-entry application
API development and integration
- What it means
- Designing the interfaces through which systems exchange data, and connecting systems that were not built to work together.
- Problem it solves
- Data trapped in separate systems and manual copying between them.
- Practical applications
- Public and partner APIs
- Connecting internal systems
- Third-party service integration
- Technologies and methods
- REST
- OpenAPI
- JSON
- Webhooks
- OAuth 2.0
- Potential projects
- A documented API for an existing database
- A synchronisation service between two record systems
Python programming
- What it means
- Using Python as a primary language for services, automation, data work and machine learning.
- Problem it solves
- Repetitive manual work, one-off analysis needs, and the gap between a prototype and a maintainable program.
- Practical applications
- Automation scripts and command-line tools
- Data processing pipelines
- Web services and machine-learning code
- Technologies and methods
- Python 3
- FastAPI
- pytest
- pandas
- Packaging and virtual environments
- Potential projects
- A command-line tool that automates a reporting task
- A tested data-cleaning pipeline
Database engineering
- What it means
- Modelling data, designing schemas and queries, and operating databases so that data stays correct, fast to reach and recoverable.
- Problem it solves
- Slow queries, inconsistent records, and data that cannot be restored after a failure.
- Practical applications
- Schema design and migration
- Query and index tuning
- Backup and recovery planning
- Technologies and methods
- PostgreSQL
- SQL
- Supabase
- Row Level Security
- Schema migrations
- Potential projects
- A normalised schema for an application with access rules
- A performance review of a slow reporting database
Related services
Have a project or a question?
Describe what you need. Kansi reads every enquiry and replies by email.