ARGON
Check-in [536f2beab9]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:"Phiosphy" type (thanks to Oskar Schirmer for spotting it!)
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:536f2beab954cfcbbce4d58ee5669ccfc2081037
User & Date: alaric 2015-07-08 08:51:32
Context
2017-03-16
18:19
Laid down the framework for "ARGON devops": ARGON code lives in CARBON stuff published by entities, so I laid out a framework for a "document entity" that publishes something with distributed workflow, ticketing, change control, etc. check-in: 4423936034 user: alaric tags: trunk
2015-07-08
08:51
"Phiosphy" type (thanks to Oskar Schirmer for spotting it!) check-in: 536f2beab9 user: alaric tags: trunk
2013-07-16
20:47
XENON added check-in: dd84df30e7 user: alaric tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to README.wiki.

19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
field of computing as best I can, learning the pros and cons of
existing systems, studying even the most exotic theoretical solutions
to a problem. Then I have tried my best to find the best combination
of technologies to solve the problem at hand: To build a platform upon
which the highest possible quality of software can be constructed with
the least effort.

<h1>Philosphy</h1>

I'm reinventing the wheel.

As a software engineer, in my day to day work, I of course don't do
this; the easiest solution to a problem is always to reuse as much
existing technology as possible. However, the long-term result of this
is that modern software is bloated, buggy, inflexible, and hard to







|







19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
field of computing as best I can, learning the pros and cons of
existing systems, studying even the most exotic theoretical solutions
to a problem. Then I have tried my best to find the best combination
of technologies to solve the problem at hand: To build a platform upon
which the highest possible quality of software can be constructed with
the least effort.

<h1>Philosophy</h1>

I'm reinventing the wheel.

As a software engineer, in my day to day work, I of course don't do
this; the easiest solution to a problem is always to reuse as much
existing technology as possible. However, the long-term result of this
is that modern software is bloated, buggy, inflexible, and hard to