Technical documentation

5 posts
Be boring

Be boring

In discussions with non-tech managers, buzzwords often mask understanding. My view: use tech pragmatically, focusing on proven tools. Innovation matters, but clarity and long-term stability are key. Managers should demystify tech jargon and ensure meaningful application.

A framework to deal with technical debt

Are there any specific product management framseworks to deal with technical debt?

A field guide to modernizing your PHP project — how to avoid a rewrite through incremental development

A field guide to modernizing your PHP project — how to avoid a rewrite through incremental development

Sometimes the code really is unmaintainable and non-upgradeable. Other times, it might just be old and written in a technology that’s dated or deprecated. Learning how to work with legacy code is a skill in itself. Here’s our playbook for modernizing that old PHP project.

Why you should code your infrastructure

Why you should code your infrastructure

Have trouble documenting your infrastructure? Infrastructure as code might be the solution you are looking for.

We are not a remote-first company

We are not a remote-first company

Although we have employees in 7 countries — not bad for 20 people! — madewithlove is not a remote-first company. Yes, we work remotely, but there are 6 traits that allow us to be a successful remote company. We are a knowledge-first company. What is a knowledge-first company? A knowledge-first company is...

You’ve successfully subscribed to madewithlove
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.