8 ms·
I don't know. I've been writing c# for years and I still go to SO for things. Sometimes it's even stuff I should know, like creating a text file. However I don'
by S_A_P 11y ago
I don't know. I've been writing c# for years and I still go to SO for things. Sometimes it's even stuff I should know, like creating a text file. However I don't do some of these tasks often enough to remember by heart and it's not an exciting problem to figure out so I go for SO. I don't see a problem with that at all. I also don't get the sentiment that you're not a real coder if you use SO and copy paste code. I don't always have the luxury to figure out which sorting algorithm is fastest for the dataset I'm working with. Sometimes I have to meet a deadline. A great developer is one who writes easy to parse code that is as bug free as possible in the alotted time frame.
There are times when it's important to do some r&d and learn more, but there are also times when you need to ship. It really depends on what the task is. You can't paint the whole thing with broad strokes.
- nilliams 11y agoWay I read it the overuse of SO (along with C&P programming) thing was just one example/potential symptom -- he wasn't making a broad generalisation that all SO usage is bad.
- thebouv 11y agoI tell employers and employees and co-workers: I'm a good programmer, I'm a phenomenal Googler. I don't have to memorize the best sorting algorithms or how to create a text file in every language I touch. I know how to problem solve, choose the correct tools and search for guidance (note: that doesn't mean straight c&p always but could if it is appropriate) on things that get sticky.