Courses & workshops
Courses in web development and tracking
For development teams, where training makes most sense inside the code you actually work in. I spend a couple of hours reading the repository beforehand.
- Same-day reply
- Fixed price
- No lock-in
- In your own codebase
- Next.js and the App Router
- Performance and accessibility
- Tag Manager for developers
Service
Courses in web development and tracking
The topics I get asked for most
- The App Router in practice: server components, caching, and the places where the mental model and reality diverge.
- Performance: how to find out what is actually expensive instead of optimising what is easy to measure.
- Accessibility for developers — keyboard navigation, focus management and the five things that solve half the problems.
- Data layers and Google Tag Manager from the developer's side, so marketing can get what they need without asking for a deploy every time.
The format
Half days work best for developers. A full day away from the work is hard to get approved, and the return drops after lunch anyway.
I prefer to finish by making a real change together in your codebase. Then there is something concrete to hold on to afterwards.
Deliverables
What you get
Concrete deliverables, not a report of recommendations someone else has to find time for.
- In your own codebase
I read the repository beforehand, so the examples are yours and not an empty project.
- A real change together
We finish by making something that stays. Then there is something concrete to hold on to afterwards.
- Notes and references
What we covered, with links to what is worth reading next. Not a slide deck.
- A data layer agreed
If tracking is included: an agreement between development and marketing on which events exist and what they are called.
Process
How it works
Four steps. You know what happens when, and you can stop after any of them.
- 01
Your tasks up front
I ask for two or three concrete tasks people spend time on every week, then build the day around those instead of using my own examples from someone else's industry.
- 02
Morning: the technical part
Short and concrete. Not a talk about what the technology is, everyone has heard that, but how to actually get something usable out of it.
- 03
Afternoon: hands on
People work on their own tasks while I move around the room. That is where it sticks. I have never seen anyone change habits from watching a screen all day.
- 04
Material you keep
A follow-up document with what we built, including what ended up working. New colleagues can catch up later without sitting through the same walkthrough again.
Who does the work
I am the person you will be working with
My name is Mikkel and I have been building for the web since 2010. There is no project manager in between, and you will not get a junior on the job because the senior was busy. What you agree is what gets built, and I am the one building it.
Day to day I am a partner at Bigum&Co, and I have worked on more than 400 projects across ecommerce, pharma, construction and the public sector. Call or write — I usually reply the same day, and I will say straight away if the job is not a fit.
- Experience
- 16 yrs
- Projects
- 400+
- Rating
- 5.0
- Reply time
- Same day
In depth
Courses in web development and tracking
What developer courses usually miss
A course in a framework is rarely what a team is missing. The documentation is usually good and people can read. What they lack is knowing why their own codebase behaves as it does, and which of the choices made two years ago still make sense.
So I read the repository beforehand. Not to criticise it, but to use it as material. When we talk about server components and caching, we talk about the place in your code where it is actually a decision, not about an example from the docs.
That also makes the day shorter and more useful. There is no point covering things the team already does right, and every reason to spend time on the one place everyone has been unsure about for six months.
Half days work best. A full day away from the work is hard to get approved, and the return drops after lunch anyway. Three half days a couple of weeks apart gives people time to use it, and then we can pick up whatever caused trouble.
Tracking from the developer's side
This is the most requested half day, and it is rarely because the developers find tracking interesting. It is because marketing keeps asking for things that need a deploy, and nobody wants that conversation every other week.
The answer is a data layer. Development commits to a set of events with fixed names and fixed fields — page view, form, cart, purchase, search, filter. Marketing can then work freely on top of it in the tag manager without asking for anything new.
That takes a conversation between the two teams that in many places has never happened. So I usually suggest someone from marketing sits in on that half day. It is not a technical problem, it is an agreement problem, and it gets solved fastest with both sides in the room.
Reviews
What people say about me
I have never come across a developer as dedicated and capable as Mikkel.
Jonas Krogslund(translated from Danish) Mikkel is seriously good, helpful, lightning fast to reply — and on top of that he is a nice person.
Trine Handskemager(translated from Danish) Mikkel delivered competent, professional work setting up my website. Everything ran quickly and without a hitch.
Sisse Find(translated from Danish)
Services
Why me
- 16 years of experience
I have built for the web since 2010 and seen most of the ways a project can come off the rails. It makes the estimates more honest.
- 400+ projects
Across ecommerce, pharma, construction and the public sector. Chances are I have seen something close to your job before.
- You talk to the person coding
No project manager in between, and no junior on the job because the senior was busy. What you agree is what gets built.
Brands I have worked with
A selection. Some freelance, some through agencies, some across several years.
Questions
Frequently asked questions
- Can you run it over several sessions?
- Yes, and it often works better. Three half days a couple of weeks apart gives people time to use it, and then we can pick up whatever caused trouble.
- Do you teach in English?
- Yes. If there is one person in the room who does not speak Danish, we run it in English. That usually works fine.
- Which topics can you cover?
- Next.js and the App Router, performance and Core Web Vitals, accessibility for developers, and data layers and Google Tag Manager. If it is something else, ask — if I am not good enough at it, I will say so.
- Do you teach in English?
- Yes. If there is one person in the room who does not speak Danish, we run it in English. That usually works fine.
- Can you run it over several sessions?
- Yes, and it often works better than one long day. Three half days a couple of weeks apart gives people time to use it in between.