681–690 of 733 posts
Not everything in life has to be "fun". Sometimes important things aren't fun to do, but we do them because they are important. Seeking endless fun is vain and meaningless. Doing meaningful work requires discipline and perseverance, it won't always be fun but it'll be more satisfying.
> What are some good jobs for a person like this? Academia, using programming in another science. You can program all you want there but you never have to do anything like software engineering.
How do you find and apply for jobs like this. Bug hunting mercenary would be my ideal job. Not sure how to find jobs that have that need.
It sounds like you'd enjoy academic/research programming. Programming for business does not seem to suit you.
Yep. I'm sure there are comlabies out there that don't suck, but I haven't found them yet.
Earlier quoted context omitted.
That's called code review, you don't need any "agile" for it. Agile is used to micromanage engineers to push out crap features, optimizing for the two week return, with poor results in the longer term. The people running amok are layman "agile coaches", "business analysts" and "product owners". While poor engineers are prevented from doing necessary non-feature work.
> Agile is used to micromanage engineers to push out crap features, optimizing for the two week return, with poor results in the longer term More correctly, organizations micromanage engineers to push out crap features, optimizing for the two week return, with poor results in the longer term, and call it 'agile'. They wouldn't know the nature agile if it fell on their heads.
Earlier quoted context omitted.
Yeah, one of the 1000-person companies had a dev whole-own a critical microservice. Changing it was always a battle, because the owner was very critical of anyone touching 'his' service. Large companies aren't immune, but due to eng specs and collaboration baked into development, its less likely for this to happen.
It looks management was a problem too, as "wholly owned" is a double-edged sword, especially if it's a microservice. Make sure you have solid metrics on your side to record problems with that microservice, document any delays caused my missing features, and eventually even non-technical management should get your point and start to apply pressure.
Usually management doesn't want to participate in these discussions, because they are more careful about retention (and stepping on toes). 1 engineer quitting is a 10% reduction in their workforce.
Earlier quoted context omitted.
There are plenty of layers at which it's misogynistic, but the most obvious one perhaps is that it wholly centers around the man in the relationship. Why must the wife be the source of the husband's unhappiness ("nagging wife" trope)? Why does he get to be the great philosopher if they're both unhappy? You can say "it's just a saying, it would be equally true with the roles reversed" -- but then, why aren't they? Sur…
The standard you've laid out proposes that any statement about a man's experience in a relationship is by definition misogynistic, because it's centers the man (and, of course, erases women). Do you stand by that? Additionally, consider that you are the one bringing the nagging wife trope into this: it's merely one of many possibile explanations and unhappy marriage.
Saying "I was in an unhappy marriage and it made me a great philosopher" would be fine. It's the generalization which is an issue here.