subj
clock this
Nice, and of course for each time position there are numerous, infinite for sure equations, to describe it....
The mathematics of time.
1. Euler's formula and cos -1*(-1)=1
2. Exponent log_10(100)=2
3. Definite integral: x^2. 2^2-1^2=4-1=3
4. sin(pi/2)=1。(2)^2=4
5. 5^3 =125, square root of 5
6. Factorial 3! =3*2*1=6
7. Binary representation of 7 is 0111.
8. Continued product (2*0+2)*(2*1+2)=2*4=8
9. Square root of 9
10: Find the exponent to get 10
11: Hexadecimal representation of 11 is b
12: Summation ∑: (3*1-2)+(3*2-2)+(3*3-2)=1+4+7=12
The mathematics of time.
1. Euler's formula and cos -1*(-1)=1
2. Exponent log_10(100)=2
3. Definite integral: x^2. 2^2-1^2=4-1=3
4. sin(pi/2)=1。(2)^2=4
5. 5^3 =125, square root of 5
6. Factorial 3! =3*2*1=6
7. Binary representation of 7 is 0111.
8. Continued product (2*0+2)*(2*1+2)=2*4=8
9. Square root of 9
10: Find the exponent to get 10
11: Hexadecimal representation of 11 is b
12: Summation ∑: (3*1-2)+(3*2-2)+(3*3-2)=1+4+7=12
subj
m vs rn
sneaky scammers! careful out there
subj
The code is the documentation -- yep
At Meta, we didn't waste our time writing documentation about how our codebase worked for a simple reason: The code itself was documentation.
Actually readable, concise, and detailed commit messages were the first step.
On top of that, every pull request had a detailed body explaining the code's business context and approach, making blames super informative.
Every pull request had a test plan section. This is where we attached logs, screenshots, and video demos to make it dead obvious what our code did.
We also required a JavaDoc style header on every file, often linking deeper resources like system design docs there.
If an engineering organization needs to write a series of O' Reilly books to explain how their own code works, they have already failed miserably.
Documentation is something that should be naturally generated as part of the culture, not an explicit extra effort. Learn more about Meta's genius approach to documentation here: https://lnkd.in/ggcqr6pK
Actually readable, concise, and detailed commit messages were the first step.
On top of that, every pull request had a detailed body explaining the code's business context and approach, making blames super informative.
Every pull request had a test plan section. This is where we attached logs, screenshots, and video demos to make it dead obvious what our code did.
We also required a JavaDoc style header on every file, often linking deeper resources like system design docs there.
If an engineering organization needs to write a series of O' Reilly books to explain how their own code works, they have already failed miserably.
Documentation is something that should be naturally generated as part of the culture, not an explicit extra effort. Learn more about Meta's genius approach to documentation here: https://lnkd.in/ggcqr6pK
express, not stress