How do you validate need for documentation?
I once was on a project where a non-tech manager had the team spending half of every hour documenting what they just did so that someone with zero understanding of the tech would be able to understand the tech. Personally, I thought this was a huge waste, but there was no way to validate this was or was not waste.
How do you validate need for documentation?
I once was on a project where a non-tech manager had the team spending half of every hour documenting what they just did so that someone with zero understanding of the tech would be able to understand the tech. Personally, I thought this was a huge waste, but there was no way to validate this was or was not waste.
How do you validate need for documentation?
I once was on a project where a non-tech manager had the team spending half of every hour documenting what they just did so that someone with zero understanding of the tech would be able to understand the tech. Personally, I thought this was a huge waste, but there was no way to validate this was or was not waste.
How to include special characters like ≅ into “UnexpandM Syntax” syntax quotations?
If I define a macro which rewrites a ≅ b
into Congruent a b
(where Congruent
takes two terms of a given type), executing the #check
command will always produce the output of the macro (i.e., Congruent a b
).
Porting Prop Logic proves from lean3 to lean4
How we could port this code to lean4 and where I could find the documentation about on lean3 to lean4 porting?
Creating a macro/elab which converts a new identifier into two existing identifiers
I am quite new to metaprogramming in Lean and have been experimenting with using macros on undefined identifiers to convert it into other types. However, I have been stuck with converting a two character identifier (e.g. ab
) which may not have defined type into two identifiers of a specified form (in this case a
and b
).
Lean 4 proof assistant on the web? (nothing to install)
Is there a good website that provides a Lean 4 proof assistant service?
confusion over meaning of underscore `_` in simple Lean example
I am learning to use the Lean 4 proof assistant. I have a simple question about what the underscore symbol _ does in the following context:
Selecting the (right?) application design [closed]
Closed 10 years ago.
Selecting the (right?) application design [closed]
Closed 10 years ago.