bitreich-manifesto

Name: bitreich-manifesto
Author: Fuwn

18stars2forks

How to install bitreich-manifesto?

fuwn/suckless-agent-skills/bitreich-manifesto

$npx -y skills add Fuwn/suckless-agent-skills --skill bitreich-manifesto

Installs into the current project.

Summary

Bitreich manifesto and principles for simple, reusable, maintainable software, command-line interfaces, patch-driven collaboration, and programmer-oriented tools.

Files · 1

View on GitHub

SKILL.md

1	# Bitreich Manifesto
2
3	## Introduction
4
5	We live surrounded by complex software which receives new versions and
6	updates day after day. RAM and CPU consumption never reduce, they in‐
7	crease. Software still provides the same features from years ago, but
8	everything looks new. This is called »advance« in the new speak of pro‐
9	prietary software development.
10
11	This has to change!
12
13	## Suckless
14
15	Suckless failed.
16
17	## Consumerism
18
19	Consumerism is the ability of persons to lose their skill in thinking on
20	their own, producing things, applying logical and practical ways of be‐
21	having. This disease of consumerism is striking the devices and comput‐
22	ers we humans produced to make them not scale in the possibilities they
23	could be used for. Computers can do things consumers cannot want and
24	imagine before they use the computer for something. The market economy
25	of demand and supply does simply not work here.
26
27	## UNIX Principles
28
29	In the beginning of the development of software principles were intro‐
30	duced how to create software which can be reused in ways the original
31	developers never imagined. Small utilities are combined using simple
32	pipes, speaking to eachother, just doing one task well.
33
34	## Dawn Of Ugliness
35
36	By not applying this methodology to its extreme, by trying to force new
37	features of computers into the UNIX principles, binary blobs evolved into
38	a complexity no young programmer can understand. They are forced into
39	the industry due to »life events«, where they are degrading to robots
40	which only apply what they learned at programming school (e.g. life,
41	university ...). This circle is producing even bigger binary blobs.
42	Nowadays this evolved into shipping whole operating systems in images
43	which you run separately.
44
45	This has to end!
46
47	## Bitreich
48
49	We form a movement to improve our daily software life. Software has to
50	not misbehave, it has to follow our rules, it has to be reusable, it has
51	to be easily maintainable, it has to provide its recompilable source and
52	it has to be easily understandable.
53
54	### Bitreich Principles
55
56	#### KISP – Keep It Simple Perfect
57
58	Software needs to do one thing well / perfect.
59
60	#### Commandline Interfaces
61
62	Always add a commandline interface to your software. Graphical User In‐
63	terfaces are for sissies. Pipes are welcome.
64
65	#### When Possible Use GPLv3
66
67	The signs of MIT‐appearance in the community is based on the circle of
68	complexity introduced into the minds of libre software programmers by
69	their oppressors transferring money to their bank accounts every month.
70	Your software is used in war machines to kill people and the companies
71	will never give back. So enforce GPLv3, it’s needed.
72
73	#### Users Are Programmers
74
75	Software should be written for programmers, which means the code is the
76	documentation, it should be easy readable, low abstraction levels should be
77	used (OOP sucks most of the times) and a simple Makefile to build everything
78	needs to be present.
79
80	#### Bugreports Are Patches
81
82	Bugtrackers are obsolete. Whenever you find a bug, fix it. The other
83	principles make it possible for you to send a patch instead of a report.
84
85	#### Applications Can Be Done
86
87	When a project solves a problem, keep it done and declare it so. New
88	problems are solved by different projects.
89
90	#### Freedom Of Language
91
92	The software world is spammed with new revolutionary programming lan‐
93	guages every month. Choose whatever you need to solve your problem, but
94	keep to the above mentioned principles. Most new programming languages
95	solve a non‐problem the principles of bitreich solve.
96
97	#### Inevitability Of Change
98
99	These principles can change, based on the consent of the bitreich elite

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

