Azure | .NET | Godot | nibble.blog
No one can make moral or ethical judgments for you. I recognize the hesitance towards defense, surveillance, attention-commerce, and tech consultancy. However, there can be positive moral and ethical perspectives even on those examples. The reverse is also true for industries that, on the surface, seem much more ethically marketable. I personally consider any automation that removes human work from the economy to be a positive contribution to humanity. You can make the perspective that robbing labor opportunities from real humans is a moral failure. My point is that moral choices are usually based on a combination of personal values and a certain understanding of the problem space.
I can’t make ethical suggestions for you, but here are some options that might appeal to you:
A career is not only the industry or sector you service. It’s also about the relationships and colleagues you deal with. The work ethic and labor standards you have to deal with. The opportunities you get to build a reputation. The physical location of the opportunities. These are all things to consider when starting out on a career.
Edit: The best way to feel good about work is to set reasonable expectations for yourself to others and meet them consistently. Understanding human problems and solving them. That’s what telling computers what to do is all about.
All you folks are crazy not to unit test personal projects. Unit tests don’t need to be fancy and exhaustive. A sanity check and having a simple way to execute isolated code is well worth the 15 minutes of setting it up. Heck, just use them as scratch files to try out libraries and APIs. I can’t imagine having the kind of time to raw-dog that f12 button and sifting through print() nonsense all night.
A single race condition is a tragedy. A million race conditions is eventual consistency.
What I love most about Krazam is that in every video they make, you see the guy move up the usual tech career ladder xD
It’s difficult problem to solve. Lemmy’s stack is a bit unconventional. The rust backend is not idiomatic and the ui is based off a template of an isomorphic not-quite-react framework. Its not impossible, but it will take a while for alot of programmers come onboard.
That being said, there’s more to it than writing code. Better bug reports, reproduction, updating docs and triaging/managing the issues is possibly more important than writing PRs. Don’t be discouraged!
Want and grit. At some point you’ll have to grit it out. You have to make it clear to your brain that you want it. Make it personal. Want it not the way you want to have a cookie after dinner, want it the way you want to breathe. Don’t even want the project, but want to prove to your brain that you are a rare capable human, able to start and finish a creative endeavour independently.
Make work time scarce and urgent. Having a child has done wonders for my creative output. I used to splurge 6 hour sessions kinda working on something…now I get maybe 40 minutes a day. An hour if I’m creative about it. But heck, does that hour get applied like nobody’s business.
Hope this helps, best of luck!