The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Deployed Xosphere to automate spot instance management across production workloads. Reduced EC2 spend by 60% with no availability impact.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
Saw this - been testing Seedance 2.5 too. Output is good but still needs human clean-up, esp label warp. I disclose it as AI-assisted. Human eye still matters.
Is AI finally good enough to shoot a product demo on its own, or human touch is still needed?
I generated a 20s product demo with Seedance 2.5 in a single take providing it with one product image reference and an example video transcript (posted in the comments).
Do you disclose...
This is good
A procedural shaded-relief cartographer's table; export the map as PNG.
I built this project to test A procedural shaded-relief cartographer's table; export the map as PNG. The core engineering challenge was sustaining uncompromised 60 FPS rendering using Canvas2D while handling continuous user interaction without framework overhead.
WHAT I WAS TESTING:
I focused on two core engineering benchmarks:
Real-time topographic contour line extraction using Marching Squares
Mountain ridge carving and hydrographic river basin generation
THE TECHNICAL SIDE:
Combines domain-warped fractional brownian motion (fBm) with Marching Squares contour generation. Renders vintage parchment styled topographic maps with seeded coordinates.
Everything executes in the browser using Canvas2D, Procedural Cartography, Contour Line Marching Squares. No third-party frameworks, no heavy runtime bundles, and zero external tracking.
WHAT I LEARNED:
Contour line marching squares often generated disconnected micro-segments. Stitching adjacent line segments into continuous polyline paths allowed smooth canvas stroke rendering.
Finding the sweet spot between mathematical precision and frame budget took careful profiling, but the result runs at a steady 60 FPS even on modest hardware.
TRY IT YOURSELF:
The live build is deployed on Netlify. Open it in your browser, test the controls, and observe the render response times.
If you are building high-performance 3D, physics, or creative web systems and want to collaborate, reach out here on Contra.
Really nice map detail
ColdFusion to LAMP for 15,000 users
ColdFusion ran the university's web applications for years, and it did its job. I respect that. But the world around it moved on. Hiring ColdFusion developers got harder every year, the ecosystem kept shrinking, and every new integration felt like swimming upstream. Moving to LAMP meant a larger talent pool, a massive open-source ecosystem, and tooling that let us ship faster with the people we had.
This was never about chasing something shiny. The old stack was quietly taxing every project, and the new one would let us serve students and staff better.
The ColdFusion apps were monolithic. Business logic tangled into CFML templates, a proprietary application server in the middle of everything. I rewrote the application logic in PHP/MySQL and tuned the stack for performance under load. The real shift was decoupling. I put REST APIs in front of the data so the same backend could serve the CMS, Salesforce, and PeopleSoft sync jobs. That API layer did not exist before. It was the single most important decision in the project.
With 15,000+ users depending on these systems, there was no big-bang cutover, especially not near enrollment season. We ran old and new in parallel, migrated module by module, validated data at each step. I built the sync layer first, tested it against production data in staging, then moved user-facing pieces over.
Honest version of what broke: data migration is where migrations go to die. Years of ColdFusion-era data had quirks. Inconsistent formats, fields used for purposes nobody remembered, edge cases buried in enrollment records. The sync jobs caught most of it, but the first stretch after cutover surfaced records needing manual reconciliation. Session handling behaved differently between the CFML server and PHP, which caused confusing login issues early on. We fixed those by tightening session configuration and adding logging we should have had from day one.
I also built the university's Drupal multisite architecture from scratch via terminal: full LAMP provisioning, virtual hosts, shared codebase. REST APIs and scheduled sync jobs across Cascade CMS, Salesforce, and PeopleSoft. Internal tools too: searchable staff directory, phone management, multi-step approval workflows. The stack changes. The approach doesn't.