bitreich-manifesto

18stars2forks

View on GitHub

How to install bitreich-manifesto?

fuwn/suckless-agent-skills/bitreich-manifesto

$npx -y skills add Fuwn/suckless-agent-skills --skill bitreich-manifesto

Installs into the current project.

Summary

Bitreich manifesto and principles for simple, reusable, maintainable software, command-line interfaces, patch-driven collaboration, and programmer-oriented tools.

Files · 1

View on GitHub

SKILL.md

1	# Bitreich Manifesto
2
3	## Introduction
4
5	We live surrounded by complex software which receives new versions and
6	updates day after day. RAM and CPU consumption never reduce, they in‐
7	crease. Software still provides the same features from years ago, but
8	everything looks new. This is called »advance« in the new speak of pro‐
9	prietary software development.
10
11	This has to change!
12
13	## Suckless
14
15	Suckless failed.
16
17	## Consumerism
18
19	Consumerism is the ability of persons to lose their skill in thinking on
20	their own, producing things, applying logical and practical ways of be‐
21	having. This disease of consumerism is striking the devices and comput‐
22	ers we humans produced to make them not scale in the possibilities they
23	could be used for. Computers can do things consumers cannot want and
24	imagine before they use the computer for something. The market economy
25	of demand and supply does simply not work here.
26
27	## UNIX Principles
28
29	In the beginning of the development of software principles were intro‐
30	duced how to create software which can be reused in ways the original
31	developers never imagined. Small utilities are combined using simple
32	pipes, speaking to eachother, just doing one task well.
33
34	## Dawn Of Ugliness
35
36	By not applying this methodology to its extreme, by trying to force new
37	features of computers into the UNIX principles, binary blobs evolved into
38	a complexity no young programmer can understand. They are forced into
39	the industry due to »life events«, where they are degrading to robots
40	which only apply what they learned at programming school (e.g. life,
41	university ...). This circle is producing even bigger binary blobs.
42	Nowadays this evolved into shipping whole operating systems in images
43	which you run separately.
44
45	This has to end!
46
47	## Bitreich
48
49	We form a movement to improve our daily software life. Software has to
50	not misbehave, it has to follow our rules, it has to be reusable, it has
51	to be easily maintainable, it has to provide its recompilable source and
52	it has to be easily understandable.
53
54	### Bitreich Principles
55
56	#### KISP – Keep It Simple Perfect
57
58	Software needs to do one thing well / perfect.
59
60	#### Commandline Interfaces
61
62	Always add a commandline interface to your software. Graphical User In‐
63	terfaces are for sissies. Pipes are welcome.
64
65	#### When Possible Use GPLv3
66
67	The signs of MIT‐appearance in the community is based on the circle of
68	complexity introduced into the minds of libre software programmers by
69	their oppressors transferring money to their bank accounts every month.
70	Your software is used in war machines to kill people and the companies
71	will never give back. So enforce GPLv3, it’s needed.
72
73	#### Users Are Programmers
74
75	Software should be written for programmers, which means the code is the
76	documentation, it should be easy readable, low abstraction levels should be
77	used (OOP sucks most of the times) and a simple Makefile to build everything
78	needs to be present.
79
80	#### Bugreports Are Patches
81
82	Bugtrackers are obsolete. Whenever you find a bug, fix it. The other
83	principles make it possible for you to send a patch instead of a report.
84
85	#### Applications Can Be Done
86
87	When a project solves a problem, keep it done and declare it so. New
88	problems are solved by different projects.
89
90	#### Freedom Of Language
91
92	The software world is spammed with new revolutionary programming lan‐
93	guages every month. Choose whatever you need to solve your problem, but
94	keep to the above mentioned principles. Most new programming languages
95	solve a non‐problem the principles of bitreich solve.
96
97	#### Inevitability Of Change
98
99	These principles can change, based on the consent of the bitreich elite

People who liked this also viewed

6 picks

Type