recentpopularlog in

WebDev

« earlier   
GitHub - cjss-group/CJSS: A CSS based web framework
A CSS based web framework. Contribute to cjss-group/CJSS development by creating an account on GitHub.
css  webapplication  webdev  framework  joke  funny  opensource  floss 
3 hours ago by gilberto5757
roma-glushko/tango at producthunt
A CLI to pull a certain amount of analytics info directly from your website's access logs.
cli  utility  apache  webdev 
5 hours ago by ttscoff
Zizzamia/perfume.js: Perfume is a tiny, web performance monitoring library which reports field data like Navigation Timing, Resource Timing, First Contentful Paint (FP/FCP), Largest Contentful Paint (LCP), First Input Delay (FID) back to your favorite ana
Perfume is a tiny, web performance monitoring library which reports field data like Navigation Timing, Resource Timing, First Contentful Paint (FP/FCP), Largest Contentful Paint (LCP), First Input Delay (FID) back to your favorite analytics tool. - Zizzamia/perfume.js
performance  webdev  javascript 
6 hours ago by amason
BlurHash
BlurHash is a compact representation of a placeholder for an image.
image  software  webdev 
11 hours ago by dexter
Production Oriented Development - Paul Osman - Medium
Engineers are the subject matter experts for the code they write and should be responsible for operating it in production. In this context, “operating” means deploying, instrumenting, and monitoring code as well as helping to resolve incidents related to or impacting that code. The responsibility of operating code aligns incentives — it encourages engineers to write code that is observable and easy to debug, and connects them to what customers care about. It encourages them to be curious about how their code is performing in production. Importantly, engineers should be on-call for their code — being on-call creates a positive feedback loop and makes it easier to know if their efforts in writing production-ready code are paying off. I’ve heard people complain about the prospect of being on-call, so I’ll just ask this: if you’re not on-call for your code, who is?
webdev  software  programming  product-management  HN 
15 hours ago by 1luke2
Production-Oriented Development | Hacker News
> Environments like staging or pre-prod are a fucking lie.
You need an environment that runs on production settings but isn't production. Setting up an environment that ideally has read-only access to production data has saved a huge number of bugs from reaching customers, at least IME.
There's just so many classes of bugs that are easily caught by some sort of pre-prod environment, including stupid things like "I marked this dependency as development-only but actually it's needed in production as well".
Development environments are frequently so incredibly far removed from production environments that some sort of intermediary between production is almost always so helpful to me that the extra work involved in maintaining that staging environment is well worth it.
webdev  programming  HN 
15 hours ago by 1luke2

Copy this bookmark:





to read