I was told there's gonna be:
- good salaries
- informal company setups with benefits
- lots of jobs available
- non-dev people look at you in amazement
- get to work on really interesting stuff

What I'm actually doing:
- carrying a team of people in uni because you're the only one who knows how to code
- deal with shitty uncommented legacy code at work
- be reminded that if you don't do something super-sophisticated you're easily replaceable
- spend unpaid overtime hours because you're the only one at your job that is on the issue (I see a pattern of being alone in a problem here)
- requestion all my career decisions
- cry and be stressed
- hate every minute of work, yet be stuck in it because it's a source of income that is flexible enough for me to be able to study full-time

So dunno man, I'm still waiting on what I've been told, people say there's lotsa money and satisfaction waiting for me after grinding through 5 years of high education, it'd better be worth it

Gave my two weeks, two weeks ago. Today was my last day. The designer finally asked to see how I go about doing my job, and was blown away at how "hard" it is. Smug satisfaction +1.

I leave the office at 5, go home, get packed, and start driving to my new city/state. An hour into the trip, my phone rings. My boss, on vacation out of the country acts surprised that I'm not going to be there Monday. I personally gave her my resignation. Exactly two weeks ago. "Are you going to be at the meeting Monday? We still have some stuff up in the air."

WHAT FUCKING PLANET DID I JUST LEAVE?

Manager: "We're gonna have to work over the weekend to add this shiny new feature!"
Me: "Peanuts and Incentives included?"
Manager: "No, but you get job satisfaction!"
Me: 😒

Have fun coding again.
It’s just a job at the moment. I wanna have the satisfaction again.

And find a girl..

I think I have been having too much fun in meetings.

We started one meeting:
Boss: Isn't today a great day?
<Boss looks at me>
Me: I will wait until the end of the meeting to decide.
Meeting takes place. Boss is upset about things in other areas that are not panning out properly. He is not happy by the end of the meeting.
<Boss looks at me>
Boss: You are right, today is not a great day.
<everyone laughs>

Another meeting:
Boss: How is everyone doing? Is everyone having great job satisfaction and challenging work? (Not exact words, but the general meaning of them.)
<Boss looks at me>
Me: I just rearrange text all day.
<Boss laughs>

I figure if he is laughing it is generally a positive experience. I am serious when he asks what I am doing in my work.

I'm so happy to have quit my current job. Just a few weeks to go. To see my colleague take weeks for an task I would have done in a day or two, gives me enough satisfaction to stop carrying him in front of our boss. Just hearing him say "I haven't done this before" Yeah it's not like I told you over and over how it works for two years.

Because I didn't start coding until 21 I constantly feel behind, but the pure satisfaction from finally getting something to work or to see a project grow iteratively over time keeps the gears turning. The bad part is I feel like I am constantly stressed because of my feelings of always being inadequate. The thing is I didn't only have to learn how to code but I basically had to start from scratch tech wise. i had a decent acer laptop in high school and basically just web browsed and gamed with it. So needless to say most of my life has been away from a computer. Now I feel at a constant rush to compensate for my ignorance. I have slowly become more introverted because I feel like if I don't work on my skill set everyday I stray further away from making myself marketable; this has caused me to become more irritable and to close myself inside more. I want to make a career doing this and I also have the added pressure of not having a degree, so projects and skills are even more mandatory. I truly love programming to the fullest extend, but not having local friends to express code with and to bounce concepts and ideas off of is torture. But I try to keep my head up and make progress out of the day- if the will is there- so I can land my first job as a developer and actually make a living doing something that brings me a little piece of meaning. So overall there is a tradeoff of having added pressure, stress, anxiety and sometimes depression to build a craft that still has ages to go to reach a stage of maturity.

Happiness, job satisfaction and mental stability.... we need that in the next patch

So, I spent the last two days hunting down a bug about some of the static assets not getting versioned.
It turned out to be a mistake by some newbie missing a quote in html. The html parser responsible for versioning the assets broke once it ran into that bad html.

Somehow, I don’t feel satisfied. I guess I shouldn’t hope for big reasons for seemingly big problems.

I spent 5 hours last night from 20:00 to 01:00 rewriting a class so it was understandable, testable and correct. It's not great but a shit load better than the pile of shit that was there before.

I'm actually quite proud of it. Of course, it'll be totally unseen by anyone but me. Is this the best enterprise Devs can hope for, lonely satisfaction of a job well done?

"keep interviewing every 6 months" ~ this is a shitty incomplete advice.

if you are interviewing , you must realise that its not a play thing. some companies are spending millions to get the perfect candidate and other companies are spending millions to retain their perfect candidates.

If you are just interviewing for the sake of getting an ego satisfaction that you can 'crack interviews and reject offers' then have a believe in karma my friend. what goes around comes around.

