Try to start contributing to some open-source projects, if you don't mind working for free. It will help you to start working with others, more. Not necessarily next to others, but checking into the same codebase as others, and getting your code reviewed. Even reviewing others code.
But it does reduce the cost of research and development coming out of the company's pocket. That said, in a capitalist society, the production price helps to set where companies will stop making it.
The price is actually set to where profit is highest, meaning it's a function of: how many people will buy at various prices and how much does it cost to produce at various quantities.
One of the strong arguments for single payer healthcare, IMHO.
We have a 2 story house where the bottom story is a daylight basement. When it gets hot, it usually stays pretty cool downstairs, so we hang down there during the day. In the evening, as soon as it's cooler outside than upstairs inside, we open the back door, both downstairs and upstairs, and turn on a high powered fan blowing air up the stairs... It is really effective at cooling the house.
Always assume any communication on your work network can and will be monitored... If you want a private discussion, best to do it in person or on your own devices, not using any company resources.
I don't know... There's a lot that's not being said in that article... As is the case in all articles about court cases... Or court cases, in general. I feel a very real, "burn the witch" attitude when it comes to hackers and coders mixing with the justice system...
Even when that does happen... and I'd argue that it often does not, if you've done the work to make your interface pretty, and write a precise, accurate test suite, you've usually done the work to make the actual functions neat and orderly...
Even when you end up with a black box full of entropy, it's segregated from the rest of the system. You can feel free to change the rest of the system around it and know that the black box will keep doing it's job, as long as you keep using the well-written API within spec.
But, that's not all you get... because you took the time to write the tests, you can refactor this entropy box to your heart's content... until it starts looking more approachable. You've got your tests around the API, right? Then you don't even really need to change them to do the refactor work. The only reason to change the tests would be if you want the function to do something else (or you missed something, of course).
Take small steps... refactor out a couple lines at a time... run the tests with each iteration. Based on previous experience, you're going to end up with a fairly clear and concise implementation... not to mention performant.
I like toml because it's easy to read and write as a human, even without text editor help...