Ask HN: I've been slacking off at Google for 6 years. How can I stop this?

Post by astura » Sun, Jan 05, 2020, 10:32 PM UTC

ec109685 wrote: post #159

pavlov wrote: post #42

I think you underestimate your value to the company. “All I do is copy code from the internal codebase and patch things together until they work” — this is exactly what established tech companies mostly need from their engineers. They want people with enough CS competence to not fuck things up while patching together new solutions from the institutional code soup that everyone knows how to navigate and review. If you…

You didn’t read his whole post. They’re bored. Their value to google is high enough to keep them employed but the job is beneath their capabilities. The failing for google is not providing this person a path to do more or at least understanding their ambition to do more.

Post by astura » Sun, Jan 05, 2020, 10:32 PM UTC

flavor8 wrote: post #161

goatherders wrote: post #50

You don't realize how good you have it: 1. you work for a company that is an excellent resume booster outside of the valley. I'm from central texas and most everyone I know in tech has worked at Dell and once complained how boring it was to work at Dell. The moment they decided to move away from Austin their Dell experience made them very hot commodities to non-Austin tech companies. Every day you stay at Google the…

> Every day you stay at Google the more valuable you become. Ehhh, to a point. Straight out of college and then (e.g.) 10 or 15 years at the same company says a lot about a person.

Post by sweeneyrod » Sun, Jan 05, 2020, 10:36 PM UTC

jcims wrote: post #157

not_kurt_godel wrote: post #102

Earlier quoted context omitted.

While I agree that there are parts of software engineering that are merely 'tedious' rather than 'hard', there are definitely parts that are legitimately 'hard' too. Just because you've had a particular set of experiences that you've classified as tedious doesn't mean your perspective represents the totality of the industry.

The problem here is that 'hard' is dimensionless and relative. There are people in Australia right now storming the gates of hell with a shovel and a hose because that's the job they signed up for. If that type of work is on the spectrum, I can't really think of anything in software/systems engineering that's 'hard'.

Post by ChuckNorris89 » Sun, Jan 05, 2020, 10:36 PM UTC

dhuyrv wrote: post #130

You remind me myself a few years ago: a talented, but bored slacker who didn't see any point in investing any energy into that project. Turns out I was right: the project didn't go anywhere after I left and investing any extra time would be a clueless thing to do. So what's changed since then? Have I found meaning in work? No! I've become a professional slacker who knows all these psychological tricks, knows what bod…

Post by zzzcarrot » Sun, Jan 05, 2020, 10:37 PM UTC

reactspa wrote: post #150

dhuyrv wrote: post #130

You remind me myself a few years ago: a talented, but bored slacker who didn't see any point in investing any energy into that project. Turns out I was right: the project didn't go anywhere after I left and investing any extra time would be a clueless thing to do. So what's changed since then? Have I found meaning in work? No! I've become a professional slacker who knows all these psychological tricks, knows what bod…

This comment is pure gold. I found Scott Adams' recent books and Daniel Kahneman's work profoundly influential in changing my "observed personality" (i.e. the psychology I project to the world), and making me an order of magnitude more effective in dealing with work issues/co-workers. Please share a few books (or perhaps authors/youtubers) that you learned from. Thank you.