Giving names to the assumptions and groups of assumptions used in decisions would also let us further document what they rest on.
-
-
Replying to @englishm_
We could start to form a shared vocabulary and collaboratively document shared chains of reasoning.
1 reply 0 retweets 1 like -
Replying to @englishm_
Things like RFCs or Python's PEPs cover some of this, but what if we factored out some of the "shortcuts"
@wycats describes?1 reply 0 retweets 0 likes -
Replying to @englishm_
@englishm_ my belief is that "kernels" are an encoding of these shortcuts, and each part of the kernel should explain why.1 reply 2 retweets 0 likes -
Replying to @englishm_
@englishm_ I mean a generalization of an operating system kernel.1 reply 0 retweets 0 likes -
Replying to @wycats
@englishm_ the kernel and userspace separation in particular.1 reply 0 retweets 0 likes -
Replying to @wycats
@englishm_ the basic idea is that you're encoding the stable assumptions in kernel APIs, and use semver rules as the "moving" policy2 replies 1 retweet 1 like -
Replying to @englishm_
@wycats particularly a layer or two up (languages and frameworks) it seems we could try to share some common vocabulary1 reply 0 retweets 0 likes
@englishm_ lemme know if you have any questions. also I agree re: shared vocab :)
-
-
Replying to @wycats
@englishm_ the first step is getting people to agree it matters :)0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.