Working with CSS is tricky enough as it is; working with legacy CSS can be nightmarish. In this talk, we’ll look at how we decide what to refactor and when; how we can refactor code whilst still shipping features; how to avoid regressions when adding new CSS; how
Author Archives: Bramus!
Δ now: realtime global deployments
Δnow allows you to take your JavaScript (Node.js) or Docker powered websites, applications and services to the cloud with ease, speed and reliability. Every time you deploy a project, Δnow gives you a unique URL to it (even before build processes are complete!). When it’s time to take your deployment to production, you simply pick …
L’esprit de l’escalier
Now this sounds familiar: “L’esprit de l’escalier” is a French term used in English for the predicament of thinking of the perfect reply too late. According to Wikipedia: During a dinner at the home of statesman Jacques Necker, a remark was made to Denis Diderot which left him speechless at the time, because, he explains, …
Exponent – Write Android & iOS apps in JS
The bold beauty of content prototypes
Thomas Byttebier, after having joined a digital team at Base a while ago: It’s been a crazy six months. And in all honesty: I struggled. I struggled with process. I struggled with communication. I struggled with clients. Front end was too far from design and content only arrived when a project was nearly live. As …
Simon Sinek on Millennials (in the Workplace)
Meet Super Mario Run
Effective Writing For Your UI: Things to Avoid
Laphs: Apple Live Photos on the Web
From the folks over at Tumblr: Add support for Apple’s Live Photos in web browsers. Install it using npm, or include the dist file: npm install –save laphs You can make Laphs work with existing elements: <img src="STILL-PHOTO.jpg" data-live-photo="LIVE-PHOTO.mov" data-live-photo-still-image-time="1.71"/> <script>LivePhotos.initialize();</script> Or, alternatively, directly create new instances: const livePhoto = new LivePhotos.LivePhoto(el, options); Laphs: Live …
Hype Driven Development
Software development teams often make decisions about software architecture or technological stack based on inaccurate opinions, social media, and in general on what is considered to be “hot”, rather than solid research and any serious consideration of expected impact on their projects. I call this trend Hype Driven Development, perceive it harmful and advocate for …