Jordan Mele
@djmm.me
Software Engineer at Canva. Open source. Typo mstr. Opinions are my own.
Caching maybe?
One way to check would be building after a change, then reverting that change and building again. Comparing times as you go (assuming the margin for error isn't larger than the difference).
One way to check would be building after a change, then reverting that change and building again. Comparing times as you go (assuming the margin for error isn't larger than the difference).
December 23, 2025 at 1:29 AM
Caching maybe?
One way to check would be building after a change, then reverting that change and building again. Comparing times as you go (assuming the margin for error isn't larger than the difference).
One way to check would be building after a change, then reverting that change and building again. Comparing times as you go (assuming the margin for error isn't larger than the difference).
Go (a sanctioned language) was in place before Rust and my team gave it a try. Didn’t get much traction and the error handling a common source of mistakes.
Jump to 2025 and there are no sanctioned languages. Just need to make a good case for inclusion.
Jump to 2025 and there are no sanctioned languages. Just need to make a good case for inclusion.
November 25, 2025 at 7:07 AM
Go (a sanctioned language) was in place before Rust and my team gave it a try. Didn’t get much traction and the error handling a common source of mistakes.
Jump to 2025 and there are no sanctioned languages. Just need to make a good case for inclusion.
Jump to 2025 and there are no sanctioned languages. Just need to make a good case for inclusion.
Pretty much.
First showed up in 2019 being used by a single team and went mostly unnoticed.
In 2023 support was added to Bazel.
In 2024 my team picks it up (mainly for build and devx things). It took off from there and is now finding usage across our stack.
First showed up in 2019 being used by a single team and went mostly unnoticed.
In 2023 support was added to Bazel.
In 2024 my team picks it up (mainly for build and devx things). It took off from there and is now finding usage across our stack.
November 25, 2025 at 7:07 AM
Pretty much.
First showed up in 2019 being used by a single team and went mostly unnoticed.
In 2023 support was added to Bazel.
In 2024 my team picks it up (mainly for build and devx things). It took off from there and is now finding usage across our stack.
First showed up in 2019 being used by a single team and went mostly unnoticed.
In 2023 support was added to Bazel.
In 2024 my team picks it up (mainly for build and devx things). It took off from there and is now finding usage across our stack.
Stockout in us-east-1.
Taking a jab at AWS there but same-same for GCP’s us-east1.
Taking a jab at AWS there but same-same for GCP’s us-east1.
October 31, 2025 at 11:24 PM
Stockout in us-east-1.
Taking a jab at AWS there but same-same for GCP’s us-east1.
Taking a jab at AWS there but same-same for GCP’s us-east1.
There is definitely an art to getting anything useful out of it. Same can be said for most places reviews can be left.
October 24, 2025 at 1:09 AM
There is definitely an art to getting anything useful out of it. Same can be said for most places reviews can be left.
No arguments that most obsolescence nowadays is by design. Not much to be gained with new gen stuff accomodating regressions in software efficiency (ignoring use cases like local AI and gaming), feels like you’d at least get something decent out of it. Like a noticeably faster system.
October 20, 2025 at 10:54 PM
No arguments that most obsolescence nowadays is by design. Not much to be gained with new gen stuff accomodating regressions in software efficiency (ignoring use cases like local AI and gaming), feels like you’d at least get something decent out of it. Like a noticeably faster system.
Not surprised to hear ASUS did that, I understand their warranty process had (and maybe still is) acting in bad faith. Reputation wise, it fits.
October 20, 2025 at 10:40 PM
Not surprised to hear ASUS did that, I understand their warranty process had (and maybe still is) acting in bad faith. Reputation wise, it fits.
That pending diagnosis turned out to be a MB failure (chip on the board burned out). Lasted 10 years, so not too bad. Thankfully all other parts are fine, so I turn what remains into an AM4 build for relatively little vs. going all new.
October 20, 2025 at 11:48 AM
That pending diagnosis turned out to be a MB failure (chip on the board burned out). Lasted 10 years, so not too bad. Thankfully all other parts are fine, so I turn what remains into an AM4 build for relatively little vs. going all new.
GPU? Market has been weird ever since crypto mining pushed everything up. Whatever says it supports the display numbers and resolutions should meet your needs. NVIDIA GeForce, Intel Arc, AMD Radeon, pick your poison, AMD has historically had driver issues though (stable currently for me).
October 20, 2025 at 8:56 AM
GPU? Market has been weird ever since crypto mining pushed everything up. Whatever says it supports the display numbers and resolutions should meet your needs. NVIDIA GeForce, Intel Arc, AMD Radeon, pick your poison, AMD has historically had driver issues though (stable currently for me).
Not much I can say for storage beyond take a look at ReFS if you haven’t already (with backups). Supposed to have several tricks around IO, could help but benchmarking would be needed to confirm.
October 20, 2025 at 8:56 AM
Not much I can say for storage beyond take a look at ReFS if you haven’t already (with backups). Supposed to have several tricks around IO, could help but benchmarking would be needed to confirm.
Continuing CPU, for any custom data processors you’ve got (not SQL Server) it’s worth seeing if they can take advantage of SIMD extensions like AVX512. For relevant workloads they can slash wall time.
October 20, 2025 at 8:56 AM
Continuing CPU, for any custom data processors you’ve got (not SQL Server) it’s worth seeing if they can take advantage of SIMD extensions like AVX512. For relevant workloads they can slash wall time.
For CPU, more cores (threadripper) is probably more important than L3 cache (x3d). Provided SQL Server is actually using them and not bottlenecked on bandwidth. Behaviour of your current rig may provide some insight there.
October 20, 2025 at 8:56 AM
For CPU, more cores (threadripper) is probably more important than L3 cache (x3d). Provided SQL Server is actually using them and not bottlenecked on bandwidth. Behaviour of your current rig may provide some insight there.
For memory, I’m pretty sure G.Skill is selling the fastest sticks (if you can find it). Dual vs quad channel MB configuration is a factor in bandwidth, but not one I’m familiar with.
October 20, 2025 at 8:56 AM
For memory, I’m pretty sure G.Skill is selling the fastest sticks (if you can find it). Dual vs quad channel MB configuration is a factor in bandwidth, but not one I’m familiar with.
Damn. TPM 2.0 was fine on all mine for W11, CPU generation cutoff is what caught them all. Real shame since they are all more than capable.
😔 There is gonna be so much eWaste over the next few months/years with 10 reaching end of support.
😔 There is gonna be so much eWaste over the next few months/years with 10 reaching end of support.
October 20, 2025 at 2:39 AM
Damn. TPM 2.0 was fine on all mine for W11, CPU generation cutoff is what caught them all. Real shame since they are all more than capable.
😔 There is gonna be so much eWaste over the next few months/years with 10 reaching end of support.
😔 There is gonna be so much eWaste over the next few months/years with 10 reaching end of support.
Brand is probably a factor, though I suspect environment is a factor (cat fur, I’ve had a lot less issues since moving).
October 19, 2025 at 1:02 AM
Brand is probably a factor, though I suspect environment is a factor (cat fur, I’ve had a lot less issues since moving).
My luck with motherboards is worse. 1 RMA (BIOS crash-loop), 2 post-warranty (same issue, but with workaround), and possibly one more pending diagnosis. All GIGABYTE brand.
October 19, 2025 at 1:02 AM
My luck with motherboards is worse. 1 RMA (BIOS crash-loop), 2 post-warranty (same issue, but with workaround), and possibly one more pending diagnosis. All GIGABYTE brand.
I’ve had less luck with RAM. A DDR4 stick from ADATA and the soldered chips in a Surface Book 2. In both cases the symptom was crashes after a few minutes.
October 19, 2025 at 1:02 AM
I’ve had less luck with RAM. A DDR4 stick from ADATA and the soldered chips in a Surface Book 2. In both cases the symptom was crashes after a few minutes.
Smaller sample size with me, and no HDD failures.
I have had an M.2 SSD die though, after about 5 years. Still far below the rate of other components (RAM, MB).
I have had an M.2 SSD die though, after about 5 years. Still far below the rate of other components (RAM, MB).
October 17, 2025 at 10:03 PM
Smaller sample size with me, and no HDD failures.
I have had an M.2 SSD die though, after about 5 years. Still far below the rate of other components (RAM, MB).
I have had an M.2 SSD die though, after about 5 years. Still far below the rate of other components (RAM, MB).
How does this relate mandatory MS account? Easier to upsell.
October 8, 2025 at 1:05 AM
How does this relate mandatory MS account? Easier to upsell.
Windows becoming more and more freemium like with all the embedded upsells (Game Pass, OneDrive, 365) all the while STILL BEING A PAID PRODUCT! 😡
October 8, 2025 at 1:03 AM
Windows becoming more and more freemium like with all the embedded upsells (Game Pass, OneDrive, 365) all the while STILL BEING A PAID PRODUCT! 😡
Probably worth treating transitive dependencies as part of the package identity in case malware is delivered indirectly.
December 29, 2024 at 1:56 AM
Probably worth treating transitive dependencies as part of the package identity in case malware is delivered indirectly.
Chunks of the ecosystem are dependent on lifecycle scripts, so outright disabling would be a mistake I think (usability wise).
For security, an option is asking for permission to run them in high risk scenarios (e.g. during updates for any new package).
For security, an option is asking for permission to run them in high risk scenarios (e.g. during updates for any new package).
December 29, 2024 at 1:55 AM
Chunks of the ecosystem are dependent on lifecycle scripts, so outright disabling would be a mistake I think (usability wise).
For security, an option is asking for permission to run them in high risk scenarios (e.g. during updates for any new package).
For security, an option is asking for permission to run them in high risk scenarios (e.g. during updates for any new package).
I'm going to tempt fate again and point out that there are multiple new line characters. Some which operate as pairs.
Unicode even went as far as adding new ones. LS and PS. For the lulz I guess.
Unicode even went as far as adding new ones. LS and PS. For the lulz I guess.
December 12, 2024 at 4:43 AM
I'm going to tempt fate again and point out that there are multiple new line characters. Some which operate as pairs.
Unicode even went as far as adding new ones. LS and PS. For the lulz I guess.
Unicode even went as far as adding new ones. LS and PS. For the lulz I guess.