I'm Tohfa Akib, an independent engineer. I collect data from protected, JavaScript-heavy and stateful websites, automate browser workflows, and build the Python and Go backends behind them. Often the work starts where a quick script stopped working. You work with me directly.
| name | price | stock |
|---|---|---|
| Desk Lamp Pro | 1299.00 | in_stock |
Getting a first version working is rarely the hard part. These are the problems that decide whether a project actually delivers, with real work behind each one.
"The site blocks us, or serves a page that only looks right."
Bot detection such as Akamai or DataDome judges the whole session: browser behaviour, cookies, request order and timing. A failed check can still return 200. The work starts with diagnosing what the site actually sees, then choosing an approach that is reliable and appropriate for your use.
"It worked on the first pages, then returned nothing."
The page is assembled by JavaScript from undocumented requests, or the session quietly expired. Both can return status 200 with no data; the fix is understanding the application's real request flow.
"We have 3,000 rows but half are the same."
Paging is stateful: asking for page 2 quietly returns page 1. The collector has to carry state forward and prove each page is new.
"It crashes overnight and starts again from zero."
No checkpoints and no idempotent writes. Long jobs need to resume where they stopped without duplicating anything.
"The site limits us, so we need more IP addresses."
Sometimes that is true, and then the infrastructure must rotate without taking itself offline. Often the fix is pacing and a smarter crawl.
"The API timed out. Did the order go through?"
A lost response is not a failure. Blind retries double-book; the integration needs an explicit unknown state and reconciliation.
"There is a login with a one-time code."
Design the human step in: a person enters the code once, the session is reused, and the rest runs unattended.
Pick the closest one. No technical words needed. You'll see how I'd approach it, work I've done that's close, and a sensible next step.
I build extractors that handle pagination, logins you own, changing layouts and sites that block simple scripts. You get a clean file or feed, and the code that produced it.
I automate browser workflows and back-office tasks end to end, with a person kept in the loop wherever a decision matters.
I connect APIs and webhooks so data moves on its own, and design for the awkward cases: timeouts, duplicates and requests whose result is unknown.
Python and Go backends, REST APIs, background workers and small internal tools, built to keep running after handover.
Scheduled checks with history and alerts, plus the unglamorous part: making sure a failed page load is never reported as a real change.
I like the problems other people gave up on: unreliable infrastructure, unfamiliar protocols, systems that fail in ways nobody can reproduce.
Describe the situation in plain words. I will tell you whether software can help, what kind, roughly what it would take, and whether it is worth doing at all.
Each case explains the problem, what made it hard, the approach and what was delivered. Client names and data stay private.
About 3,300 member and sub-account records from a Cloudflare-protected directory, with a three-step access ladder and a resumable crawl.
LTE dongles on a Raspberry Pi behind HAProxy, with ordered recovery after each reboot and a scheduler that rotates one modem at a time.
Read the case studyEvery 2026 roofing, siding, and window permit from a county portal, with contractor details, delivered as a workbook plus a resumable script.
Read the case studyCourier integration architecture for online sellers: controlled retries, explicit handling of uncertain bookings, and deduplicated delivery updates.
Read the case studyA news aggregator app for the most popular Bangla newspapers, backed by Scrapy spiders and an authenticated Django REST API.
Read the case studyDrag the handle. A typical weekly data task, done by hand on the left and by a scheduled job on the right. Hours are illustrative.
Interactive demos built from real projects. Each one says whether it runs live in your browser or is a simulation.
Run a quick script and an engineered collector against the same awkward website, and see why "it ran without errors" is not "the data is complete".
OpenDrive the rotation logic of a real Raspberry Pi and LTE-modem proxy farm: traffic-driven rotation, the keep-one-online rule, and a modem that fails to come back.
OpenAlso in the Lab:Page to dataResilient job runnerCSV cleanerAutomation estimator
You never pay to find out whether something is possible. A paid proof of concept is only suggested when a source or system is genuinely uncertain.
In plain words. A few sentences is enough to start.
Within two working days: is it doable, what are the risks, what would it take.
A small paid sample on the real source when there's real uncertainty. Otherwise, straight to a quote.
Fixed scope with written acceptance checks, or hourly for open-ended work. Regular progress you can see.
You own the code, the data and a short runbook. Maintenance is available, never required.
Exact words from reviews of completed contracts.
Amazing job, amazing freelancer. Efficient and quick. Would highly recommend.
helpful, responsive, and overall great work
Fast and Quality work result
Practical write-ups with real code, taken from things I've built.
Websites display values for humans. The small normalisation layer I put between the parser and the output so clients can actually sort, filter and compare the data.
Nov 15, 2026Challenge pages, expired sessions, JavaScript shells and repeated pages all arrive as status 200. The checks I run on every response before trusting it, with an interactive response…
Nov 15, 2026Position, class or label: three ways of finding a field and three ways they break. Why a shape check is not enough, how a canary catches silent errors,…
Describe the problem in your own words, even if you are not sure what kind of solution you need. I reply within two working days with an honest assessment.