An information communication technology company dedicated to developing innovative IT solutions.
Part 4 — What I would tell myself before starting Suspect the step before the one that failed. Nearly every error here appeared downstream of its cause. Read the status code, not just the body. A time
Part 2 — Three decisions to make before deploying Don't share an existing database server The server already had a PostgreSQL container, and reusing it was tempting. Don't, if your application depends
I recently took an API from "works perfectly on my laptop" to "live on its own domain over HTTPS". On the laptop it was in good shape: hundreds of automated tests passing, static analysis clean, and a
One spreadsheet for sales.Another for expenses.A separate file for payroll.Invoices sitting in email.Customer information somewhere else.Projects being tracked through messages.And somehow, you are ex
It probably started with one spreadsheet.One for student records.Then another for fees.Another for attendance.Before long, there are spreadsheets for examinations, staff, inventory, reports and countl
In Part 1, we prepared for the migration and created backups.In Part 2, we moved the website files and database to the new server and connected the website to its new database.Now we are at the final