We can’t test yet, we’re going to make changes soon
This could be a good opportunity to introduce the concept of test-driven development (TDD) without the necessity to “write tests first”. But I think it can help illustrate why having tests is better when you are expecting to make changes because of the safety they provide.
“When we make those changes, wouldn’t it be great to have more confidence that the business logic didn’t break when adding a new technical capability?”
You shouldn’t have to refactor to test something
This seems like a reasonable statement and I sort of agree, in the sense that for existing production code, making a code change which only adds new tests yet also requires refactoring of existing functionality might feel a bit risky. As other commenters mentioned, starting with writing tests for new features or fixes might help prevent folks feeling like they are refactoring to test. Instead they’re refactoring and developing for the feature and the tests feel like they contribute to that feature as well.
It’s probably not going to work as a defense against training LLMs (unless everyone does it?) but it also doesn’t have to — it’s an interesting thought experiment which can aid in understanding of this technology from an outside perspective.
Related: ts10 aluminum silver, red, and green hosts are being discontinued according to Wurkkos, but not black, so it might be a good time to stock up.
I hope that they can recover from this and repair all the lights that were already produced. The performance was excellent in TacGriz’s review so it’s clear the driver quality is much higher than Acebeam H16. Safety is kind of important though 😀
Hank Wang:
You can always request us to modify the driver a bit (remove the spring), so that D2 can work with the unprotected, button top 14500 battery only
Thanks. Good point about scratches - also makes me think that when the T3 coating scratches the metal could be exposed, leading to patina in those spots only.
Do folks find raw copper practical to carry? I’m interested in the Convoy T3 copper because (I think) it’s coated so no patina would develop. But I understand the metal changing is desirable to some.
It looks like the AAA Solitaire goes up to 47 lumens, which is pretty easy to find in a similar size. I have used the acebeam pokelit AA (not 2xAA) which has been reviewed quite a bit and can be found on amazon in the US for under $20. It is sold with an included 14500 cell which also has a built-in usb-c charger. So you would need to unscrew the head (which has a glass lens I think not plastic) to charge the battery, preventing water or other ingress.
I’m not sure if it makes sense to invest in a very durable but more expensive light in the event it does end up broken, but if you want to, zebralight is well regarded for durability and you can get a single-AA model and use rechargeable Nimh cells if you would like: https://www.zebralight.com/SC53c-N-Neutral-White-High-CRI-AA-Flashlight_p_249.html. They also offer other models supporting lithium-ion.
I agree with how you characterized it and the term “ai engineer” didn’t resonate with me as defined by the author. If such an engineer doesn’t need to know about the data involved (“nor do they know the difference between a Data Lake or Data Warehouse”) then I don’t think they will be able to ship an AI/ML product based on data.
New titles can be helpful for sorting out different roles with some shared skillsets such as the distinction which emerged between Data Scientist and ML Engineer at some companies to focus the latter on shipping production software using ML.
Thank you! I’ll also look into Weller’s product line for reference.
The “smart” aspect of the pinecil gives me a slight pause as I wouldn't need it at the moment, but I suppose that just like in flashlights with Anduril I could simply ignore the advanced features.
I appreciate it! This looks like the one. Just going to look into the UI first but presumably I will only need to set a temperature or two and turn on and off, simple enough.
Thank you for the great rec! Will check each of these out. Looks like the Pinecil runs something that might be (at first glance) the soldering iron counterpart to Anduril: IronOS.
This could be a good opportunity to introduce the concept of test-driven development (TDD) without the necessity to “write tests first”. But I think it can help illustrate why having tests is better when you are expecting to make changes because of the safety they provide.
“When we make those changes, wouldn’t it be great to have more confidence that the business logic didn’t break when adding a new technical capability?”
This seems like a reasonable statement and I sort of agree, in the sense that for existing production code, making a code change which only adds new tests yet also requires refactoring of existing functionality might feel a bit risky. As other commenters mentioned, starting with writing tests for new features or fixes might help prevent folks feeling like they are refactoring to test. Instead they’re refactoring and developing for the feature and the tests feel like they contribute to that feature as well.