Payment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.
Example result
Code review: Python order-import script for a small online shop
What the code does
- Reads
orders.csvfrom the shop export. - For each order line, finds the product by SKU in
stock.xlsxand subtracts the quantity. - Writes the updated stock back and logs totals to
import_log.txt.
The structure is clear and functions are well named. Most issues are about input that does not look the way the script expects.
Bugs and weak spots
| # | Line | Severity | Issue |
|---|---|---|---|
| 1 | 48 | High | The same CSV can be imported twice; there is no check for already processed order IDs. This is the most likely cause of negative stock. |
| 2 | 72 | High | int(row["qty"]) crashes on empty or "2.0" values from refunded orders. |
| 3 | 95 | Medium | SKU lookup is case-sensitive: "gt-101" and "GT-101" are treated as different products. |
| 4 | 130 | Medium | The file is opened without encoding="utf-8", so product names with accents break on Windows. |
| 5 | 201 | Low | Bare except: hides real errors and makes the log useless. |
Corrected fragments
Issue 1: skip orders already imported
processed = load_processed_ids("processed_orders.txt")
for row in reader:
if row["order_id"] in processed:
continue
# ... existing logic ...
processed.add(row["order_id"])
save_processed_ids("processed_orders.txt", processed)
Why: each order is applied once, even if you run the script on the same file again.
Issue 2: read quantity safely
raw = (row.get("qty") or "").strip()
try:
qty = int(float(raw))
except ValueError:
log.warning("Order %s: bad quantity %r, skipped", row["order_id"], raw)
continue
Why: refunded or partial lines are skipped with a clear note instead of stopping the whole import.
Issue 3: normalise SKUs
sku = row["sku"].strip().upper()
Apply the same .strip().upper() when building the stock dictionary.
Style and readability
process()is 90 lines long; split it intoread_orders,apply_to_stock,write_report.- Replace magic column numbers (
row[7]) with header names.
Please test each fix on a copy of your files: we read the code but did not run it.
Client: owner of a tea shop who wrote a 310-line Python script that imports orders from a CSV export into the stock spreadsheet Problem reported: "Sometimes stock goes negative, and the script crashes on some files."
The client and all details are made up.
About this service
Arduino sketches tend to fail for software reasons that look like hardware faults: delay() blocking button presses, String objects slowly filling the 2 KB of memory on an Uno, a variable shared with an interrupt but not marked volatile, or a button read without debouncing. We read your sketch, explain what loop() does on every pass, and mark the timing, memory and logic problems. Corrected fragments use millis() timing, the F() macro and clearer state handling.
What is included
- What you getA written review on the order page: what your sketch does on each pass of loop(), problems by importance and corrected code fragments for your board. Premium adds a plan for splitting the sketch into functions or a simple state machine.
- Non-blocking timingmillis() instead of delay()
- Memory useString, arrays and the F() macro
- Inputs and interruptsDebouncing and volatile variables
- Pin and library setuppinMode, pull-ups and library calls
- Fixed fragmentsReady to upload and test
How it works
- 1BriefYou paste the sketch and describe the wiring
- 2ReadingWe trace setup() and each loop()
- 3ReviewYou get problems and corrected code
What we need from you
The sketch pasted as text, the board, the sensors and modules with their libraries, a description or photo of the wiring and the Serial Monitor output.
We will ask you:
- Which board do you use?
- Which sensors, modules and libraries are connected?
- What should the project do, and what does it do instead?
- What does the Serial Monitor show?
Compare packages
| Packages | BasicSketch up to 100 lines$15 | StandardSketch up to 400 lines$35 | PremiumUp to 1,000 lines with a structure plan$69 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 3 days |
| Revisions | 1 | 2 | 3 |
| Lines of code | up to 100 | up to 400 | up to 1,000 |
| Corrected fragments | Yes | Yes | Yes |
| Sketch structure plan | No | No | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Do you test it on real hardware?
No, we read the code and your wiring description. Upload each fix and check it on your board yourself.
Can you check my wiring?
We point out pin conflicts and code that does not match the wiring you describe. This is not an electrical safety check, so verify voltages and mains wiring yourself.
Do you review ESP32 and Wi-Fi code?
Yes. Replace your Wi-Fi password and any keys with placeholders before pasting.