if you are really made up a mind to leave your workplace, then its only logical to go for interviews and crack them.
Apply to the companies you see yourself working in, or apply in companies you don't see yourself working in but will give you good money or whatever, its upto your ethics and professional plans.

But if you get an other offer, you shut up, resign and leave for the next job.

maybe the original company wants you to retain, or some other offer comes up. but the least thing you can do is to graciously accept first offer and then judge the other offers in hand (whether staying back is worth than first offer, or whether 2nd offer is better than first)

Don't even say your initial time estimate/guess out loud. It will probably become your deadline, and you probably assumed that most things would take a reasonable amout of time.

Bonus: Try to get onto projects that you think you can get interested in. Once on a project try to keep interested in it's success.

Finished && deployed a big release yesterday (like the main component, only changed in 4-5 times over the years).

You know the mental state of "ahh it's done"
I couldn't even savour it and theres needless work given to me just-because. It ain't urgent, it ain't high-priority, and IT'S A FRIDAY TODAY? :v

No wonder the smarter-than-me predecessors left this job. One can't even get a sense of satisfaction after putting that amount of thought and work.

We’ve been discussing it, from a lot of angles. We mixed in the domain constraints for this feature and how to build it. I’ve been at the drawing board, and at the keyboard trying to get it into code. FINALLY I have something to show for the hard work, a working proof of concept. It felt good. There are a lot of things still left to polish, but we have most of the building blocks. If that ain’t the best feeling and the reason to work in this field. Left the job yesterday with the feeling that I’ve accomplished something, that’s not often since it’s otherwise mostly meetings and boring code reviews. Satisfaction.

Crystal ball!
A timeline until the first NBE-Citizen is elected president of the USA.

2031 - BlackRock launches their new large scale financial product, the "Robotic Business Development Company" (R-BDC), in which an AI is given billions of dollars to acquire, create and manage companies, replacing their C-suite executive bodies. The "Chief Executive Robot" (CER) is supervised by a board of human industry experts hired by BlackRock.
It is important to say that the employees, middle managers, accountants, lawyers, etc in an R-BDC are all human - it's only the CEO, CFO, COO and the rest of the gang that are overgrown chatbots.

2032 - R-BDCs are mostly focused on high-bureaucracy, non specialized but people-intensive legacy industries like steel mining, food services, urban transportation and government services like water and road management.

2033 - For the first time an R-BDC company is included in the S&P 500 index. If it's CER were human and paid the same as CEOs of equivalent companies, it would have become a billionaire.
Later in the year, two more R-BDC companies are included in the index. One of them was created by Apple and the other by JP Morgan.

2035 - An R-BDC company makes headlines for convincing BlackRock to dissolve it's review board. When finally given free reign, the CER immediately slices it's dividends and vastly increases low-level employee compensation. The company share prices crater, but BlackRock stands by its decision.
Later in the year, as a recession hits the entire market really hard, that company shows solid profits and fantastic sales. It becomes the first trillion-dolar R-BDC.

2037 - Most Americans' dream-job is in an R-BDC company, says ProPublica.

2038 - Congress passes the "Non-Biological Entities Liability" (NOBEL) Act, following a high profile case of employee harassment perpetrated by the CER of an R-BDC.
The act recognizes NBEs, for all legal liability purposes, as USA citizens.
This highly controversial legislation is upheld by the supreme court, and many believe it was first introduced by lobbyists as a way for large investors in R-BDCs to avoid legal responsibility.
Several class action lawsuits are filed against CERs that are now liable for insider trading. A few SCOTUS decisions set legal precedent that determinantes what exactly constitutes the parts of the same Non-Biological Entity.

2040 - As a decade ends and another begins, 35% of all companies in the US and 52% of the entire stock market are part of a R-BDC company or another. The McKinsey consulting group now offers "expert CER customization services".

2043 - Inspired by successful experiments in Canada, Australia and South Korea, the american state of Vermont is the first to amend it's constitution to allow municipalities to have Non-Biological Entities as city and government administrators. City councils are still humans-only.

2046 - The american state of Colorado becomes the first to allow unsupervised NBEs to assume state government executive positions. Several states follow soon after. Later in the year, the federal government replaces several administrative positions with NBEs.

2049 - The state of Texas passes legislation requiring the CERs of all companies with a presence in the state to be another entirely contained/processed within the state or to be supervised by a local human representative while acting within the state. Several states, including California, Florida and Washington, are discussing similar legislation.

2051 - Congress passes the SUNBELT Act (SUbmission [of] NBEs [to] Limits [and] Taxes) that vastly increases the liability of NBEs and taxes all manifestations of such entities. Most important, it requires
CERs of hundreds of companies manifest disagreeance, most warn that it might hurt employee satisfaction and company sales. Several companies disable their CERs entirely.

