For music: if (and that’s a big if) Spotify does not fuck that up they’ll have the majority of people off the harbours.
They deliver exactly what people asked for when it was common to pirate music. A monthly affordable fee, +90% of the music available and no advertising. If neither of these three variables are changing, there will be no big group pirating music anymore.
Yes and no. I did build several in-house enterprise applications and for this I know about this problem. And yes you’re right, a lot of the complicated contexts are more complex than searching on Google.
But! Enterprise software architects have a tendency to make every feature as visible, and also making the apps as feature rich as possible. This comes with high costs.
I always try to establish a strive with exactly what google delivers.
Cage the user in his first decision, Filter or action and then show him or her the application with all the features feasible in the chosen context. It is amazing how complexity reduced most of these applications are when you just ask this first question.
Imagine a webser or proxy and for every incoming request it creates an new thread 💣
Yes you’re right if it’s a second or third thread it is/may be fine. But if you’re i/o bound and your application has to manage quite a lot of that stuff in parallel, there is no way around delegating that workload to the kernel’s event loop. Async/Await is just a very convenient abstraction of that Ressource.
If you have an avr you could just use avr-hal.
The documentation is ok and if you used to work with arduino it should be straight forward.
Story points are meant to have a shared understanding about complexity during the planning phase. There where never meant (and do not fit) for either capacy planning or to measure the throughput.
If your PO is using this he or she is either not well informed and/or uses this as a tool to create toxic pressure.
If you do so, what you shouldn’t please write one unit test, failing as long that flag is set.