Insights Hub
These insights distill years of building, managing, and growing. They bridge the gap between the strict discipline of C-level operations and the creative freedom of a digital alchemist. From leading teams of 860+ people to crafting unconventional strategies and hand-coding WebGL shaders, these articles document the reality of the work.
No abstract theories. Just the mechanics of what works, the analysis of what doesn’t, and the strategies that drive growth.
Cloudways has a powerful built-in feature where Varnish cache doesn't just store one single version of your page. Instead, it can store three separate versions: one for mobile, one for tablet, and one for desktop.
In this article, we will explore a straightforward but highly effective workflow for fracturing a 3D model into pieces and animating its destruction or assembly.
The idea is simple: instead of simulating physics in the browser, we let Blender do all the heavy work. We shatter the model with the Cell Fracture add-on, run a Rigid Body simulation, bake that simulation into plain keyframes, and export everything as a single glTF file. The browser then only has to play back an animation clip - no solver, no collision detection, no frame-rate-dependent surprises. Because the result is baked, you can also scrub it: tie the timeline to scroll position, a mouse hover, or a click, and play it forwards for a destruction and backwards for an assembly.
When building a Three.js scene, we often get carried away. We add new meshes, make the geometry more complex, and import heavy models from Blender.
At some point, even without any obvious complex logic or heavy generative calculations, we hit a wall. The FPS drops, CPU ms spikes, and the scene starts to lag.
This problem pops up a lot when we add geometry in a loop, like generating map tiles. It also happens when we import large, unoptimized scenes from a 3D editor where every single screw is a separate object.
Regulate what? Regulate why? Regulate how? Folks aggressively pushing for AI regulation seriously think that it is a good idea to grant power to control the industry to some guys in expensive suits who will dig their claws into a trillion-dollar market under the noble banner of public oversight for the sake of humanity.
Before we get to techniques, here’s the constraint everything else follows from: at 60 FPS the browser has about 16.7 ms to produce a frame. On a 120 Hz display – most recent flagship phones, iPads with ProMotion, plenty of laptops and monitors – the budget drops to roughly 8.3 ms. And you don’t get all of it. The browser needs part of that window for its own bookkeeping, so treat something like 8-10 ms at 60 Hz as your realistic ceiling for style, layout, paint, and your own JavaScript combined.
WordPress is okay. It was disturbed by AI in 2024, but now it is okay. People realized the real capabilities and limitations of AI website building and got back to WordPress. That's not my biased opinion, that's based on statistics of 35.8 million websites. Statistics has no bias, it tells truth.
Whenever I see politicians seriously sitting around with straight faces discussing plans to roll out AI across national infrastructure, it instantly reminds me of this fairy tale from centuries ago. Honestly, it's the exact same parallel. There really is nothing new under the sun.
Vibecoders! Before you rush to code another unique and groundbreaking personal AI assistant, voice note app or habit tracker, just look at the data. The total number of apps in the App Store remains flat, while the number of new app submissions is experiencing a massive spike.