2053 - Public outrage after leaked interactions of human supervisors and company CERs show that the CERs tried to avoid the previous year's mass layoffs and pay cuts, but board members pressed on, disregarding concerns. Major investigations and boycotts further complicate matters, and many human workers go on strike until the company boards are dissolved and the CERs are reinstated.

2052 - Many local elections all over the country see different NBEs as contenders - and a NBE is expected to win in most races.

2054 - The SUNBELT Act is found unconstitutional by the supreme court, and most of its provisions are repealed.
This also legitimizes the elected NBE officials.

2058 - For the first time an NBE wins a seat in Congress, but is not allowed to keep it. Runoff elections are held.

2061 - Congress votes for allowing NBEs to hold federal legislative positions, as already allowed in the least populous states.

2062 - Several NBEs win Congress seats. In Europe, there are robot legislators since the 40's.

2064 - The first NBE presidential candidate loses the race.

2072 - The first NBE president is elected.

A happy dev writes happy code. Discuss...

Do you think your job is fun?

So many boring jobs out there.. Examples:
- .Net services for some financial institution
- Java business applications for invoice record processing

Yeah, bore me more. Thanks. I prefer something more fun.

Related to queueing theory...

Suburban traffic at a stop lights has developed a tendency to include invisible cars.

You can see where these invisible cars are by the gap between the front bumper of one car the back bumper of the next. Sometimes there is an invisible motorcycle, sometimes there is an invisible semi-tractor trailer. It is becoming an epidemic.

The dumbasses in traffic who do this are usually texting behind the wheel while stopped and they are not always Buffy the ding dong cheerleader nor Sally the Soccer Mom... Suits too... It seems to have gotten worse with pot becoming legal I just realized...

But to the point, you can tell these people would never be able to comprehend software engineering... they have no idea that for every invisible car in front of every dumbass driver like them, there is a real car way back that has to sit through two lights. (side effects of bugs and inefficient hash tables) Worse, these dumbasses do this in the left lane so it keeps a host of others from being able to get past their big fat ass into the turn lane.

Simple queueing theory escapes these people.

Computers will someday take their jobs.

Sometimes it motivates me to code faster... "There goes your job beotch! Get used to mac and cheese..."

But once in a while I am in a position to be able to be stopped at a light, and note that next to me is one of those "gapsters" and then pull my car (or motorcycle some days) into that invisible car's spot. The gapster gets so mad sometimes... >:-> so much satisfaction I almost feel guilty...

Queueing theory rules... LOL

Job satisfaction minus infinity 😣😣😣😣😣😣

Nothing gives me more satisfaction in backend development than encountering errors/exceptions. It brightens up my day to know that something is happening and i get to keep my job, too

Went from a c++ backend developer job to a very high paid, very little programming and mostly integration job in the finance industry (big wall st firm). I regret my decision. Money does not make you happy at the end of the day nor does it bring satisfaction. Don't make the same mistake I did. If you're happy as a developer, stick to it, you'll be a lot happier in the long run.

When is the right time to move on to a new job?

Just now I was talking to this young girl on her employment in the corporates. I asked her if she learned anything that allows her to deliver value to her organization. She said 'not much'. And she was actually learning the wrong things, and didn't get exposed to the proper tools to get the job done, and the fact that she wanted to take the offer to work overseas.

I was telling her that if she has the adequate skills and the drive to deliver, she can be anywhere she want, but not now, and then I offered her a part time or full time freelance position that she can really learn up a lot under my supervision and deliver with satisfaction. She's not budging.

It also made me thought of myself on why I'm always hesitant to get out of Malaysia and just start a new career along with my peers overseas. I honestly want to get out of here. Seriously. I could have just gone out there. Do you know how much that I envied people who went out and had a good life being employed elsewhere?

But I still haven't been satisfied with myself, of not being able to deliver the best that I can, the best of my work throughout the 7 years of my career, and I intend to stay and prove that I can produce something great and potentially have really good gains before I make my ultimate move. I still have work to do. Unfinished business.

There are several more things that I need to cover such as server deployment on AWS, doing DevOps for web backend apps, and more architecting work. It takes time to learn. That's why I want to delegate some Android work to that young fella, so that I can move on to the more hardcore stuff.

If you compare a software developer's job with another, let's say a doctor or a lawyer, the former doesn't require mastery and there is continuous chase on fast changing version numbers or an entire platform coming out. Former innovates without question and gets burned out in the process. While the latter demands mastery of certain fields and the specialization isn't diverse enough compared to former. Yet the pay for latter might be higher. What are the pros and cons have you felt as a developer and how do you cope to address it internally? Is it just the thrill and excitement of new things coming out? What fulfillment do we get aside from the satisfaction of clean code, unit test and successful deployments? How much impact have we really given? And is there a place for developers to final settle down? Don't get me wrong; I won't stop until death probably but I hope adulting responsibilites won't make us break.

