ArchAengelus
@ArchAengelus@lemmy.dbzer0.com
- Comment on Weekly “What are you playing” Thread || Week of May 5th 1 week ago:
Replaying Fallout: New Vegas. I wanted to do a tale of two wastelands, but I couldn’t get the mods to settle out. It’s a much better game than I remember from my first play through!
- Comment on Nintendo DMCA nukes 8,535 GitHub copies of Switch emulator yuzu 2 weeks ago:
Ryujinx works well, but not as well as yuzu, and doesn’t seem to be a target of takedowns
- Comment on RNAception 2 weeks ago:
Thanks! The first link was a useful summary, and I’ll look at the others when I have more time!
- Comment on RNAception 2 weeks ago:
Anybody got a link for a good explanation of this for someone whose knowledge of micro bio is 12 years out of date?
- Comment on I'm 99% sure it's not real 4 months ago:
As an engineer:
- Receive or identify a problem.
- Design a solution that solves or mitigated the problem.
- Usually pay someone to make a prototype or do it ourselves
- Test the prototype and see if it solves the problem. If no, go back to #2 until a workable solution is found
- Get someone else to build the final thing.
- Make sure thing works. Ship it.
This is a recursive and iterative process. Meaning you will find problems inside your solutions and need to fix them.
Eventually you finish the thing and get a new problem and do the whole game over again. It’s like a puzzle that requires absurd amounts of knowledge to play well, but anyone could try to solve the problem. That’s why good engineers are paid pretty well.