a) Solution X does it generally better than Y and their solution is *ported*.
b) Adapt to solution Y. The end.
* Does it work in an airplane?
* Does it work in a submarine?
* Does it work in the mountains, when a thunderstorm is approach and you need to share the GPX?
* No XML
* Simple to read and understand
* Simple to manage dependencies
* Simple to use options
* You need to be very careful. Select alwaysCTO build with the best available display. But even then, Lenovo *removed* the HiDPI display from the X13. The only actual competitor to the MacBook Air is the ThinkPad X13.
* Lenovo added useless camera humps protruding out of the panel. There is a thick bezel and enough space for a much better camera. And for opening the laptop used to be a dent in the (round!) palmrest, nothing protruding.
* AMD, Intel and Lenovo fail to ship a fanless X13 and T14. I would happily keep same performance for two years, just getting rid of it.
* Lenovo is drowning us in Yogas, Z13 or whatever Legion.
* Big size is a status symbol in Asia. And TV replacement. Their a lot of people in Asia.
* Due to vendor lock-in people need to purchase anyway. So just sell them the standard phone.
Restart braking to brake because our code failed.
One single sensor delivers wrong data. Let us put the trim down. DOWN! DOWN!
But I’m only programming a text viewer.
Generates entire websites with AI Slop. Instead of sending a single text mail with three links and the words please make that certificate.
No. He wastes the time of all personnel. Wastes energy. And hides the important message in a wall of text (I was the only person which recognized, that he requires the certificate…it was hidden in a side box).
Right now we re-implementing every frogging tool which was ever developed by more experienced people.