Skip to content

📌 Interesting tech-related manifestos

License

Notifications You must be signed in to change notification settings

imsky/awesome-manifestos

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 

Repository files navigation

📌 Awesome Manifestos

Awesome Tweet

A collection of awesome manifestos.

Ten Principles for Good Design by Dieter Rams

Good design is as little design as possible

Choose Boring Technology by Dan McKinley

We should generally pick the smallest set of tech that covers our problem domain, and lets us get the job done.

This Page is Designed to Last by Jeff Huang

How do we make web content that can last and be maintained for at least 10 years?

Calm Technology by Amber Case

How many are notifications are necessary? How and when should they be displayed?

Keep a Changelog by Olivier Lacan

Changelogs are for humans, not machines.

The Twelve-Factor App by Adam Wiggins

This document synthesizes all of our experience and observations on a wide variety of software-as-a-service apps in the wild.

The Rails Doctrine by David Heinemeier Hansson

The chief accomplishment of Rails was to unite and cultivate a strong tribe around a wide set of heretical thoughts about the nature of programming and programmers.

HTML First by Tony Ennis

The main goal of HTML First is to substantially widen the pool of people who can work on web software codebases.

The NoJS Club by Karan Goel

Not all websites need Javascript to be beautiful and usable.

NoYAML by Geoffrey Huntley

Anyone who uses YAML long enough will eventually get burned

Immutable Web Apps by Gene Connolly

Immutable Web Applications are generated once and published once to a permanent location.

Local-first software by Kleppmann, Wiggins, van Hardenberg, and McGranaghan

Cloud services defy long-term preservation. No Wayback Machine can restore a sunsetted web application.

Frameworkless movement by Francesco Strazzullo

Every time a team uses a framework, it also takes a risk.

Always Own Your Platform by Sean Blanda

Stop giving away your work to people who don't care about it. Host it yourself. Distribute it via methods you control. Build your audience deliberately and on your own terms.

Publish on your Own Site, Syndicate Elsewhere (POSSE) by IndieWeb

POSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, the practice of posting content on your own site first, then publishing copies or sharing links to third parties (like social media silos) with original post links to provide viewers a path to directly interacting with your content.

Functional Web App by LeRoux and Block

Functional Web App (FWA)...empowers developers with the flexibility of dynamic, full-stack applications paired with the ease of scaling a static website.

Against software development by Michael Arntzenius

These days, for better or worse, software defines everyone's reality. Let's build one worth living in.

Trunk Based Development by Paul Hammant

Trunk-Based Development is a key enabler of Continuous Integration and by extension Continuous Delivery.

The stacking workflow by Greg Foster

Stacking parallelizes your development and code review workstreams, so you don't need to wait for your previous changes to be merged before building on top of them.

Conventional Commits by Damiano Petrungaro and Ben Coe

The Conventional Commits specification is a lightweight convention on top of commit messages.

System Font Stack by Tom MacWright

Webfonts were great when most computers only had a handful of good fonts pre-installed.

Semantic Versioning by Tom Preston-Werner

Under this scheme, version numbers and the way they change convey meaning about the underlying code and what has been modified from one version to the next.

Calendar Versioning by Mahmoud Hashemi

CalVer is a versioning convention based on your project's release calendar, instead of arbitrary numbers.

The Remote Manifesto by Darren Murph

We believe that a world with more all-remote companies will be a more prosperous one, with opportunity more equally distributed.

Principles of Chaos Engineering by Lorin Hochstein

Even when all of the individual services in a distributed system are functioning properly, the interactions between those services can cause unpredictable outcomes.

The Reactive Manifesto by Bonér, Farley, Kuhn, and Thompson

Systems built as Reactive Systems are more flexible, loosely-coupled and scalable.

The Software Defined Delivery Manifesto by Christian Dupuis

Delivery infrastructure is now programmable, and we will program it.

Stop breaking the Web by Derek Schaab

Rather than chasing after the latest features available only to those living on the bleeding edge of browser support, we should invest in making our creations open to all, consumable by all, and welcoming to all.

Contributing

Contributions are always welcome, feel free to open a PR!

License

awesome-manifestos is licensed under the MIT license.

About

📌 Interesting tech-related manifestos

Topics

Resources

License

Stars

Watchers

Forks