2,054 karma · joined May 24, 2012
To me it seems a theoretical discussion about the definition of free speech that is mixed up with a business discussion which makes no sense.
In fact I had also been working for some time on actually cool tech and was looking forward to go into the office as early as possible and stay late. But as I "progressed" I worked on more and more boring problems and products. The by far most exciting tech is what I use in my free time.
Also it seems that only a small fraction of tech products nowadays are driven by tech geeks.
Also I don't buy anymore that Bitcoin is resilient to inflation. Inflation is a financial symptom but caused by a failing real economy. Dividing out the inflation just leads to other malfunctions...
That said, until shit had been hitting the fan a lot of facts about PFAS had been kept in secrecy with active manipulation going on. Even today there isn't much authorative and practical information available.
Also the practical benefit of Teflon pans over say Emaille or iron pans is more than questionable. Are professional cooks really using Teflon pans?
Also the cost of these lies are immense for companies, managers, employees and customers. Assigning employee A for one task and B for the other although it should be reverse. IMHO that's also the reason why companies ship products that are profoundly bad for their customers and only "realize" this after many years.
I know of a few people for who that is the reason why they prefer working in startups.
IMHO the refactoring sounded very reasonable since the old code base was unmanageable. But there was a culture of extreme pressure from the CTO, making everyone haste through tasks preventing everyone to do "proper engineering". At the time the CTO was in some sort of permanent absence already. Afterwards the team lead left because of burnout, I also left and later on I heard they closed down the company.
Actually I've seen similar destructive refactorings at other places. At one they also had a lot of subtle problems leading to many user complaints. It could be fixed but by then it was already too late.
IMHO refactorings are great but it's always necessary to keep regressions in check all the time and really understand the design decisions of existing code.
Also the title is a bit click-baity. The protestware example is clearly weaponization of OSS but the other examples are not.
At workplaces this creates a lot of absurd situations that eat up insane amounts of productivity.
Or another example, it's pretty common that water pipes don't work as expected. (Congestion, low pressure, undesired backflow, tricky to get water at body temperature...) Nobody really complains, everybody lives with it and learns to completely ignore it. I'm not saying these problems occur everywhere 100% of the time but often enough to show there's something structurally not working
(With dropping a bomb I also mean something like a larger/tedious amount of work)
If you install services like email or http prefer software with a small footprint and with few CVEs in the past. Since http services are quite common, it's advisable to put a reverse proxy in front. Separate users for separate services is also a good idea.
Never had any issues with that kind of setup. Of course it's possible to add additional hardening like using an ssh jump host or a VPN to access ssh. (Probably advisable if you plan to put private data on it) Also using SELinux is an option, Fedora has it by default.
Actually ImplicitCAD is written in Haskell which implements CSG (very tricky to efficiently implement)