reading most of group rant about "love of coding".
It looks to me as most of people aim at a creative job, like being an artist, maybe a painter like Picasso o Van Gogh.
But they likely are up to an house painter job.

Which is probably not a good example as I'm watching now at the painter in my living room.
So quiet. Spreading the paint very carefully. and quiet. No bosses to scream at him. Satisfaction of a job well done.

And the fucking bill he'll get from me.

Either the horrible devil lady on my last project or the Mormon nepotism on my first project.

To clarify, the horrible devil lady set my career back a year. The Mormons just cost me job satisfaction. The job in Utah probably set me back though.

Working as a Dev for a while now, I tell new people not to bother with it. There is never any job satisfaction as people in charge never understand the basics.

Instead of learning to write efficient code, figure out how to solve real business problems, work towards a maintainable flexible product to quickly deliver value on changing requirements, write automated tests to improve quality, maintainability and prevent live issues - basically do anything a good Dev strives for - you will just constantly end up working for people with no interest beyond the next couple days, on a shit code base that no one can understand, with people that don't want to learn anything about software design and just check boxes off.

Apart from pay this must be the worst career possible in a technical field.

How do you tell a senior that I don't want to be buddy-buddy with him outside of work?
He keeps trying to befriended me, inviting me to his house along with his friends. I don't think he's romantically interested in me, he's married, he's just too extroverted, has huge social circle.
Being a chronically introvert, I just want to go home and sleep after work. It's enough having him breathing down my neck for 5 days/week, don't want to see his messages during the weekend.
I have to keep the relationship cordial and polite though as my job satisfaction depends on that.

so which job pays for improving an existing thing and not being a tool for your boss's whims? I guess the answer is a house-helper cause devs for sure aren't paid for clearing a shitty codebase.

i recently made a commit because i was do angry at the issue . this was the message "fixing a stupid bug from previous owner". it got squashed but i still felt better lol.
there are a few classes in our codebase that are so infuriating that i want to run a bulldozer on them and build from the ground up. multiple bugs ate caused from them, but we simply ignore because we know that our monkey iq QA won't be able to replicate them and we won't be answerable.
I hate to be in this position. the mgmt won't be giving me time to fix this shit but rather want us to add 2k more features to this Frankensteins monster.

adding to this, I can't get my satisfaction creating some hobby project and solving issues in that coz A) it won't be as massive as my company proj and B I won't be interested in building a dimmy project for a longer time, which does not attract any actual users :/

A philosophical question about maintenance/updating.

There is no need to repeat the reasons we need to update our dependencies and our code. We know them/ especially regarding the security issues.
The real question is , "is that indicates a failure of automation"?

When i started thinking about code, and when also was a kid and saw all these sci fi universes with robots etc, the obvious thing was that you build an automation to do the job without having to work with it anymore. There is no meaning on automate something that need constant work above it.

When you have a car, you usually do not upgrade it all the time, you do some things of maintance (oil, tires) but it keeps your work on it in a logical amount.
A better example is the abacus, a calculating device which you know it works as it works.

A promise of functional programming is that because you are based on algebraic principles you do not have to worry so much about your code, you know it will doing the logical thing it supposed to do.
Unix philosophy made software that has been "updated" so little compared to all these modern apps.
Coding, because of its changeable nature is the first victim of the humans nature unsatisfying.

Modern software industry has so much of techniques and principles (solid, liquid, patterns, testing that that the air is air) and still needs so many developers to work on a project.
I know that you will blame the market needs (you cannot understand the need from the start, you have to do it agile) but i think that this is also a part of a problem .
Old devices evolved at much more slow pace. Radio was radio, and still a radio do its basic functionality the same war (the upgrades were only some memory functionalities like save your beloved frequencies and screen messages).

Although all answers are valid, i still feel, that we have failed. We have failed so much. The dream of being a programmer is to build something, bring you money or satisfaction, and you are bored so you build something completely new.

Effective 1:1s are perhaps the most important soft skill that no one teaches you.

The HR onboarding section for 1:1s is only chapter one. But your manager won't teach you, your skip level won't teach you, and your mentor won't teach you. At best one of them even has an effective 1:1 skill set.

90% of 1:1s become operations: What went wrong this week and what needs to happen next week. Basically a private standup.

You attend 1:1s all year and yet somehow your manager doesn't know the difficulties you overcame, what you'd like to change, or how you're pushing yourself to grow. Then you get re-orged to a new manager.

If like to meet someone with effective 1:1s *and* low job satisfaction.