Give me more like these… Search engines are a great tool for content discovery beyond the simple text searching. Often, it is difficult to express exactly what we are looking for. This may be due to limitations of the interface, or our own struggle to explain it in enough detail. There is one thing, however, which we are fairly good at. Given two things, we can easily say which one we like more than the other.

I have been using iOS 13 / iPadOS / watchOS 6 for a couple of weeks now. My general impression: something seems a bit off. Don’t get me wrong, the new features are great. I totally love the Dark Mode support, the new Notes features, etc. I also have managed to get through the whole update phase without any major issues. No iCloud syncing problems, no significant battery drain, no frequent restarts, or any of the kind. Yet, there are many tiny things that give a feeling of something unfinished. The worst thing is, those used to work in previous OS versions, and they do now too, but only sometimes:

• copying links and files between Apple devices occasionally won’t happen
• the same for the new Share Sheet. Sometimes, I’d keep tapping an app or an action several times and nothing would happen.
• when running the Apple Watch in Cinema Mode, tapping the screen might not wake it up. Sometimes, up to four or five taps were needed.
• Apple Pay occasionally won’t open up on a double tap.

If those were all things that did not work in general, I wouldn’t t be worried. Those I am sure that Apple would have fixed by now. What worries me are those many tiny things that work most of the time, but often fail to do so. I know from experience with the the products that I have been working on that those are the issues that cause the most customer distrust, because of being treated as working.

P.S. All of this reminds me of:

Broken windows theory - Wikipedia

Theory

Source: - https://en.wikipedia.org

Even in a simple language like Go, concurrently updating mutable state is like playing with fire. Take this piece of code, for example: l := content.NewLoader() l.PageCount = 5 c := l.Load(bytes) Can you be sure that what you are loading is actually going to contain five pages? What if another goroutine having access to l, interjects and sets PageCount to 1000? Or worse, updates the state of l such that a panic is inevitable?

Kickstarter has made its position clear. It is against unions. It opposes its workers’ effort to organize. It will not be changing its mind. It will be fighting its own staff and its project creators. Now, Kickstarter’s users must make their position clear. We will not tolerate union-busting. We will not give our money to a company that does it. We demand that the company reverse its position and commit to voluntarily recognizing the union if a majority of workers signal support. The company is taking its workers and users for granted. If they get away with it, other companies will feel even more empowered to crush their own organizing efforts. It is critically important that Kickstarter be loudly opposed.

Kickstarter To Workers and Project Creators: Drop Dead | Current Affairs

<p>The company doubles down on its anti-union stance and says it plans to fight its workers to the bitter end… </p>

Source: - https://www.currentaffairs.org

Chiefly, Go sacrifices expressiveness for uniformity.

The general principle is to favour the transparent and ready-to-hand over the remote and opaque, the concrete and literal over the abstract and magical. It’s like speaking a language without metaphors.

Learning Go won’t teach you any exciting new computer science concepts, or introduce you to a whole new paradigm of software development (for that, try Idris). But it will give you a better understanding of the breadth and variety of the design space for programming languages, at a time when mainstream languages generally seem to be converging (Kotlin is rather like Swift, is rather like Typescript, etc). Sometimes it isn’t the innovative new features that distinguish a language, but its choice of restrictions.

From Java to Go, and Back Again - OpenCredo

Introduction: fitness landscapes, Cassandra, and making things worse   In evolutionary biology, a fitness landscape is a way of visualising the relationship between genotypes and reproductive success. Each possible variation of a genotype is projected onto a position on a map, and the height of the terrain at that position represents the reproductive success associated …

Source: - OpenCredo

Despite being a video-focused platform, people are increasingly coming to YouTube to look for podcasts. A recent survey of Canadian adults found that 43 percent of people “went to YouTube for podcasts in the past year.” That put YouTube ahead of Apple Podcasts (34 percent) and Spotify (23 percent).

Some of the top podcasts on YouTube are pulling in millions of views every few days or weeks. Top shows, like Ethan and Hila Klein’s H3 Podcast or Joe Rogan’s Joe Rogan Experience, have dedicated audiences who use YouTube notifications as an RSS feed, letting them know when a new episode is available to watch. While the podcasts are also distributed via Spotify and Apple Podcasts, YouTube acts as a first stop.

YouTube creators are turning the site into a podcast network

And they’re launching secondary channels to do so.

Source: - The Verge

If you wake up on a Casper mattress, hail a Lyft to get to your desk at WeWork, use DoorDash to order lunch to the office, hail another Lyft home, and have Uber Eats bring you dinner, you have spent your entire day interacting with companies that will collectively lose nearly \$13 billion this year. Most have never announced, and may never achieve, a profit.

Too many consumer-tech companies nearing their public offerings are selling magic shows at a science fair. The unicorns aren’t doomed, even if their old valuations are. But they have to change their stories, and their businesses. Magic made them. Only math will save them.

WeWork and the Great Unicorn Delusion

Why the consumer-tech revolution can’t seem to survive public scrutiny

Source: - The Atlantic

You have seen them many times. Small snippets of code and the question “What would the the following piece of code print” beneath. You might have tried taking a guess, and perhaps, even failed. #golang pop quiz: what will this print? https://t.co/99xR8wybpp pic.twitter.com/Q7YpJbYr8c — ✕✕✕✕✕ (@peterbourgon) May 18, 2017 I find those kinds of questions utterly pointless. They not only teach you nothing about real-world programming, but might also lead many newcomers to long-term frustration with programming.