Articles by the team at CodeIQ.
Developers and the planning team write about takeovers, management and integrations. About what we come across in projects, without client names.

Takeover
What you have on paper after a two-week code audit
Every takeover starts with a two-week audit. Afterwards you know the risks and what it costs to continue.
Serge Huijsen3 minute read
Takeover
How the handover works when you switch suppliers
With a fixed order your platform keeps running while it moves from one supplier to the next.
Aaron Duran3 minute read
Way of working
Why you see something on a test environment every two weeks
Every two weeks new work is ready for you to click through and approve in My CodeIQ.
Anna Smink3 minute read
Integrations
An ERP integration that keeps working
An integration usually works on day one. This is how we make sure it still works after the next update.
Serge Huijsen3 minute read
Legacy
Rebuilding is almost never the answer
Everyone looking at someone else's code for the first time wants to throw it away. That is a feeling, not an analysis.
Aaron Duran3 minute read
Approach
The grand plan you wait a year for
A plan is a pile of assumptions in tidy sentences. Only once someone works with it do you learn which of them held up.
Serge Huijsen3 minute read
How we work
Why you do not get a project manager here
No layer in between that checks internally and comes back three days later. Whoever built it explains it.
Serge Huijsen2 minute read
Process
Excel is not the problem
That spreadsheet is usually the smartest solution someone had at the time. It only becomes a problem when five versions are going around.
Serge Huijsen2 minute read