[1] https://www.pbs.org/newshour/economy/making-sense/heres-what...
97 karma · joined February 6, 2018
[1] https://www.pbs.org/newshour/economy/making-sense/heres-what...
I have to point out that your build isn't entirely an old computer. Having an SSD makes a major difference. If you were to use an IDE HDD or even an old SATA, you'd probably think differently.
Nevertheless, an interesting exercise.
Given that the sender didn't provide constructive feedback, is seemingly not contributing financially, and can simply choose to not use the application, I don't see why a response in kind shouldn't be given. To me, Don's response was mild.
I have to say that Crump was incredibly forgiving and put in a lot of extra effort. I don't think anyone I've been taught by would have gone to this much trouble.
What a ridiculous post.
For some apps, the big issue is when you schedule the downtime to happen. If you are truly customer-centric, you should schedule for a time that causes the least disruption for your users. Of course, a decision like this depends on other factors - the number of users likely to be affected, how critical the app changes are, costs, etc.
I've noticed a number of companies in my country taking sites and apps offline in the middle of the workday when they're very likely to be in use. To me, this is unacceptable - the work on the app should be done after hours.
This whole issue is another example of how hard it is for all of us to make good decisions about privacy. Most people wouldn't think about privacy being a problem when using Avast. Even if you do read the privacy policy you actually can't be entirely sure what's being done with your data (which you indicated in your original October 2019 article). However, it appears that you're safe because the data will be anonymised. There's nothing more for you to do at this point other than trust that Avast is handling anonymisation correctly.
I wonder if it's actually possible to anonymise data effectively yet still make it useful. Based on literature such as the academic article you referred to [1] and another I looked at a long time ago [2], it seems to me that with enough seemingly unrelated data you can identify most people.
[1] De-anonymizing Web Browsing Data with Social Networks [2] Robust De-anonymization of Large Sparse Datasets
The Affinity suite is great and affordable for me as a hobbyist. Many of the open source packages are also excellent.
In defence of the developers/programmers, many people are really bad at explaining what they want, not least because it's often not what they actually need.
If a designer is designing something that looks good but doesn't work well (i.e., solve the problem), they are bad at usability/UX. They should be getting user feedback on their design before it's implemented - that's what user-centred design is about.
There's often a gap when it comes to understanding requirements - between the end-user and the developer, between the designer and developer, etc. Requirements gathering is actually a specialised skill and one of the key duties of a business analyst.
"we always forget that maintenance in perpetuity is much much harder"
I imagine that part of the problem is that the heavy maintenance for large engineering projects begins years or decades after completion. Upon completion, it's hard to imagine these huge creations falling apart; add to this an element of "this won't be my problem (I won't be here in 50 years)" and you've got a recipe for short-term thinking - especially by those who don't have the expertise (read: the politicians and bureaucrats).
[1] https://www.marketplace.org/2015/05/19/americas-infrastructu... [2] John Oliver: https://www.youtube.com/watch?v=Wpzvaqypav8
It's fair to question things, especially if they don't make sense to you and even if acknowledged authorities are behind them. However, (1) something that you may question is not necessarily something I may question, and (2) questioning may be a waste of time.
If a paper that says mixing red and blue paint makes green paint has a thousand citations, perhaps you don't need to question it because others already have. If you can't reproduce it, the simplest thing to do is ask an expert who says it is possible to do it.
The cost of the experimentation is people wondering what product they'll discontinue next and whether it'll be one that _they_ rely on. If you find yourself asking this often enough, you'll probably start moving out of the Google ecosystem. How is this good for Google?
Yes, I understand that products need to pay for themselves, but Google keeps drawing people into services that they then shut down. It's frustrating for users and damaging to Google. What's the cost of the damage to their reputation?
You may be right, but how exactly is someone meant to make an informed decision when they don't know what their TV is doing? It's unreasonable to expect the average person on the street to be an expert on the subject and to have fully researched everything before walking into a store, so if the TV's packaging doesn't say anything about the subject, how do they learn?
> However, to remain price competitive with the other TVs on the shelf in WalMart, they need to rely on ad revenue.
Which other TVs are you referring to? And is this really the case or are you speculating? Surely a company the size of Samsung can be competitive without having to resort to this sort of activity?
It's a good illustration of why privacy is so complicated: most people wouldn't think that in buying a TV they're compromising their privacy because they don't know about ACR and such. The manufacturers, of course, know all about it, but it's not in their interest to share the information - specifically, to do so in a way that empowers the consumer to make an educated decision at purchase time. (Or am I wrong and they do in fact explain everything "on the box"? I haven't had to buy a TV in a long time.)
I like the metaphor and agree with this sentiment: "the problem of understanding what customer needs, as opposed to accepting what the customer is asking for".
A few points:
1. The customer has a say in the requirements. They are often the domain expert. Even if they have no expertise, they need to be regularly consulted otherwise you still run the risk of delivering software that no value to them.
2. Understanding the business and eliciting requirements is often beyond the ability and scope of the software developer. These are the skills of a business analyst. Of course, developers can and do have these skills, but it shouldn't be assumed that they do.
3. Proper business analysis may lead to a solution that doesn't involve custom software. The article doesn't seem to allow room for this.
4. Implementation is often important to the customer. Many won't be comfortable to leave everything "below the surface" to the software developer.
This is definitely an immensely aggressive hive. In my limited experience, even the ones I've seen opened up and worked on were not as bad as this.
What medical staff wear are masks that are effective at filtering out viruses. Read this [1] on the FDA site for a good explanation.
It's well established that there's a global shortage of masks. [2] They're made in China and they can only make so many because the manufacturing requires special equipment. [3]
[1] https://www.fda.gov/medical-devices/personal-protective-equi...
[2] https://theconversation.com/the-global-effort-to-tackle-the-...
[2] https://www.npr.org/sections/goatsandsoda/2020/03/16/8149292...
I don't imagine that these DIY masks should be used more than once (as is the case with most masks), so you'll probably need to make a lot of them.
[1] https://www.researchgate.net/publication/258525804_Testing_t... [2] "Should I wear a mask to protect myself?": https://www.who.int/news-room/q-a-detail/q-a-coronaviruses