462 karma · joined July 28, 2020
The people who design/build enterprise software rarely eat their own cooking. Feedback cycles are infrequent and long or non-existent.
Apple's handling of the situation is baffling. "Let's martyr the smaller company!"
Like all masterful operations guys with an MBA™, he either forgot or ignored an ancient adage. In his case it was, “don’t put all your eggs in one basket...and don’t put all your baskets in one boat.” At no point did he or anyone at Apple question the narrative that China could merrily support their supply chain without any hiccup into eternity.
Apple reaped the rewards for 20 years, and now the lack of meaningful hedge could undo all of it...with one Tweet or two.
That's why they behave in funny, distorted ways, like pissing off their developer community and acting baffled that the community is getting irritated.
Once you've got that rule down, pick a popular language (Python's good because you can ask questions and get answers), pick a simple program that'd be useful to you, and then figure out what you need to make it work. Then make it work, applying rule #1. Rinse and repeat.
I always thought that would be useful on a screen.
For decades I assumed that there’s some weird fluky behavior when trying to select a word and accidentally selecting the paragraph.
But no one is a prophet in their own city...so getting ideas from the outside looks nicer...
I could see quite a big market of bozos for this if you market it right.
Drunk vs. Sober Tired vs. Awake Hungry vs. Satiated
Amazing how dramatically each changes your perspective.