Building useful software, exploring new ideas, and sharing what we learn.
Coding Moves is a growing software and technology initiative built around a simple idea: make things that are useful, learn by building, and share work that can help other people.
What began as a place to experiment with software and technical projects can grow into something broader: an umbrella for open-source projects, research and experiments, our own products, and software services for clients. We want to keep room for curiosity while also taking real-world software needs seriously.
This repository is the starting point for that bigger picture. As Coding Moves grows, the sections and links below will lead to the different parts of our work.
Some parts of Coding Moves are active today; others are plans for the future. We will add them as we build them, rather than pretending everything is already in place.
Coding Moves brings different kinds of software work together under one name. That includes projects we build for learning, tools we share with the community, ideas we test, products we develop, and solutions we create for clients.
We believe good software comes from understanding the problem first, making thoughtful decisions, and improving the result through feedback. Not every experiment will become a product, and not every project needs to be open source. We want to be clear about what each project is for and how people can use it.
The links below are the intended entry points for each part of Coding Moves. We will add the live links as each page or initiative becomes available.
Area What you will find Link
Coding Moves The main home for the Visit the website
Website Coding Moves identity,
current work, and
updates.
**Coding Moves Open Public repositories, Explore open
Source** community tools, source
contributions, and
projects others can
inspect, use, or
improve under their
licenses.
Coding Moves Lab Experiments, Explore the lab
prototypes, technical
explorations, and early
ideas---especially in
software, AI, and
machine learning.
Coding Moves Software development Explore services
Services services for
businesses,
organizations, and
individuals who need a
practical solution to a
real problem.
Coding Moves Software products and Explore products
Products reusable tools
developed under Coding
Moves.
Research and Notes, investigations, Explore research
Experiments prototypes, and lessons
from trying out
technical ideas.
About Coding Moves Our story, approach, Learn about us
and the people behind
the work.
Contact and Project A way to discuss a Get in touch
Inquiries project, ask a
question, or explore
working together.
Note: The # links are placeholders. Replace each one with the
correct URL when the relevant page is published. If a section will live
on the main website, it can use a path such as /services or /lab; if
it has a separate repository or page, link directly to it.
Open source is an important part of how we learn and contribute. We want to build and maintain useful projects, make selected code available for others to study, and support the wider developer community.
Depending on the project, this may include:
- Developer tools and utilities.
- Web applications and small software products.
- AI and machine-learning experiments that are suitable for public release.
- Documentation, examples, and learning resources.
- Contributions to existing open-source projects.
Each repository should explain what the project does, how to run it, its current status, and how people can contribute. Every project will have its own license and contribution guidance where appropriate.
Public visibility does not automatically mean that every project is open source. A repository is open source when its license and permissions allow others to use, study, modify, and share the code.
The Lab is where we explore ideas and learn by building. It gives us room to test approaches, make prototypes, investigate problems, and decide whether an idea deserves more time.
Areas of interest may include:
- Artificial intelligence and machine learning.
- Data processing and automation.
- Developer experience and software engineering.
- Web technologies and application architecture.
- Small experiments that answer a specific technical question.
Lab projects may be unfinished or experimental. We will try to label their status honestly so visitors can distinguish a proof of concept from software that is ready for everyday use.
An experiment does not need to become a product to be worthwhile. Sometimes the most useful result is what we learn and share along the way.
Coding Moves Services is the planned home for paid software development work. The aim is to help clients turn a clear need into software they can actually use and maintain.
Depending on the project and our available capacity, services may include:
- Business websites and web applications.
- Custom management systems and administrative dashboards.
- Inventory, billing, and record-management workflows.
- Database design and application integrations.
- AI integrations and workflow automation.
- MCP server and tool integrations.
- Maintenance, improvements, and technical support for existing applications.
We will take on work based on the requirements, timeline, technical fit, and our ability to deliver it responsibly. Not every request will be a good fit, and we will aim to discuss scope and limitations before work begins.
- Understand the need. Discuss the problem, intended users, and desired outcome.
- Agree on the scope. Define the features, deliverables, timeline, budget, and responsibilities.
- Plan the solution. Choose an appropriate architecture and technology stack.
- Build and test. Develop in manageable steps and check the important workflows.
- Deliver and hand over. Provide the agreed application, documentation, and access.
- Discuss ongoing support. Agree separately on maintenance or future improvements where needed.
The exact process will depend on the size and nature of the project. Clear expectations and regular communication matter more than promising every feature immediately.
Client work is handled according to the agreement made for that project. Before development starts, the client and Coding Moves should clarify source-code ownership, licensing, deployment, access, confidentiality, third-party services, and any permission to feature the work publicly.
A completed project may be shown as a case study only when we are allowed to share the relevant details. A case study can describe the problem and outcome without exposing private data, credentials, internal workflows, or source code.
Alongside client work, we may develop our own software products. A product could begin as a Lab experiment, become useful to a wider group of people, and then receive the documentation, testing, support, and ongoing development it needs.
Some products may be free or open source; others may use a paid, hosted, or commercial model. We will explain the availability and terms of each product individually rather than treating every project as having the same model.
We want Coding Moves to be a place where practical work and learning can support each other. When it is useful and appropriate, we may share technical notes, implementation decisions, experiments, and lessons learned.
Research and experimental results should be described honestly. A prototype is not necessarily production-ready, and a promising test is not proof that a method works in every situation. We will aim to make those distinctions clear.
Across our work, we aim to follow a few practical principles:
- Solve the real problem. Understand what people need before choosing a technology.
- Keep things understandable. Prefer clear code, useful documentation, and designs that can be maintained.
- Be honest about status. Say whether a project is experimental, in progress, or ready for use.
- Respect users and clients. Handle data, credentials, access, and confidential information carefully.
- Choose tools for a reason. Use technologies that suit the requirements instead of adding complexity for its own sake.
- Learn and improve. Take feedback seriously and revisit decisions when evidence shows a better approach.
- Share responsibly. Publish code and project details only when the rights, license, and confidentiality requirements allow it.
- Build for the long term. Consider reliability, accessibility, security, and maintainability---not just getting a demo to work.
These are the standards we want to keep working toward as Coding Moves develops.
The technologies used will vary from project to project. We work with tools that fit the problem and our team's capabilities, and we will list the actual stack in each project's README rather than claiming a fixed stack for the entire organization.
If you have a project idea, a software problem, or a possible collaboration, use the contact link on our website once it is available. It helps to include:
- A short description of the problem.
- Who will use the software.
- The most important features or outcomes.
- Any preferred deadline or budget range, if known.
- Any existing system or technical constraints we should understand.
You do not need a complete technical specification to start a conversation. We can first work out what is needed and whether the project is a good fit.
For open-source contributions, start with the relevant repository's README and contribution instructions. Project-specific guidance takes precedence over general information in this organization README.
Coding Moves is being built gradually. Some projects and services may be available now, while other areas described here are future directions. We will update this README as pages launch, projects mature, and our process becomes more established.
We would rather show real work and communicate its status clearly than make promises we cannot yet support.
For projects where it is appropriate and agreed, we may include a credit such as:
Developed by Coding Moves
The final attribution and its placement depend on the project agreement. Client branding, ownership terms, and any white-label requirements take priority where agreed. Attribution does not, by itself, determine who owns the software.
Website: Add the Coding Moves website URL
Services: Add the services page URL
GitHub organization: Add the Coding Moves organization URL
Project inquiries: Add the preferred contact method
Replace these placeholders with the official links before publishing.
Coding Moves is a work in progress---in the best sense of the phrase. We are here to build useful things, explore ideas, contribute where we can, and grow through the work itself.
Built step by step, with curiosity and purpose.