A few things I’ve worked on

I built client sites at an agency. At Popupsmart, I worked on embeds that run on other sites, analytics and integrations.

Popupsmart · Embedded web

Embeds that run on other websites

Preact · TypeScript · Vite · Cloudflare

Our script had to run on other people's pages. Their CSS, other scripts and loading order could affect it, so a working component on our test page wasn't enough.

What I worked on

At Popupsmart I worked on the Vite and Preact runtime, the Next.js dashboard and the connection between them. I also worked on caching and Cloudflare delivery to use the origin more efficiently.

What I'd keep in mind

I'd write down the runtime's boundaries earlier: what it can change on the page, what it owns and what needs cleaning up when it closes. That gives the next feature a clearer starting point.

Popupsmart · Product development

The dashboard behind the popups

Next.js · React · Redux · GraphQL · Jest · Cypress

The popup script was one part of the product. Customers also used a dashboard to design and publish their popups.

What I worked on

I worked on this dashboard with Next.js, React and Redux, connected the interfaces to GraphQL, and used Jest for unit tests and Cypress for end-to-end flows. I also took part in the move from the .NET backend to GraphQL.

What I'd keep in mind

The backend migration let frontend developers contribute to the backend too. I started working across both sides, including the bugs that came with the transition.

Popupsmart · Analytics

Moving analytics to ClickHouse

ClickHouse · Node.js · AWS SQS

We were using OpenSearch for analytics. Query performance and the work of running it pushed us to look at ClickHouse for that workload.

What I worked on

I was involved in the ClickHouse schema, event ingestion, migration checks and changes to the queries the application used. We did the migration as a team.

What I'd keep in mind

I'd allow more time for running both read paths and comparing them. When two numbers differ, finding out why can take longer than rewriting the query.

n8n · API integrations

Connecting library APIs to a chatbot

n8n · REST APIs · Node.js

Each library had its own API, authentication and response format. We needed to get useful results into the chatbot without rebuilding the whole integration every time.

What I worked on

I built the n8n workflows for authentication, library queries and passing results to the chatbot. I also worked on a repeatable starting point for the next integration.

What I'd keep in mind

n8n helped with the orchestration. For logic that's hard to read across several nodes, I'd use a small piece of code and test it separately.

Popupsmart · Growth & marketing

Working with the growth team

Technical SEO · Webflow · Cloudflare · Docker · n8n

The growth team had websites to maintain as well as marketing work. I joined the team for work on the sites and their infrastructure.

What I worked on

I worked on technical SEO and the Webflow migration. I also set up Docker hosting for multiple marketing sites and worked on outreach automation with AI tools and n8n.

What I'd keep in mind

For performance work, I'd check the bundle, cache and delivery setup together. Editing a page is only part of getting it to load well.

Fikirhouse · 2019–2021

Nearly 50 client websites

WordPress · PHP · Laravel

At Fikirhouse I built nearly 50 websites for clients across different industries. I worked on them from the initial brief through launch.

What I worked on

I designed and coded WordPress themes and built custom sites with PHP and Laravel. One project was for an organized industrial zone, where I integrated an online card payment gateway.

What I'd keep in mind

My work continued after the site was built. I also created graphics, chose which content went on the site for each campaign, and worked on retargeting.