On a related note I've found docker for windows so buggy at times.
Docker for Windows won't run if Razer Synapse driver management tool is running
111–120 of 191 posts
Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#112Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#113I think it would be a great addition for StackOverflow to have a sort of report button for dangerous code. Take for example libcurl (thus, implementation in PHP, Ruby, Go, etc). There are sooo many posts with cURL example code where CURLOPT_SSL_VERIFYPEER is disabled. These are often answers with thousands of upvotes, that have been there for years. Inexperienced developers copy/paste this code into production withou…
You can report the errors in comments, and develop a habit of looking in the comments for reports of dangerous code.
Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#114Earlier quoted context omitted.
> read API docs for anything I’m unfamiliar with One of the differences i've noticed between myself and some of the junior devs i've worked with. I would usually use the official docs as my first resource, and they would use stack overflow instead.
It's a common use-case that the best docs are provided on some dude's gist or blogpost. Devs and orgs update the code but don't bother with the forgotten docs. It happens all the time.
Namely, "some dude's gist or blogpost [or stack overflow answer]" not getting updated. Not just that they didn't but that they couldn't.
Unsurprisingly, which you should rely on depends heavily on context. It takes experience and patience to figure out which one is correct based on circumstances.
Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#115Earlier quoted context omitted.
I agree: Recently I found an interesting snippet of C code which was using an sprintf to write a string into a char array. Unfortunately, it contained an off-by-one error where the null terminator would be written outside the char. I proposed to fix the answer, but for incomprehensible reasons the edit was rejected (!)
See https://meta.stackexchange.com/a/164449/192171 If an answer is factually wrong (as opposed to just poorly formatted or missing a few details), generally its better to leave a comment rather than try to edit it. I agree its not ideal, but suggested edits go into a site-wide review queue, so not everyone reviewing them will necessarily be familiar with C. This makes edit reviews a poor tool for evaluating factual c…
Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#116Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#117Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#118Docker for Windows has had a fundamental Dns[1] bug since April of last year, I've been forced to run v2.0.0.3 for months now to ensure yum repos resolve inside AmazonLinux containers. Truly a second class platform. [1]: https://github.com/docker/for-win/issues/3810
>Truly a second class platform.
Now maybe some Windows users will see how Linux users have felt for over 2 decades.
Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#119Ha, stackoverflow is a great tool, but... the more answers I see on an area I’m experienced in, the more I realize how wrong they can be. Sure, the answer usually gets the job done, but everything else about it might not be right. If I need to use stackoverflow, these days I make sure I do a few things: - read a number of answers, comments included. Just because an answer is accepted doesn’t mean it’s the best one -…
I'll suggest one more addition to this (and any code you take from the internet): put a comment in saying where you got the idea from (with a link). It can help the next guy out a lot. And you might be the next guy.
Re: Docker for Windows won't run if Razer Synapse driver management tool is running
#120Do not copy/paste code from stackoverflow. SO is not a code writing service. It is a problem solving/question answering service. Any code you see in the answers should be takes as reference only. If you don't understand what the code does, re-read the answer, check the documentation, understand and then write your own code. What happened here is such a stupidly trivial bug. If someone only took a second glance at this code it would be blindingly obvious what is going on here. I saw it as soon as I looked at the SO code sample and I don't even write C#. Do people at Docker even do code reviews?
Also, when I write answers in SO, I try (not 100% of the time, but I do try) to make my code generic, so it solves the problem the user is having, but does not include any specifics from the question. I suggest you all do the same.
P.S. I know that this rant of mine is rather idealistic. Nobody is going to stop copy/pasting code and these things will keep happening. But writing this was therapeutic.