It depends a bit on context... and scale of scale.
At my first software engineering role the system I 'inherited' (The guy who wrote it quit after it launched, I was hired on after) was only used by 5-10 users at a time. On the flipside, one or two of those users would do things that the system was advertised as being able to do, but would really stress out the system and slow certain operations down for everyone, including exposing our company to financial penalty risks. We actually for a time slowed down trying to get large customers signed up, because even the business folks had to manage enough complaints that they didn't want to risk damage to our reputation. [0]
At my second job, well, I remember the debate I had with the manager about a change I suggested to improve memory allocation on a new email templating process he wrote. He then gave me a lecture about 'premature optimization'. Then when the thing kept crashing with OOM errors he cribbed the parts of my changes that solved the memory leak but left out the pooled buffer to save face. [1]
[0] - The thing was written such that we could only process 2 messages concurrently from a given integration partner at a time, we eventually fixed it by moving the processing to actors behind a consistent hash router.
[1] - The pooled buffer changes were 5-10 extra lines total, lol.
One of the earliest 'mountain biking' trails, before real mountain bikes existed, is called Repack because they were using Coaster brakes and you'd basically have to rebiuld/repack the coaster brake hub with grease after a run due to all the heat forcing the hubs to expel.
My -favorite- setup for Discs, at least use to be, Avid BB7s with Avid Speed Dial levers, with Flak Jacket Housings.
That combination was super simple to 'dial in' (Hydraulic brakes tend to be a lot more inconsistent on 'feel' unless you are very persistent about bleeding and know how to use a disc tuning fork) and honestly had a lot less overall drag than I've experienced with most hydraulic discs. Replacing cables is way easier than re-doing hydraulic lines, also you don't have to worry as much about overheating janking up your fluid. Only drawback is, yes, make sure your cables are set up right and clamped down good.
But yes, Coaster brakes suck, especially since 'failure' means either rebuilding the wheel or outright replacing, because nope, not gonna do that sort of hub job.
One of the things I liked about my Windows phone, was the relative lack of apps made it very hard to fall into addiction 'traps'.
On the flip side, my partner has fallen deep into the cesspit, either seeing her doom-scrolling through Facebook for hours, or the way she talks about all the things she saw on there despite not handling any of the things that she said she would get done that day (FWIW... My partner does not work at this time, she quit her job under the auspices of taking care of the house. Has not gone well. I guess at least she stopped playing cow-clicker games on her phone...)
If I will give my first 'real job' some credit for anything around their Blocking policies, they had extremely strict blocks around anything that could be 'personal use' and had very alarming warnings pop up if you happened to hit one of the blocks. (To the point where even doing legitimate work research I more than once freaked out and went right to my manager and the IT managers explaining my case and what I was doing.)
But it's also part of why the open office / panopticon layout has become more popular; It provides at least some vague threat to somewhat lower the risk folks get sucked into their phones out of view...
Actually the Point and shoot market has largely dried up, even the 'fancier' point and shoots.
Apple did a very smart thing, using Sony BSI[0] and Stacked[1] Sensors in their phones.
As the 'Camera Snob' in the family my Brother recently asked me to help look for a small point and shoot for his wife for their child's events, and I was shocked at how few options there are compared to a decade ago (And how little most have improved since!)
To be clear, the 'ILC' (what many might think of when they think of when they say DSLR) market has continued to advance and the tech is better than ever, but the simple built-in lens point and shoot market has gotten very small outside of certain markets.
[0] - Back Side Illumination, basically a way to build the sensor that allows more light to hit it, but has some yield implications
[1] - Stacked sensors is again another sensor-build optimization, but it allows for faster readout of the full sensor with less rolling shutter, makes 'computational photography' feasible.
Namely, It's very easy to 'design to load' where you don't need to worry about the next shipment of Coal, or an extended weather event causing excessive cloud cover and depleting your reserves.
Heck, even as far as compared to LPG, you don't have to worry as much about disruptions or possible cost shifts around LPG supply.
Yes, I'm possibly tongue-in-cheek handwaving specific types of 'weather events' here and potential impacts, i.e. Tsunamis... OTOH it's a lot easier in current gen designs to make something that would have minimal risk for something, say, in the middle of nowhere Texas.
I don't think there's a law or precedent for that.
The Tucker Act allows for a company to claim damages related to the seizure of property. That is not the same as having a product being stopped from 'shipping'[0].
Also, despite the US Concept of 'Corporate Personhood', Even the Citizens United decision did not set the bar for civil damages to be awarded for a civil rights violation to a 'corporate personhood'. i.e. While they were ruled to have had their First Amendment Rights Violated, there was no financial compensation to be had. The bar for waiving sovereign immunity for an individual/bureau/branch is very high and AFAICT requires specific action from congress.
[0] - The Tucker Act was written in the late 1800s, long before even the concept of Nuclear tech 'Born Secret' doctrine became a thing.
> Even the Citizens United decision did not set the bar for civil damages to be awarded for a civil rights violation to a 'corporate personhood'
I'm almost upset at the notion only being invoked. Let's hope we don't see such a precedence emerge, especially around a company touting to be selling "intelligence".
I'll be rude/bold enough to say that Canada's ability to argue around 'in-country' made goods has been eroded for decades;
I will admit I'm going to point to a specific example; Canadian Bike makers have been able for at least a decade to get an unpainted frame from Taiwan/China/Etc, components from wherever, but so long as they painted the frame in canada and did final assembly in Canada... 'Made in Canada' alongside all of the tariff exemptions that came with that.
> But from Canada's point of view: they have already been threatened enough that im sure those remaining ford,gm and stellantis jobs might be gone eventually...
Guess you didn't hear about Brampton in the news, the Stellantis plant there might be on the chopping block...
Yeah Canada has natural limitations bigger countries like the US does not have but still, I wonder if good negoiation and maybe a changing situation in regards to the US's declining prospects might allow Canada to swing a bit higher in the future and demand something like this. There is a skilled workforce in place as well so maybe that changes the calculus.
TBH I agree with you, even mentioned it in my other reply.
Modern China is not like the Soviet Union; it is much closer to a capitalistic society, but instead of private equity there is a (heavier than even the most 'socialist' of EU nations) government planning push.
In some ways, one could argue they're just taking lessons learned from all of the current systems and applying them aggressively in their centralized planning.
As someone who has lived in/around the heart of the 'Arsenal of Democracy' for my whole life, gotta say they are taking better lessons learned than the US has.
The thing people tend to handwave about China's manufacturing prowess is that they have spent the last 25-ish years getting really good at 'making things to a spec' at a cost in-line with their labor market, being bolstered by their government's approach at Economy planning (i.e. subsidizing certain industries, required partnership agreements when foreign companies want to use that labor market to build things).
The quality of the product you get, like always, is about what people are willing to pay. The big difference is that the current cost of labor/material inputs there, is low enough that you can get the same or often better quality for less.
I wouldn't call that dumping. And to be clear, yeah they've done dumping in some cases.
But when we look at what's happened in the last 8 months or so around various AI SaaS-ish offerings, one could argue that plenty of US companies have done 'dumping with extra steps'. (And that's not even the first time necessarily, e.x. the DoorDash Pizza Arbitrage thought experiment...)
> It's also worth noting that many Chinese manufactured goods would mostly substitute for US manufactured goods (eg cars).
Heck, GM was (although they are moving it due to the Tariffs AFAIR) building the Buick Envision (Compact CUV) in China and shipping it to the US for sale. GM Announced in January that they'd move production to the US by 2028.
Similar for The Lincoln Nautilus (Midsize CUV), The current Gen is built in China and they only in the last month announced that they would move production back to the US... by 2030.
At my first software engineering role the system I 'inherited' (The guy who wrote it quit after it launched, I was hired on after) was only used by 5-10 users at a time. On the flipside, one or two of those users would do things that the system was advertised as being able to do, but would really stress out the system and slow certain operations down for everyone, including exposing our company to financial penalty risks. We actually for a time slowed down trying to get large customers signed up, because even the business folks had to manage enough complaints that they didn't want to risk damage to our reputation. [0]
At my second job, well, I remember the debate I had with the manager about a change I suggested to improve memory allocation on a new email templating process he wrote. He then gave me a lecture about 'premature optimization'. Then when the thing kept crashing with OOM errors he cribbed the parts of my changes that solved the memory leak but left out the pooled buffer to save face. [1]
[0] - The thing was written such that we could only process 2 messages concurrently from a given integration partner at a time, we eventually fixed it by moving the processing to actors behind a consistent hash router.
[1] - The pooled buffer changes were 5-10 extra lines total, lol.
reply