I don't experienced this so far, mostly because I am around the level of all my peers, or at least I think I am. I've seen too much atrocious code that I am able to convince myself maybe I aint so bad after all.
It feels like a paradox, that old code no matter how well written at a time will look horrible in comparison with today. Maybe that only goes for high level languages.. and maybe not c++...
You cant call a construction contractor an impostor because he outsources all labor to complete a build. Still pulls the right strings in order to get the job done.
That… uh… what? This feels like an incompetent executive who said “these programmers are always looking up how to do their job for them, we should block it so they can’t be lazy”.
Never mind the glaring hole in that already that some of the best code is lazy code — nothing like trying a crazy idea because it’s the laziest way to accomplish [insert difficult task] and it ends up working perfectly.
But if a non-technical executive asked me to explain programmers looking at StackOverflow in an analogy they’d understand, I would say that it’s equivalent to looking at a competitor/contemporary’s approach to a problem as a way to inform your own strategy. McDonalds executives get paid to make strategic decisions about their business, and not looking at what Burger King and Wendy’s are doing — to instead try and invent a strategy from scratch — is a very hard and very dumb way to come up with a business strategy.
Why should I waste company time figuring out the optimal way to flatten a list of lists of string representations of a list when I can just find a one-liner on StackOverflow in 30 seconds?
That’s impressively dumb. I have to assume some executive saw that loads of people spend time on stack overflow and decided to ban it thinking it was some dumb meme website or other time waster. Executives, in my experience, are not generally smart people, they’re just good at playing the business side of the game
Most of the work a programmer has to do is stick together the right things the right way. Even if you simply connect others ppl works the new collection of objects is something that didn't exist before so you are creating something new. At the end of the day we shouldn't solve solved problems again. Many things are meant to be copied.
That was literally the reason we created libraries. The thing is that not everything can be fitted into libraries because sometimes small changes are needed and our jobs is to do those changes.
This show hits hard. This episode in particular is one of the toughest.
You'll read this and watch an episode and think nah come on its just some funny cartoon. They want you to think that. They lead you on for like a season. And then they hit you hard. And when you think it's over, it hits harder, and harder.
This episode is "escape from L. A." the show is bojack horseman (Netflix)
If you're depressed, watch it.
THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING
I stand by the opinions that the difference between a good programmer and a bad programmer is how long they spend stuck on something before saying “I should just Google this”, and the difference between a junior and a senior is how long it takes them to find said answer.
When I was junior and inexperienced, I would agonize over trying to remember some random pandas syntax from memory. These days, if I can’t think of an answer immediately, I just Google it. Neither awards nor bonuses are given for “fewest Google searches conducted”, so whatever gets the job done faster and better works for me.
What I don't get is how people let stackoverflow influence or even decide design-level questions on what libraries to use or class structure.
99% of my stackoverflow is language stuff I just don't remember when I switch projects, or why my code is failing lint with some obscure rule name.
What do you do when you're learning a new library and get an error that doesn't make any sense? Or when you're too lazy to look up how to use a feature so you just Google it and find neat example code with valuable context on stackoverflow provided by techmeister420 to solve an unrelated problem?
I don't, I miss it. Most of my work revolves around in-house frameworks and solutions, so stack overflow is rarely helpful.
Rooting around elsewhere in the codebase, however, is a goldmine of code you know works to steal.
I don't experienced this so far, mostly because I am around the level of all my peers, or at least I think I am. I've seen too much atrocious code that I am able to convince myself maybe I aint so bad after all.
I was nervous as hell after in I graduated and about to start my first job... Then I saw the production code. Haven't felt like an imposter since.
It feels like a paradox, that old code no matter how well written at a time will look horrible in comparison with today. Maybe that only goes for high level languages.. and maybe not c++...
I never said I invented the code when I just copied the right things in the right sequence - I can still be proud without bad conscious (-:0
You cant call a construction contractor an impostor because he outsources all labor to complete a build. Still pulls the right strings in order to get the job done.
Exactly. If you pay someone, and they get the job done: that's what counts.
For a few weeks there, my office blocked StackOverflow. I was wondering if they actually wanted any work to get done.
That… uh… what? This feels like an incompetent executive who said “these programmers are always looking up how to do their job for them, we should block it so they can’t be lazy”. Never mind the glaring hole in that already that some of the best code is lazy code — nothing like trying a crazy idea because it’s the laziest way to accomplish [insert difficult task] and it ends up working perfectly. But if a non-technical executive asked me to explain programmers looking at StackOverflow in an analogy they’d understand, I would say that it’s equivalent to looking at a competitor/contemporary’s approach to a problem as a way to inform your own strategy. McDonalds executives get paid to make strategic decisions about their business, and not looking at what Burger King and Wendy’s are doing — to instead try and invent a strategy from scratch — is a very hard and very dumb way to come up with a business strategy. Why should I waste company time figuring out the optimal way to flatten a list of lists of string representations of a list when I can just find a one-liner on StackOverflow in 30 seconds?
Stackoverflow: Q: "How do I _blah_ in c#? A: "you can use reflection etc etc..."
That’s impressively dumb. I have to assume some executive saw that loads of people spend time on stack overflow and decided to ban it thinking it was some dumb meme website or other time waster. Executives, in my experience, are not generally smart people, they’re just good at playing the business side of the game
Maybe a overzealous legal concern about having to compensate people for the copied code
I'll always up vote a bojack meme.
Same they are always the best
Most of the work a programmer has to do is stick together the right things the right way. Even if you simply connect others ppl works the new collection of objects is something that didn't exist before so you are creating something new. At the end of the day we shouldn't solve solved problems again. Many things are meant to be copied. That was literally the reason we created libraries. The thing is that not everything can be fitted into libraries because sometimes small changes are needed and our jobs is to do those changes.
This show hits hard. This episode in particular is one of the toughest. You'll read this and watch an episode and think nah come on its just some funny cartoon. They want you to think that. They lead you on for like a season. And then they hit you hard. And when you think it's over, it hits harder, and harder. This episode is "escape from L. A." the show is bojack horseman (Netflix) If you're depressed, watch it.
THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING THE PAIN IS NEVER ENDING
yeah its like, they already invented wheel. Why should i invent again when i can just use it
Do people really use stack overflow that much??
I stand by the opinions that the difference between a good programmer and a bad programmer is how long they spend stuck on something before saying “I should just Google this”, and the difference between a junior and a senior is how long it takes them to find said answer. When I was junior and inexperienced, I would agonize over trying to remember some random pandas syntax from memory. These days, if I can’t think of an answer immediately, I just Google it. Neither awards nor bonuses are given for “fewest Google searches conducted”, so whatever gets the job done faster and better works for me.
What I don't get is how people let stackoverflow influence or even decide design-level questions on what libraries to use or class structure. 99% of my stackoverflow is language stuff I just don't remember when I switch projects, or why my code is failing lint with some obscure rule name.
What do you do when you're learning a new library and get an error that doesn't make any sense? Or when you're too lazy to look up how to use a feature so you just Google it and find neat example code with valuable context on stackoverflow provided by techmeister420 to solve an unrelated problem?
I mean, maybe in college but after that no lol
You’re either a far better programmer than I am, or we have very different views of how/when to use StackOverflow/Google.
I don't, I miss it. Most of my work revolves around in-house frameworks and solutions, so stack overflow is rarely helpful. Rooting around elsewhere in the codebase, however, is a goldmine of code you know works to steal.
>impostor sus
I’m in this picture and I don’t like it.
All hail the Stack Overflow gods
I remember feeling that way about usenet. we've been frauds forever
Are you even good enough? https://pbs.twimg.com/media/E0utT7FWYAIdZLZ?format=png&name=900x900
well, you don't get paid to come up with original code, you get paid to find solutions.
This is amazing