How to feel engaged at work: a software engineer's guide • Hacker News Board

Re: How to feel engaged at work: a software engineer's guide

#181

Post by throw827474737 » Fri, May 20, 2022, 8:59 PM UTC

corrral wrote: post #121

throw827474737 wrote: post #108

Earlier quoted context omitted.

Huh, for what hide that? Would they proactively fire you? Here, it is always joked that intentionally giving those signals is the trick to support getting the desired pay raise.. some years ago even saw one guy pulling that off.

The trouble is if you're just idly searching a bit and aren't in a hurry, you might not want your current employer (or co-workers) to start planning to be rid of you soon. At the very least, it might make things awkward.

Its strange but I never worked or can imagine working in such an environment.

When coworkers would learn I'm searching for something else they either understand me and/or try to persuade me not to jump ship. Why should they, lol? And if I go they wish me all the best as I would do to them.

And actually just the same for bosses?

Re: How to feel engaged at work: a software engineer's guide

#182

Post by PeterisP » Sat, May 21, 2022, 8:23 PM UTC

alkonaut wrote: post #27

My motto is: I don't want to work on a CRUD app. I want computer science to actually be part of what I do. Not parsing and validation and deployments and migrations. But finding these jobs where actual "what you do with the data" is the majority work, and the fluff around it is a minority, is HARD and such jobs seem to be more far between. Perhaps because the software jobs that used to be difficult algorithmic proble…

IMHO those jobs are exceedingly rare, because all the roles with difficult algorithmic problems seem to have the grind around them as the majority of work that needs to be done. You mention data science, well, if you're doing serious data analytics two thirds or more of your time is converting data from one form to another and handling its flow; if you're doing cutting edge AI research, most of your time is devoted to 'plumbing' required to run these experiments, and only a minority to the algorithms you're researching. The same is pretty much everywhere, so if you find a job where that does not apply, that's quite exceptional.

Re: How to feel engaged at work: a software engineer's guide

#183

Post by ohwellhere » Tue, May 24, 2022, 2:15 PM UTC

lupire wrote: post #44

ohwellhere wrote: post #41

Here's my advice on the same topic after living through burnout and "blah" several times: Make your job the union of what you're interested in and what is valuable to the business. You have to know what is valuable to the business; that knowledge is challenging to acquire but will _always_ help you in any role. It has to be true and verified with stakeholders, not your gut. There are soft skills involved here. You al…

Do you mean intersection, not union? Union is kind of a fantasy, getting paid to have your own fun.

Yes, I did mean intersection, thank you.