241–250 of 754 posts
Earlier quoted context omitted.
That is not a Neruda poem. It is apocryphal. Pablo,ever the communist, would have never written such a piece of libertarian crap.I am surprised that such a fan of Neruda as you claim to be did not notice that.
Not surprised to see such a salty reply from a Neruda fan.
I'm having similar issues, and i think i found a way out: stop playing their game. Don't make enterprise software. Don't write unit tests. Don't accept pull requests. Simply write software for yourself and have fun doing it. Forget refactoring code into modules, just fucking code. Don't worry about deployment with k8s, just copy the Python script to your production folder and run it. Fuck all that shit about git bran…
When I was young, I loved being outside, camping, hiking, being in the forest, learning about plants and animals, foraging for berries and stuff. I ended up going to school for biology and ecosystems mangement. I worked on a few scientific studies, the stuff I actually liked, then ended up helping manage a long term research and education project. Suddenly, we were dealing more with money, government organizations other biologists. We ended up getting sucked into a bunch of politics, had our grant money and data held hostage by the government, dealt with shady corporations who didnt give a fuck. I watched lots of money get wasted on nothing on other projects simply to make companies look good while real problems went unaddressed and ignored.
Came to learn of the chain off command, the biologists that officially must sign off on work who do nothing but collect money for signing their name on a paper and tend to be in the pockets of mining companies, logging companies, the gas oil industries and again give no fucks outside getting that sweet pay cheque for writing their name on a paper. We were threatened with loss of funding after finding an endangered species on an active mine site and deciding to share the data publicly.
I just generally came to realize, that all the science and saving the world I'd wanted to do, didn't really matter to the people who funded this work or to governments in general and I became fairly jaded to it all. I seen renowned biologists steal grant money from volunteer organizations and shit like that. Hell I even met David Suzuki, turns out he's like any other celebrity, as soon as the camera's off the caring stops.
Reality just ended up being so different and souless compared do everything I'd learned in school. I just don't have any motivation to continue with it. Since then i've gone on to do other things, and I've found them a lot more fulfilling than that thing I thought I wanted to do and enjoyed as a child.
I'm having similar issues, and i think i found a way out: stop playing their game. Don't make enterprise software. Don't write unit tests. Don't accept pull requests. Simply write software for yourself and have fun doing it. Forget refactoring code into modules, just fucking code. Don't worry about deployment with k8s, just copy the Python script to your production folder and run it. Fuck all that shit about git bran…
No unit tests?? You should just recommend never running your code if that's where you're going.
Buuuuut... a lot of the personal projects I've worked on have zero unit tests. Maybe they have a couple of tests around a complicated algorithm, but mostly... no automated testing. What they do have though is a) version control, and b) a fast-iteration platform underneath them. They're also generally well factorered into small chunks.
As an example, I have a package that takes an org-mode file and extracts time entries to drive into time tracking software a client uses. Written in Lisp, zero tests. Every month I fire it up, look at the table of entries it's about to post, and hit "go". Looking at the table of entries provides two sanity checks: first, that I properly logged my hours that month (I'll occasionally forget to clock out for a weekend and rack up a 48 hour time log), and second, that it didn't encounter a bug while doing the processing. As of around September of last year, this program is done, and does its job perfectly every month.
Another example, also in Lisp, is used for making estimates for my clients. I give it a list of tasks with 3-point estimates, it churns through and calculates all the means and standard deviations, generates a file for Pandoc to consume, and spits out a PDF. I use it every couple of months. No tests, all done inside the SBCL repl. I obviously proofread the output PDF before sending it to a client, but that's again to check for bugs and to check for brain farts.
I've worked on great codebases that have giant test suites, and I've worked on terrible codebases that have giant test suites. And likewise for no test suites. While I appreciate the sentiment, I think it's dangerous to talk in absolutes like that. While I agree there is probably some degree of correlation between whether or not a codebase has a unit test suite and whether it's good code, writing unit tests does not intrinsically make the codebase good, and not writing unit tests does not intrinsically make a codebase bad.
Earlier quoted context omitted.
> I also have friends who have been in tech for close to ten years, and are close to burning out I realize the audience here is probably mostly younger folks but 10 years doing anything is not that much time IMO. I think a 3rd or 4th burnout at 30 years of service is a lot harder to recover from, but I’m biased from my own experience.
Would you share yours? I'd really like to hear from an older person. I'd imagine you know 10x of what I do now. It would be incredibly helpful if you could share some of what you've experienced and learned.
I got to kick back a bit and the job was more about delivering accurately and not delivering volume. I spent the first 3 years in that position recovering from prior burnout while still working. I got bored, so I quit and started a business. I worked myself for years right into the ground, burned out again. I took a few months off and relaxed. I ended up geting bored again before I fully recovered and went back to work.
I changed career tracks and switched technologies figuring this would give me a challenge and excitement. A new profession, systems, and rules of engagement. I was truly excited at first and I worked hard. Then I burned out again, before having recovered from prior burnout. This time it isn't due to lack of work/life balance, its due to lack of technological and social satisfaction.
At first I thought it was a bout of imposter syndrome as it's a new career but as time went on I realized it's more about the industry, the direction it's going, and the effects of people getting into STEM for money and not because they're technologists. It's a lot of younger folks who boast about their adderall abuse, get excited to give presentations, and other stuff that I'm really not interested in.
I'm stuck in burnout #3 now. It’s easier to burn out after the first one. I don't have the ability to make a risky move at the moment, I have people who depend on me. I don't know what my next move is now but as you age and your responsibility grows your options shrink. I think I might ride out the virus and look for a new job in the hopes a new environment will give me a push to keep going.
I have also experience close to burnout and recovered multiple times, in the process I have lost very precious relationships, and entire years were spent in darkness. I also have friends who have been in tech for close to ten years, and are close to burning out though they would never admit to such. This is the nature of the beast, all things that appear glamorous on the outside ( Hollywood, Finance, Tech, many nonpr…
I would also like to add that therapy is not just for the mentally ill, and nothing to be ashamed of. Navigating your career, and life in general, is tough and a good therapist can help put it in perspective. I personally went to therapy weekly for about six months to help deal with the impact of burnout on my life. I think I came away from it a more capable person.
Do you think therapists get tired of dealing with people who are just unhappy with their job in a bubble?
It is here in HN that I first heard Pablo Neruda's "No culpes a nadie". Even though a fan of Neruda I somehow had missed this. Perhaps this speaks to you something too: ## Don't Blame Anyone Never complain about anyone, nor anything, because basically you have done what you wanted in your life. Accept the difficulty of improving yourself and the courage to start changing yourself. The triumph of the true man emerges…
That is not a Neruda poem. It is apocryphal. Pablo,ever the communist, would have never written such a piece of libertarian crap.I am surprised that such a fan of Neruda as you claim to be did not notice that.
Either way, it's a fact. Protip: this is the part where you see reality and update your perspective
I'm having similar issues, and i think i found a way out: stop playing their game. Don't make enterprise software. Don't write unit tests. Don't accept pull requests. Simply write software for yourself and have fun doing it. Forget refactoring code into modules, just fucking code. Don't worry about deployment with k8s, just copy the Python script to your production folder and run it. Fuck all that shit about git bran…
This is a great point, laced with justified indignation. As a graybeard, I've seen multiple generations of "how to do software" and the most recent are the least fun. A lot of this is driven by the agile approach. It's tailor-made for dev burnout: from the endless tight cycles that force people into an infinite loop of productivity with scant satisfaction that comes with "completion", to all of the tools and philosop…
> Likewise, with CI/CD. And don't get me started on the monkey-work that is TDD. You might argue that it improves code quality. But, it's hard to make the case that it improves job satisfaction. If you move more work from the creative, problem-solving bucket into the busy-work bucket, the result will not be personal fulfillment.
> Does agile increase productivity for companies? Sure. But, it comes at a high cost that's mostly paid by devs.
I agree wholeheartedly with you. I'm by no means suggesting we move back to waterfall, but I am really enjoying the work I'm doing more and more of lately: embedded. Nominally it's a sort of Agile-type workflow (Kanban-ish), but because there's hardware design and manufacturing in the loop, things get planned out early and the multi-month plan doesn't change very much. New algorithm ideas pop up and get scheduled, new ways of doing sensor filtering pop up and get scheduled, but the direction of the wind doesn't change at the start of every "sprint". There are no sprints, just a prioritized/sequenced task list that gets reevaluated periodically.
(Plus, I get to go back to my old days C-hacker roots. The thing builds with a Makefile and spits out a ~32kB binary that gets flashed onto the device.)