115 karma · joined January 22, 2020
I encounter this so often. It must be hard for some people to question a given design or requirement. Sometimes when someone asks for a solution to a problem, they don't actually want what they asked for they just want a solution to the problem.
This would put so much selective pressure on anyone lower on the totem pole compared to their superiors, it is sure to cast aside good talent for making the slightest mistake, but Apple makes good stuff so what do I know.
Secondly, I was a bit frustrated with the conclusion of the article.
> What can you do to acquire better product judgment? How might you recognise when someone has it? How might you develop taste?
I think this read needs a bit of stewing on those very questions, otherwise it's quite discouraging indeed. If you can't even define what good taste is, this advice kind of breaks down a bit for the average person.
Maybe a 202 Accepted code makes more sense
There are also windows machines that make it hard to replace things mind you.
That doesn't mean I wouldn't also use the best practices codes for authentication vs authorization etc. I say this loosely though because best practices are really just that. It's more important to maintain a level of consistency within your team or organization so you're all speaking the same language. It's nice to have a starting point like rest APIs (or something that resembles them) so you're not writing a completely new rulebook on standard stuff that other people have already figured out, you can focus more on the problems your team is trying to solve. Why not use a 409 when there's a conflict? Someone already solved that problem. You can still return whatever pretty error message you want.
Won't you just send up in those huge discussions you waste so much time on?
If you truly prefer chrome why not use a chromium browser that is not Google? (Brave for example)
Anyone understand the technical jargon here? I'm a bit lost.