orthogonal_cube
Joined 8 months ago
Joined 8 months ago
I’d love to know what internal services and tools that are included in this, as well as any deliverables that shipped as software products to customers.
If it’s legacy code for IOS firmware, however, I’d be very worried.
I’m not against employee names and contact info being made public. That’s no different than someone’s business card being passed around. What I worry about is that all DHS employees get lumped together indifferently by disgruntled individuals and harassed using the information made available.
People who are (rightfully) angry by ICE’s activities in recent deportations, wrongful detaining of US citizens, and misuse of force are going to begin harassing these employees indiscriminately. I’ll admit that I don’t care if they do it to anyone listed as employed under ICE, but some departments elsewhere in CBP have actual positive purposes. Customs agents who scan incoming goods for invasive species, for example, help prevent the destruction of domestic plants.
I guess we just have to see how this info is used and what the effects will be.
This is a major contributor for specific models. I was listening to my brother complain about a vehicle that rolled into their shop lately and how the engineers really didn’t think about how difficult it would be for technicians to service things. Some parts are fairly inexpensive and easy to replace but you have to remove the engine or transmission in order to get enough clearance to swap out the part!
> If Claude is to significantly increase the rate of new cures, we need to work with many more biotechnology firms and integrate Claude more deeply into their development processes.
Given all that, the wording here feels very self-serving. Cautious optimism is probably warranted.
Because it safeguards against fraud and tax evasion.
> Paying 2-5$ fees on trades seem backwards this day and age.
Many brokerages don’t charge for buying or selling stock. They make their money elsewhere, likely with contracts on calls/puts. But to your point, having to pay a variable rate fee for moving my Ethereum from one wallet I own to another wallet I own also seems silly. I’m certain though that in both cases the charges cover the maintenance costs to keep the platform going. Everything comes at a cost.
What?!
Unit testing was to ensure the code operated according to an intended specification or outcome especially when it deals with a complex support matrix. It extended well beyond the codebase itself! You can have language errors where output behaviors differ between one supported version to another (ex. Java 11 vs Java 17), runtime errors that are specific to operating system quirks (ex. RHEL 8 vs RHEL 9), or workarounds added to your codebase for known bugs in different dependency libraries you support at compile/run time (ex. Net-SNMP 5.2 vs 5.5). It wouldn’t matter if someone read all your code; you would still have the potential for errors caused by the components needed to run your software.
If your project doesn’t have to worry about these types of issues then lucky you and continue on without unit tests for as long as you can.