Nikolas.ws

There are approaches to writing code that are structurally appropriate for the task, and make it easier push beyond the boundaries of what's possible.

Scrum's story points rapidly turn into a game of Numberwang.

Software development teams invented agile as an immune response to destroying the world and — adding insult to injury — being prevented from doing so efficiently by middle management.

Salvage capitalism is the ability for capitalist process to take advantage of non-capitalist systems and processes.

JSON-LD is a good tool for manipulating and presenting data, but how do we get at it's potential as an API layer?

A proposal for connecting content across communities without closed platforms.

In which we try and understand what JSON-LD is all about, what it's good for, and why it's interesting and cool.

A component for looking at a code alongside the result of that code.

An overview of RDF, what it is, how it works, and why.

Every year I make this, and every year I spend too much time trying to find the recipe online somewhere.

Implementing a secure JWT token authentication system for server-rendered applications.

Managing the lifecycle of development projects - as well as other open-ended creative endeavors — tends to be an act of wishful thinking more than "planning".

Ontological data structures, real-time editing, and what a web app _really_ is man.

An interactive component for computing time savings and efficiencies.

Finding an upper limit on factorials in JavaScript

What _is_ a Headless CMS, and how can it be useful for building websites and apps?

Thinking about what it means for an industry to determine a moral standard of practice.

Adapted from a talk given at the Portland Cartography symposium, a look at how media informs design.

Learning about JSON-LD is all about and why we should.

Translations and compromises in image making or; the Image Cult Society.

Moving beyond the idea that the designer and the developer on a web project are different people, and that somehow those are different things.

Writing a wrapper client library to smooth out design weirdness at the API level leads to plenty of design thinking on the way things should be.

Understanding maps as designed objects and attempting to define a theory for making digital maps on the internet as good as old paper maps.

They don't.