The people on our team have experience with public-sector information systems, telecommunications, payment terminals and AI solutions. During delivery, we manage estimates, dependencies between teams and risks that may affect completion. Here are six principles we work by.
A report is a claim. A working product is evidence. From the first weeks of the project, we review completed features from the user’s perspective, using data representative of real operations. This helps us find defects before they affect other parts of the system.
An estimate describes the amount of work we expect. Feasibility depends on specific people, dependencies and deadlines. If the plan does not work, we adjust the scope, sequence of work, team or allocation of responsibilities. For risks, we describe the potential impact, options and deadline for a decision.
Customers often need a simpler solution than engineers would like to build. We do not cut corners on security, data integrity, permissions, recovery or usability. For additional features and automation, we consider what problem they solve and whether the benefit justifies the cost.
The project’s core is a small senior team with clear responsibilities and access to specialists. We staff your project with senior professionals. As code output grows, we focus on review, integration and the team’s understanding of the system.
A problem between two providers is still a problem for your project. We take it on. We address dependencies between applications, infrastructure and teams and agree who is responsible for connecting them.
We design diagnostics, automatic recovery from selected failures and procedures for the operations team. Handover includes documentation and training. Together, we check which operational tasks your team can handle independently.
Cloud, your own data centre or both. We build Kubernetes on-premises, run AI on our own GPUs and handle migrations to and from Azure, AWS and GCP. We get to know your business, work out the costs, risks and vendor lock-in, and tell you straight what speaks for and against each option. If you need to process data in Europe, we account for that in the design and service selection. You decide, we build it.
“We’ll have it up in a couple of days” is the most common lie in the history of software. It is usually said by someone who sees their own piece and not the whole. Valdemar Závadský’s book is about who is supposed to see the whole, and what to do the moment they hear that sentence. It is not a methodology, it is a way of looking at things that we apply on every project at Cloudfield. You are welcome to argue with it, and we would be glad to talk it over with you. The book is in Czech.
I want to read the bookWe also share tools: Reviewer for website feedback and Shieldoo Gate for controlling software dependencies. Their code is open, and you can run them in your own environment.
We also take over projects already in progress from other providers. We assess the current state and obstacles to completion and propose next steps. We agree the scope and timing of the assessment based on the project.
Tell us what costs you the most time, money or operational effort. Together, we will choose a first step and a way to measure its benefits.
info@cloudfield.czThe site does not work without strictly necessary cookies, so those are always on. Traffic and LinkedIn campaign measurement only switch on with your consent. Rejecting is as easy as allowing – no hard feelings. Privacy policy
The site does not work without them. We set just one, and it remembers what you chose in this banner.
cf_consent · cloudfield.cz · 1 year — Stores your cookie settings choice.Google Analytics shows us how many people visit the site and what they read. It does not tell us who you are.
_ga · Google · 2 years — Distinguishes visitors for traffic statistics._ga_2FE6EFFNHT · Google · 2 years — Keeps session state for Google Analytics 4.The LinkedIn Insight Tag measures whether our LinkedIn campaigns are any good. LinkedIn may link the visit to your profile while doing so.
li_sugr · LinkedIn · 3 months — Probabilistic browser identifier for campaign measurement.bcookie · LinkedIn · 1 year — Identifies the browser for LinkedIn services.lidc · LinkedIn · 1 day — Routes requests to LinkedIn's servers.UserMatchHistory · LinkedIn · 30 days — Syncs identifiers for LinkedIn advertising.AnalyticsSyncHistory · LinkedIn · 30 days — Time of the last sync with the lms_analytics cookie.li_fat_id · LinkedIn · 30 days — Attributes a site visit to a click on a LinkedIn ad.