Jake Roberts
@jakerob.pro
Expat living in London🇬🇧, developer @monzo, passionate about travel and leaving the world a better place than I found it
You really cooked with this one
March 31, 2025 at 11:05 AM
You really cooked with this one
Do you have a link to the original post? I can’t find this tweet anywhere
January 8, 2025 at 2:11 PM
Do you have a link to the original post? I can’t find this tweet anywhere
Did the controls in control center not work from the menu bar?
January 8, 2025 at 2:04 PM
Did the controls in control center not work from the menu bar?
Great article Kent! Out of interest, how expensive is the epic web camp? Looking to plan my work’s learning budget for 2025 and I can’t find the price online
November 23, 2024 at 9:24 AM
Great article Kent! Out of interest, how expensive is the epic web camp? Looking to plan my work’s learning budget for 2025 and I can’t find the price online
we don’t want any further division to be required to use rates.
Variable naming is important!
// bad
let fee = 0.035
let feePercentage = 3.5
// good
let feeRate = 0.035
Variable naming is important!
// bad
let fee = 0.035
let feePercentage = 3.5
// good
let feeRate = 0.035
November 22, 2024 at 2:51 PM
we don’t want any further division to be required to use rates.
Variable naming is important!
// bad
let fee = 0.035
let feePercentage = 3.5
// good
let feeRate = 0.035
Variable naming is important!
// bad
let fee = 0.035
let feePercentage = 3.5
// good
let feeRate = 0.035
3. Only round once, as a final step, rather than rounding at each operation
4. Any percentages must be represented as rates (n/1) e.g 3.5%=0.035 as opposed to percentage point units (n/100) or basis point units (n/10000)
4. Any percentages must be represented as rates (n/1) e.g 3.5%=0.035 as opposed to percentage point units (n/100) or basis point units (n/10000)
November 22, 2024 at 2:51 PM
3. Only round once, as a final step, rather than rounding at each operation
4. Any percentages must be represented as rates (n/1) e.g 3.5%=0.035 as opposed to percentage point units (n/100) or basis point units (n/10000)
4. Any percentages must be represented as rates (n/1) e.g 3.5%=0.035 as opposed to percentage point units (n/100) or basis point units (n/10000)
Off the top of my head:
1. Don’t round whenever possible (we use IEEE-754 decimal128 in memory and for calculations, but strings (preferred) or Int64MinorUnits on the wire)
2. When rounding is unavoidable, use ToNearestEven (aka Bankers rounding)
1. Don’t round whenever possible (we use IEEE-754 decimal128 in memory and for calculations, but strings (preferred) or Int64MinorUnits on the wire)
2. When rounding is unavoidable, use ToNearestEven (aka Bankers rounding)
November 22, 2024 at 2:51 PM
Off the top of my head:
1. Don’t round whenever possible (we use IEEE-754 decimal128 in memory and for calculations, but strings (preferred) or Int64MinorUnits on the wire)
2. When rounding is unavoidable, use ToNearestEven (aka Bankers rounding)
1. Don’t round whenever possible (we use IEEE-754 decimal128 in memory and for calculations, but strings (preferred) or Int64MinorUnits on the wire)
2. When rounding is unavoidable, use ToNearestEven (aka Bankers rounding)
This is great!
At Monzo (a bank), we call the “cents” “minor units”, because that’s the more technically correct term globally
At Monzo (a bank), we call the “cents” “minor units”, because that’s the more technically correct term globally
November 22, 2024 at 12:37 PM
This is great!
At Monzo (a bank), we call the “cents” “minor units”, because that’s the more technically correct term globally
At Monzo (a bank), we call the “cents” “minor units”, because that’s the more technically correct term globally
I loved this! The future of arm looks bright!
November 15, 2024 at 3:20 PM
I loved this! The future of arm looks bright!