9:38:22 PM: Build ready to start
9:38:24 PM: build-image version: 8e315e54bc4032a32e73290be556cde4f8348c12
9:38:24 PM: build-image tag: v2.8.2
9:38:24 PM: buildbot version: b925d11411cabfe7b120501027bd0e96dbc28dde
9:38:24 PM: Fetching cached dependencies
9:38:24 PM: Starting to download cache of 225.2MB
9:38:25 PM: Finished downloading cache in 794.8542ms
9:38:25 PM: Starting to extract cache
9:38:32 PM: Finished extracting cache in 7.333988229s
9:38:32 PM: Finished fetching cache in 8.197678528s
9:38:32 PM: Starting to prepare the repo for build
9:38:32 PM: Preparing Git Reference refs/heads/trunk
9:38:33 PM: Found netlify.toml. Overriding site configuration
9:38:33 PM: Different publish path detected, going to use the one specified in the toml file: '_site' versus '/' in the site
9:38:33 PM: Different build command detected, going to use the one specified in the toml file: 'DEBUG=* npm run build' versus '' in the site
9:38:33 PM: Starting build script
9:38:33 PM: Installing dependencies
9:38:34 PM: Started restoring cached node version
9:38:36 PM: Finished restoring cached node version
9:38:37 PM: v8.16.0 is already installed.
9:38:38 PM: Now using node v8.16.0 (npm v6.4.1)
9:38:38 PM: Attempting ruby version 2.3.6, read from environment
9:38:40 PM: Using ruby version 2.3.6
9:38:40 PM: Using PHP version 5.6
9:38:40 PM: Started restoring cached node modules
9:38:40 PM: Finished restoring cached node modules
9:38:40 PM: Installing NPM modules using NPM version 6.4.1
9:38:47 PM: npm
9:38:47 PM: WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
9:38:47 PM: npm
9:38:47 PM: WARN notsup
9:38:47 PM: SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
9:38:47 PM: added 35 packages from 21 contributors and audited 11419 packages in 5.686s
9:38:47 PM: found 0 vulnerabilities
9:38:47 PM: NPM modules installed
9:38:47 PM: Started restoring cached go cache
9:38:48 PM: Finished restoring cached go cache
9:38:48 PM: Installing Go version 1.10
9:38:48 PM: unset GOOS;
9:38:48 PM: unset GOARCH;
9:38:48 PM: export GOROOT='/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64';
9:38:48 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64/bin:${PATH}";
9:38:48 PM: go version >&2;
9:38:48 PM: export GIMME_ENV='/opt/buildhome/.gimme_cache/env/go1.10.linux.amd64.env';
9:38:48 PM: go version go1.10 linux/amd64
9:38:48 PM: Installing missing commands
9:38:48 PM: Verify run directory
9:38:48 PM: Executing user command: DEBUG=* npm run build
9:38:49 PM: > @with-humans/website@1.0.0 build /opt/build/repo
9:38:49 PM: > run-s build:css build:siteBuild software with humans
Well tested, continuously delivered
As long as it has a testing framework, we'll be fine. Throughout our careers, we've worked in a plethora of different programming languages and we managed to get up to speed in no time.
We do have our preferences, but they always depend on the requirements and the context we're working in. We prefer pairing anyways, so if one of us or someone from your team knows the language, we'll be produtive from day one.
What you'll find anyways, is that we deploy hourly, not weekly. Even on Fridays, because we're confident in what we're shipping. We also always strive to slice a feature so we deliver value as soon as possible.
If the tools work for you, they'll work for us. If you need help deciding, we've got some ideas and we'll happily train you and your team so you can eventually continue without us.
Languages & Frameworks
This is just an excerpt of our collective work experience. We found our practices to be applicable in every language and every framework we worked with so far, and we're up to speed in a new language in no time
On the JVM, we've deployed small microservices in Clojure using Components, wrote our own event-sourced monolith in Scala and spent a fair share of our time putting Spring applications written in Java and Kotlin under test.
In the browser window, we've written testing libraries for redux, build customer projects in vanilla JS, gave workshops and taught clients React and KnockoutJS and delivered toolsets and libraries written in TypeScript.
On servers and on your machine, we've developed desktop apps in Qt/C++, webapps and backend services written in Ruby, Python and NodeJS, and tied everything together using Make, Bash, sed and awk ;)
Continuous Integration/Delivery
More importantly, we have extensive knowledge in putting the systems written in the languages above under test and know how to deliver them
We make sure our software works, by setting up CI systems on GitLab, Travis CI and GitHub. Our testing approaches are aligned with the testing pyramid, so expect plenty of unit tests, appropiate integration tests and extensive acceptance tests. There might be an occasional smoke test as well, as we don't want the canary birds to feel left out.
We delivered software, using kubernetes, ansible and bash. If there's a faster way to deliver it to you, we'll use that one. If the product doesn't need a backend, we'll deploy it to a CDN like netlify (like this page).
