Perspectives
Explore articles and insights about Science & Technology.
Latest articles
Software, literature, philosophy and science — notes from the team and the ideas that shape our work.
From Complexity to Competitive Advantage: The Multi-Cloud Management Strategy of Atomic Server Pilot In today's digital landscape, choosing a cloud provider...
We are thrilled to announce Arena — our new all-in-one management platform for sports academies and clubs. Manage athletes, coaches, trainings, attendance, payments, and evaluations from a single, beautiful dashboard.
WIRED Greece published an extensive article on the Greek state's PosoKanei platform, featuring our own experience with "Noikokyris" — the price comparison platform we developed at ATOMIC.
PHP is moving faster than ever. If you are still writing code like it's 2020, you are missing out on features that drastically reduce boilerplate and improve performance.
Searching is a core feature of almost every app. The first instinct is often to use the LIKE operator with wildcards.
You have a query that takes 3 seconds to run. Why? Guessing doesn't work. MySQL tells you exactly what it is doing if you ask it.
When syncing data from an external API (like updating product prices or user details), developers often write logic like this:
How often do you need to find just the first matching item in an array? Historically, developers used array_filter (which loops through everything) and then grabbed the reset() or current() item. It was messy and inefficient.
One of the most common requirements in Object-Oriented Programming is: "I want everyone to be able to read this status, but only the class itself should be able to change it."
For over a decade, PHP developers have written the same boring code: a private property, a getX() method, and a setX() method. It clutters your classes and makes them hard to read.
Let's talk
Join our community of thinkers, developers, and lifelong learners. Explore ideas that challenge and inspire you to think differently.
