271–280 of 733 posts
Earlier quoted context omitted.
[flagged]
>most people stuck in unhappy marriages are men That is wildly untrue. The research on whether men or women are more satisfied in their marriages shows that they have about the same levels of satisfaction. For example: https://onlinelibrary.wiley.com/doi/10.1111/jomf.12077 Not really sure why the demographics of philosophers effects the impact of the statement. Most philosophers are white, would it have been more imp…
> I have come to a realization that I don't really enjoy Software Engineering(& the processes that it comes with) but I do love programming & solving problems. I can almost guarantee that you’re just at the wrong company. Some software companies can turn even the simplest tasks into a grueling series of processes, endless meetings, and joint work across a big number of “stakeholders”. These companies will take the jo…
1000x times this. It's a weird thing our profession. There's a horrible but apt (misogynistic even) saying. Happily married men are happy husbands - Unhappily married men are great philosophers. I really feel agile has killed the happiness of our industry because it's met with a lot of back and forth, meetings, rituals, and meta-work and not actual productivity (If agile is done well though it can be amazing but that…
Agile was created to beat exactly those things that you are mentioning. Then Agile became big, enterprise became aware of it and smothered it with their rituals, processes and bureaucracy. And now we're back where we started again.
I've found that if I'm in the software department, the performance review and metrics and overall culture lean towards "how good of a software developer/engineer are you?" as opposed to "how good are you at solving the business's problem."
That said, it's tough to make progress outside of the software org. Personally I'm doing a masters in math right now and thinking about a PhD in it as well, because I need skills outside of software in order to be able to make programming part of my job but not my career.
Earlier quoted context omitted.
There's a slight implication because it only covers men that women are the source of unhappiness (e.g. the nagging wife trope), but I agree it's trivial and likely unintentional. Agree with sibling, just as applicable as "happy married people are happy partners, unhappily married people are great philosophers".
[flagged]
Earlier quoted context omitted.
[flagged]
> Was Aristotle misogynistic? Yes. https://en.wikipedia.org/wiki/Aristotle%27s_views_on_women
> Among women's differences from men were that they were, in his view, more impulsive, more compassionate, more complaining, and more deceptive. He gave the same weight to women's happiness as to men's, and in his Rhetoric stated that society could not be happy unless women were happy too.
And the modern psychology:
https://www.bbc.com/future/article/20161011-do-men-and-women...
I think you’re really stretching the word “misogyny” when you’re using it for people who accurately describe reality and view male and female well-being as equally important for society.
You're in the wrong job.
A developer has to keep on top of tech industry or they'll become a dinosaur early and find trouble getting work after you lose your job (just ask Java devs who steadfastly refuse to move off anything but Java 8).
Firefighting issues ("incidence response") due to lack of software engineering is not enjoyable when you've just manually deployed to production from your desktop computer and put the wrong build on that has migrated a prod db schema used by millions of people to one that isn't compatible with the rollback version of the software. And you'll be fixing it across your holiday and weekends.
There's a reason these processes are in place - and its to stop the wild west cowboyisms bringing down the company.
As other people suggested you may consider switching to a green field project. Usually when there is a new product to write, you don't have a legacy code baggage and business is usually pushing for fast delivery and iteration. There is a lot of freedom, as long as you can deliver a working solution. Startup would be a good choice about 3 years ago, today I would advise to be more careful when changing jobs now.
alternatively, consider that it's just a minor component of programming in general: it doesn't deserve to be called a field: just like "using sandpaper" is just one of many activities within the profession of carpentry.
we do SE in order to program.
SRE/Devops person at a FAANG.