1. Preface
1.1
Below is my detailed report to Stetrin B.V. on the work I performed during February 22-26, 2026, under our contract for their onlinecamerashop.nl e-commerce website.
1.2
This report details the exact time spent on each stage of the work.
This time was tracked using Upwork's official «Time Tracker» program.
1.3
When I work on an hourly contract, the «Time Tracker» always runs on my workstation and automatically creates a «work diary».
1.4
The «Time Tracker» takes screenshots of all 3 monitors of my workstation at a random moment within every 10-minute interval.
Upwork stores these screenshots for 2 weeks and makes them fully available to clients, allowing them to independently verify the state of my workstation monitors in 10-minute increments.
1.5
However, since clients are not specialists in my field, the essence of my monitor screenshots may be unclear to them.
That is exactly why, in this report, I provide a detailed description of the work I have performed in a way that is understandable to non-professionals.
2. The report
2.1. Day 1, 2026-02-22, Sunday
The 1st day of work.
Work continued for 8 hours.
I worked on 5 tasks:
2.1.1
For my work, it is crucial to access the client's server via the SSH protocol, so it was the 1st task I undertook.
However, ShopWizzy's firewall blocked the connection.
2.1.2
During the network analysis (when attempting to connect to the server via the SSH protocol), I obtained proof (whois -h whois.cymru.com 144.76.102.70) of my previously stated hypothesis that ShopWizzy simply subleases a Hetzner server to you with a markup of at least 5-6 times, and most likely even 10 times.
By this finding alone I have provided you with the opportunity to save approximately €400/mo (judging by your monthly bills from ShopWizzy, which are visible in the ShopWizzy hosting control panel, point 2.1.3 below).
2.1.3
Analysis of the information systems to which you provided access:
- ShopWizzy hosting control panel
- Low-level hosting control panels accessible via point 1:
2.1. Virtualmin
2.2. Usermin - Cloudflare
- Magento backend
- Trello
- Google Analytics
- Google Search Console
2.1.4
Organization and documentation of the knowledge I acquired during the previous stage (in particular, from the analysis of the 7 information systems to which I was granted access).
2.1.5.
The most time-consuming task that day: preparing my workstation for your project.
Rationale:
2.1.5.1
A high-quality programmer never performs a significant part of their work directly on the client's server.
Instead, they perform it on their local workstation.
To do this, they configure their workstation to run the exact same software as the client's server.
Since each Magento project runs in its specific software envronment, it needs a custom software configuration on the workstation.
Every detail matters: in particular, the exact versions of the software used on the client's server, as different versions can behave differently.
2.1.5.2
Running the client's software locally on a local workstation allows the programmer to analyze and diagnose the software's behavior more thoroughly and professionally, as well as to modify it faster and more safely, without affecting the client's production server until the successful completion of programming and testing.
2.1.5.3
At that time, because of ShopWizzy's firewall (point 2.1.1 above), I did not yet have access to the source code of your website.
However, using the access provided to the aforementioned information systems (Virtualmin, Usermin, Magento backend), I already knew exactly what software and specific versions were running on your server.
Therefore, I replicated this exact software environment on my workstation.
As a substitute for the source code of your website, I temporarily used a blank instance of your Magento version (2.4.8-p2).
2.2. Day 2, 2026-02-23, Monday
2.2.1
That day, I logged only 20 minutes of my billable time using Upwork's «Time Tracker».
The rest of my working time that day, I provided consulting services to you for free.
2.2.2
The main problem I continued to address that day was obtaining access to your server via the SSH protocol.
2.2.3
You proposed an unworkable solution to this problem — using a ready-made VPN service: Surfshark.
I investigated this and discovered that in the country where I currently reside (Turkey), Surfshark and other similar services are blocked by the state.
2.2.4
Therefore, I proposed the only viable option in this situation: to configure a VPN server on my own Hetzner server and connect to your server indirectly, thus providing a static IP address to ShopWizzy's firewall.
You accepted my solution.
2.3. Day 3, 2026-02-24, Tuesday
2.3.1
That day, I logged only 2 hours of my billable time using Upwork's «Time Tracker».
The primary task I performed was configuring my VPN server (point 2.2.4 above).
2.3.2
2 years ago, in 2024, I solved a similar problem for another client and documented the solution in a fundamental 27-step guide, as well as a dozen auxiliary instructions.
Back then, delivering a high-quality solution to this problem and thoroughly documenting it took me 15 working hours.
2.3.3
However, precisely because I comprehensively solved this problem back then and just as thoroughly documented the solution, solving a similar problem again now, 2 years later, took me less than 2 hours, which is 7.5 times faster.
This is a clear example of why it is important to solve problems properly and organize information thoroughly.
2.3.4
This is the approach I consistently follow in all my work.
This is why the initial analysis and organization of knowledge require a significant investment of my time, but they ultimately yield substantial time savings for me later on.
2.3.5
So, that day I finally resolved the problem with ShopWizzy's firewall and gained access to the source code of your website.
2.4. Day 4, 2026-02-25, Wednesday
2.4.1
The previous day I finally resolved the problem with ShopWizzy's firewall and gained access to the source code of your website, so I resumed the replication of your server environment on my workstation: the task whose rationale and significance I thoroughly explained in point 2.1.5 above.
2.4.2
That day, I logged only 2 hours 40 minutes of my billable time using Upwork's «Time Tracker».
I described the reason for this in my deep and insightful letter the day before:
«A significant part of my thinking happens away from my workstation».
2.4.3
Upon the initial analysis of your website's source code, I encountered many complex architectural aspects that required careful consideration.
Instead of rushing to write code, at such moments I prefer to step away from the computer and engage in deep analytical thinking.
2.4.4
As I wrote in the aforementioned letter, I am currently not compensated for this analytical work away from my workstation, although it is no less important than the actual programming, and in strategic phases as the initial analysis of the source code, it is significantly more important.
2.5. Day 5, 2026-02-26, Thursday
2.5.1
The previous day, I intentionally minimized my time at the computer, dedicated significant time to analytical thinking away from my workstation, and went to sleep early to start working on the source code with a clear mind.
2.5.2
That day, I finished replicating your server environment on my workstation.
This allowed me to develop and analyze your online store using this identical local copy rather than directly on your live website.
2.5.3
Then I analyzed the differences between the source code of your website and the reference version of Magento 2.4.8-p2.
This was critically important work.
ShopWizzy (and most likely its subcontractors as well) made numerous modifications directly to the Magento core source code (rather than to separate modules).
It was absolutely necessary to analyze all these modifications in detail because they affect Magento's behavior.
2.5.4
Additionally, ShopWizzy (and most likely its subcontractors as well) left numerous non-functional junk files containing previous versions of the source code.
Leaving junk behind in the source code is a very bad practice.
Such files hinder the analysis, maintenance, and modification of the source code because it becomes unclear whether Magento uses a specific piece of code.
2.5.5
I always remove such junk from the website.
For 6 years, I have been developing a fundamental script for it.
However, in each specific project this script needs to be used very carefully.
Its application requires serious analytical work and an understanding of how Magento works.
It cannot be run thoughtlessly.
2.5.6
In total, the tasks of points 2.5.2, 2.5.3, and 2.5.5 took 5 hours and 20 minutes of my working time.