# Carlsson.tech Technical writing by Erik Carlsson on software engineering, data engineering, cloud platforms, Agile, project delivery and engineering leadership. ## Articles - [Off to New Adventures](https://carlsson.tech/read/off-to-new-adventures) After three years at Codeplay, through an Intel acquisition, shifting priorities, redundancies, workshops, coaching, and more than a few unexpected challenges, it was time for a new adventure. A look back at what I learned, the people who made it worthwhile, and why I decided to return to Technical Project Management. - [From Guidance to Independence: Measuring Agile Team Maturity](https://carlsson.tech/read/from-guidance-to-independence-measuring-agile-team-maturity) If you've ever worked on an Agile team, you've probably seen first-hand that not all teams operate at the same level of effectiveness, autonomy, or clarity. Some need hands-on guidance just to run a daily stand-up; others seem to run themselves like a well-oiled machine. But how can we assess where a team is on its journey—and more importantly, how do we tailor support to help them grow? - [From Guidance to Independence: Measuring Agile Team Maturity Part 2](https://carlsson.tech/read/from-guidance-to-independence-measuring-agile-team-maturity-part-2) In the previous post, we explored why measuring Agile maturity is essential and how it complements Bruce Tuckman’s model of team development. Now it’s time to look at the five maturity levels in detail. Each level represents a distinct phase in a team’s evolution—from heavily supported to fully self-organizing. Understanding these stages helps Agile coaches and managers provide the right support at the right time. - [From Guidance to Independence: Measuring Agile Team Maturity Part 3](https://carlsson.tech/read/from-guidance-to-independence-measuring-agile-team-maturity-part-3) In our first two posts, we explored why measuring Agile maturity matters and walked through the five maturity levels teams progress through—from Fully Supported to Self-Organized. But how do you actually measure where a team stands? - [From Guidance to Independence: Measuring Agile Team Maturity Part 4](https://carlsson.tech/read/from-guidance-to-independence-measuring-agile-team-maturity-part-4) In the previous post, we introduced a questionnaire-based tool to assess Agile maturity. Once you've collected the data, what comes next? How do you use those results to make better decisions as a coach, engineering manager, or leader? - [I did a thing - and now I have two bots](https://carlsson.tech/read/i-did-a-thing---and-now-i-have-two-bots) To ramp back up after ~5 years away from professional coding, I started building things in my spare time. This website was one of those projects. I also spent time on Docker, Spark, and generally getting back into a systems mindset. - [Team Agile Maturity Questionnaire](https://carlsson.tech/read/team-agile-maturity-questionnaire) A practical Agile maturity questionnaire designed to assess how independently a team operates. Includes scoring guidance and management considerations to help determine the right level of external support. - [How COVID changed the Standup](https://carlsson.tech/read/how-covid-changed-the-standup) Standups were never really about the format. Remote work didn’t break them - it made it clear why they exist in the first place. - [My Bot Detection Broke My SEO](https://carlsson.tech/read/my-bot-detection-broke-my-seo) A “simple” bot rule broke my indexing. Redirecting everything worked for social previews, but not for Google. I fixed it by reworking my bot handling, OG routing, SSR, and Nginx. - [Why “Small Changes” Don’t Exist in Software Engineering](https://carlsson.tech/read/why-small-changes-dont-exist-in-software-engineering) “It wasn’t the change that was big. It was everything connected to it.” - A tale of why the word “Googlebot” turned into 3 days of work. - [Things I learned working in IT](https://carlsson.tech/read/things-i-learned-working-in-it) Lessons from working in IT. No tools or frameworks, just the things that actually mattered for my growth and long term career progress. - [Why being a good engineer isn’t really about writing the best code](https://carlsson.tech/read/why-being-a-good-engineer-isnt-really-about-writing-the-best-code) A reflection on what senior engineers actually do: thinking in systems, balancing trade-offs, understanding domain, and taking ownership beyond code. - [The Day My Logging System Became My Security System](https://carlsson.tech/read/the-day-my-logging-system-became-my-security-system) I thought my website was down because I'd run out of disk space. I was right - but the reason why uncovered a brute-force attack, corrupted SQL Server metadata, and some uncomfortable security lessons. - [Why I Treat Good Recruiters With Respect](https://carlsson.tech/read/why-i-treat-good-recruiters-with-respect) Good recruiters deserve professional respect. Bad ones waste your time. The worst can cause real problems. This is how I deal with recruiters - and why effort should go both ways. - [The Redirect That Confused LinkedIn](https://carlsson.tech/read/the-redirect-that-confused-linkedin) My Open Graph tags were correct, but LinkedIn still showed the wrong domain. The cause was hiding in an Nginx redirect. - [A Shift In Perception](https://carlsson.tech/read/a-shift-in-perception) A reflection on how translating cybersecurity into familiar physical-security concepts - asset protection, access control, monitoring, cost, and proportionality - made the subject far less abstract. ## Projects - [carlsson.tech - Technical Description](https://carlsson.tech/project/carlssontech-technical-description) Built to regain my technical edge, this full-stack VPS project forced me to own everything—auth, security, data, and delivery. It’s not perfect, but it’s hardened through trial, error, and a refusal to let things break silently. ## Pages - [About](https://carlsson.tech/about) Background, certifications, what I enjoy working on, and what I use this webpage for. - [Contact](https://carlsson.tech/contact) How to reach me, and how to get in touch for work or collaboration. ## Legal - [Privacy Policy](https://carlsson.tech/privacy-policy) How I handle your data, and what information I collect when you visit this website. - [Terms of Use](https://carlsson.tech/terms-of-use) The terms and conditions for using this website, and the content on it.