I might have missed it, but I don't see this quote in the article. Either way, it feels disingenuous when a place like business insider posts these criticisms of FIRE like it is the ultimate gotcha.
Finding a purpose outside of work seems like the main issue most people struggle with when doing FIRE. Once you get going, the saving is automatic and addictive to some, but figuring out what to do with your life to give it meaning outside of a traditional work context is not just an issue with FIRE.
I’ve recently learned to downvote/flag and not respond to green names. The number of new accounts coming in hot with inflammatory takes lately has seemed higher to me, but admittedly this is purely a “vibe,” I have no numbers to back it up.
The U.S. government won’t have a seat on the board and agreed to vote with Intel’s board on matters requiring shareholder approval “with limited exceptions.”
The cumulative ROI for basic research is positive, but I don't think that is true for many individual research efforts, which is what a company is more likely to support. An individual company seems much less likely to benefit enough from an aggregate pool of research that they will actually contribute. Look at the state of open source software with respect to company investment in maintainers.
No you cannot. While it is 1 to 1, you still need to know where to start as if you start at the wrong place data will be interrupted as an asm instruction and things will decode legally - but invalidly. It is worse on CISC (like x86) where instructions are different length and so you can jump to the middle byte of a long instruction and decode a shorter instruction. (RISC sometimes starts to get CISC features as they add more instructions as well).
If the code was written reasonably you can usually find enough clues to figure out where to start decoding and thus get a reasonable assembly output, but even then you often need to restart the decoding several times because the decoder can get confused at function boundaries depending on what other data gets embedded and where it is embedded. Be glad self modifying code was going out of style in the 1980's and is mostly a memory today as that will kill any disassembly attempts. All the other tricks that Mel used (https://en.wikipedia.org/wiki/The_Story_of_Mel) also make your attempts at lifting machine code to assembly impossible.
It definitely isnt a 1:1 process, as there are multiple ways to encode the same instruction (with possibly even having some subtle side effects based on the encoding)
Mire things down in bureaucracy. Try and make everything take substantially longer than it should. Throw up hurdles in the face of progress. "Forget" to do important steps in the process so that you have to re-do work. Implement things on the face of it that are correct, but that don't achieve the same result, etc.
Finding a purpose outside of work seems like the main issue most people struggle with when doing FIRE. Once you get going, the saving is automatic and addictive to some, but figuring out what to do with your life to give it meaning outside of a traditional work context is not just an issue with FIRE.
reply