Software engineering student, London
I'm studying for a BEng in Software Engineering at the University of Westminster. I also run the office side of a construction company, which is where most of my code comes from. There is always something there that gets done by hand and shouldn't be.
I write Python day to day. I like small tools that fix one specific problem and then get used every week. Longer term I want to work on backend systems.
Built for my own job at FAS Construction.
Attendance for each site arrives as WhatsApp messages. They mix English and Romanian, dates are written however the sender felt like that day, hours are sometimes typos, and the site name is often stuck to the date with no space. Someone used to retype all of it into Excel every week.
This script reads those messages and produces the payroll spreadsheet (date, site, worker, hours). The rule I set for it: parse what you're sure of, and put everything else in a review log with the original line next to it. It never crashes on bad input and it never quietly guesses a number.
Command-line tool for tracking a construction crew.
Keeps track of who's on the books, their hourly rate, hours per site, and
produces a pay report with overtime worked out. There's a Worker
class and a nested dict for hours per worker per site, and everything is
written back to CSV so it survives closing the program. Bad rows in the CSV get
skipped with a message rather than taking the whole thing down.
It started as practice with classes and nested data in Python and turned into something I actually used.
FAS Construction Limited, London
University of Westminster, London
Distinction, Merit, Merit
Email is the best way to reach me. I'm also on GitHub and LinkedIn.
LKS Software