Interesting, thank you Ryan for sharing that. I for sure want to explore it more, just for the reason that it attempts to bring Microsub and regular feed readers together.
Links
Thank you Aaron. I am confident the consistency of Aperture will consistently grow with more edge cases covered. On client, I did try all the apps, both on web (Together) and iOS (Indigenous). I found Monocle to be the most stable one. I do not think my primary concerns around posts display are addressed by any. But anyway I will use these apps a bit longer. I want to use this system, really!
★ Liked “Shameless vs. shameful” by Seth Godin
Shaming a person is a senseless shortcut. When we say to someone, “you’re never going to amount to anything,” when we act like we want to lock them up and throw away the key, when we conflate the behavior with the human–we’ve hurt everyone. We’ve killed dreams, eliminated possibility and broken any chance for a connection.
★ Liked “Inside X, the Moonshot Factory Racing to Build the Next Google”
(..to qualify) It must involve solving a huge problem. It must present a radical solution. And it must deploy breakthrough technology.
May be that’s why Loon is all we hear.
“Magic Leap Finally Demoed Its Headset And It Is… Disappointing” — the valley between promises and reality keeps biting the tech media. When will we learn to not get excited by demos?
Though I agree with Daniel’s sentiment, it’s part of the overall cycle of creation — inspiration, ideation, implementation, appreciation, recognition. It is not must for all creations to pass through this, but it’s significant if one does.
So, AirPods remain the wireless earphones of choice for many, primarily due to the ease of use, design and comfort. Bluetooth is a hated technology amongst staunch audiophiles, Apple just made it bearable by making the experience frictionless.
I really liked this comment from a hacker news thread1 on a post around how Microservices architecture failed a product’s dev team.
Everytime (sic) you touch something under a repo, it affects everyone. You are forced to use existing code or improve it, or you risk breaking code for everyone else. What does this solve? This solves the fundamental problem a lot of leetcode/hackerrank monkeys miss, programming is a Social activity it is not a go into a cave and come out with a perfect solution in a month activity. More interaction among developers means Engineers are forced to account for trade offs. Software Engineering in its entirety is all about trade offs, unlike theoretical Comp Science. Anyway, this helps because as Engineers we must respect and account for other Engineers decisions.
Working on a shared code is indeed a social activity. And this principle is something I just can’t stress enough when amongst my team. There is a misguided view of coders as lone warriors, sitting in the dark corner somewhere, beating at their keyboards and delivering working software day and night.
Reality can’t be farther in most work environments, especially enterprises. Every coder needs to be accountable, extra cautious with each line of code he or she commits to the repository. If not, it might lead to a sleepless night of debugging for the whole team.
I do not endorse the tone, of course. It’s from hacker news forum after all. May be people get trained to shout once you are in forum.↩
★ Liked Throwing and Catching by Seth Godin
We spend most of our time in catching mode. In dealing with the incoming. Putting out fires. Going to meetings that were called by other people. Reacting to whoever is shouting the loudest.
But if we learn a lesson from jugglers, we realize that the hard part isn’t catching, it’s throwing. Learn to throw, to initiate, to do with care and you’ll need to spend far less time worrying about catching in the first place.