It's more of a cost benefit analysis as the author pointed out. When so much of valuable content is surfacing in hackernews and other streams, it's not cheap, rather a wise decision not to spend money.
We could automate the link posting process. Here is a thought, create a form which accepts the input of link details, stores in some place and ur website reads and displays from there. Submitting a form could be simpler and can be done from any device.
Yes and no, abstractions dumbed down things for common users. But there are and will always be a set of power users who get into the details. Power users are the ones who abstract in the first place and abstraction is not a one time process. Abstraction keeps evolving too, hence there are going to be power users who know the capabilities and support in the evolution. This is any how stream works let alone software. There is no need for everyone to be a power user.
This is just an initial version. Their primary focus is to link the Instagram user graph with threads to build a solid use base. The decoupling should emerge in later versions
I feel there are two kinds of people. The ones who derive happiness from posting online and the others who restrain from it. Baby isn't the provoking factor to exhibit the behaviour.
Use feedly? Duh. Following a feed functionality which is a pretty basic feature is a bug for weeks now in the mobile app. It's not the best reader to go!
One thing i can share from my experience is, some people communicate poorly because of laziness.
In this case, Even if the vague communication is understandable to you since you are aware of the dev's current WIP, pretend you don't understand and nudge the developmer to add more details for the context as necessary.
For example let's say your team has 5 services. The developer pings you : when starting the service i am facing this exception, tried different ways couldn't figure out, can you please help? .
Questions : Which service is he trying to start? Which machine is he trying to start?(local/virtual).
He probably doesn't mention these details because he thinks you must be aware of what he is working on. Even if you know the same, you can ask these questions and ask to mention such infos going forward to improve their communication.
The idea is to communicate clearly as with any developer and not to take things for granted due to laziness in typing the relevant details.
https://gatling.io/
Gatling is one among the load test tools people need to give a shot. It uses akka for generating asynchronous loads. And it's good from a programmer standpoint since load test scripts can be programmed and maintained as any other script.