Avatar
Fervour
278492a905cab200737ee5bdac11f9824a9a599e56c231eb4a0d555d22668f30

Also seems as though the sunk cost fallacy applies to this in some way. People are so deeply invested into their way of thinking that to deviate now would feel to costly.

I truly do believe a lot of people like being dependent on the ideas of others and in some way fool themselves or turn a blind eye to the negatives.

Replying to Avatar Cyph3rp9nk

Rats, wish I’d seen this advice 3 hours ago. Could’ve saved my knee.

Your blacked out nym portrait thingy is wikkd. Nice one

Why did damas app just ask to connect to other devices on my network? #damas

Replying to Avatar Lyn Alden

A recent meme has been “Nostr Lyn” where I am more raw here than anywhere else. I love that. Nostr is raw truth. Here is some meat for those willing to be here, purposely enjoying a decentralized and small protocol/community. No filter; just me.

I eat healthy, I exercise, I minimize problems, etc. I am one of those people who, when I first experimented with a keto diet nearly a decade ago, measured my ketones with a blood test on a regular basis to ensure I was in ketosis, and plotted out my blood sugar and ketone level on a regular basis, to see how it matched with my subjective well-being and various biometrics. I was doing science and various if/else observations. And now that I have experience in this dietary regard, both subjectively and biometrically, I am more flexible in terms of seasonal ketosis, broadly low carb, mild/moderate cheat meals at restaurants, and so forth. In other words, I precisely know my dietary limits where I feel bad vs where I feel good generally. I bike most days, and run and lift where possible. I enjoy a nice glass or two of wine with a nice meal on occasion, but little else.

But on those very rare occasions when I disregard moderation, well, fuck. “All things in moderation, including moderation. Sometimes you gotta party”. During the depth of my recent burnout phase in the past two weeks, I went out and… I ignored moderation one night in terms of wine and such. In terms of numbers, I only get hungover like once per year. I do, afterall, live near Atlantic City, which has plenty of clubs and so forth. I don’t even like marijuana, but I did marijuana too (which is legal in this state).

The next morning? Holy shit. I hadn’t been wrecked like that in a few years. Not only was it my yearly fuck-up, it was my multi-year fuck-up. It was a culmination of working 16-hour days with no weekends for months in a row and then the release all at once. My advice: don’t do that if you can help it. Especially if you are in your 30s or older, where you don’t heal as quickly as if you are in your 20s.

I had an interview with David Lin at like noon the next morning and my base case was to cancel it at the last minute due to how rekt I was. But I had *never* done that before, and Lin is an amazing interviewer and an acquaintance of mine, so I couldn’t do that to him, and I knew he could handle it if I was a bit lackluster. Tens of thousands of people would see this.

So, I rolled out of bed, drank some matcha, and somehow got myself in front of my camera to try to replicate what I would normally do every day with no issue. While I was doing it, I felt so off-base, thinking, “Anyone watching will know I’m so fucked right now that I’m like almost half-drunk from last night. This might be my worst interview ever. They’ll notice, right?”

I was almost afraid to go back and watch it. I only watch a small subset of my interviews for iteration purposes, but because this was my potential fuck-up, I went back and watched it closely. And you know what? In terms of views and comments and content, it was above average.

Probably it was because I was so mentally focused at the time to not fuck up. Where I lacked energy, I made up for in focus. I looked for signs in myself in my after-review, and the *only* place I can see it is in my eyes. I often squint during interviews because I am thinking a lot, but in this interview my eyes are constantly squinted/dead because I am barely able to even be there. That’s the only small sign where my multi-year fuckup hangover becomes apparent. All of my verbal content is normal, and leans above average.

After the interview, since I was non-functional, I went back to bed, and vowed not to fuck up like this again. This was my biggest hangover as a serious adult. Sitting there and talking about macroeconomic content for 45 minutes was an all-out massive effort.

But I also learned something, which kind of goes back to my martial arts days, college days, early work days, and goes back to various business memes. A common business meme is, “Most of success is just showing up.” Much of that is actually true, but I would rephrase it as, “Much of success is taking initiative, finding ways to show up, and then be consistent with quality."

You can’t, for example, be 10/10 in most interviews and then 2/10 in some interviews. You need to be 8/10 or better all the time. So, whether it came to my engineering work, my analysis work, my media work, etc. You just have to *fucking show up in good order* no matter what. Consistency of quality. Every single day. You traveled and had jet-lag during an important meeting? Tough. Your baby kept you up all last night? Well, you're paid the big bucks to tank that anyway. You got rekt in Atlantic City? Deal with it.

The first order advice here is don’t drink and party at clubs in Atlantic City the night before an interview or other serious work as a way to relieve an unusual amount of work stress during the prior months of over-work.

The second and probably more important and broad takeaway is about minimizing your weaknesses- when you do fuck up, be able to handle it. We all have moments of weakness. Success is about showing up with intention and quality. When it matters, you need to be there, present. You have to summon the strength to get through an hour about math and macro and sociability or whatever it is that you do, where you are half-dead, where your problems are only visible in your eyes, and just get it done.

I’m better now, but that was a low point. I was still running my research business, concentrating finishing-touches on a year-long book, and just literally working 80 hour weeks. Sometimes we need bursts of that sort of thing but it’s important to minimize it and get back to work/life balance, and ultimately when you are at your lowest, still find a way to be there.

Anyway, this is the current issue of "Nostr Real Thoughts". Enjoy the interview. Spot my failures.

https://www.youtube.com/watch?v=dXujV7P_hZc&ab_channel=DavidLin

Fire! That put a big smile on my face. Been listening to your interviews for a number of years now.. but that post is pure gold. Your a blardy legend Lyn.

Sorry for late reply, I didn’t see this at first. Tbh I’m just at the start, I’ve not started on the LN/ wallet yet. Basically just stated setting up a BTC node and will go/progress from there. So I’ve put the node together and done the virtual machine part, installed tor using apt install tor and can see it running. But I now am not sure what the tor part is actually protecting.

Sorry to info dump… yikes

When I check the status of tor on a virtual machine via terminal and it says “running” etc, what does this actually mean in terms of security?

So If I open a random browser on the vm is the traffic on that browser using tor? Or would I need a tor browser with vpn?

#plebchain

Replying to Avatar Lyn Alden

For reference, here are my main thoughts on the current Bitcoin softfork ideas/dramas to those who care.

For context with regards to wherever it might matter, I have a 12-year background as an engineer initially and eventually an engineering manager, including overseeing electrical/mechanical/software for an aviation simulation facility, but although I have written code here and there in my early days, I am certainly *NOT* a software engineer. My career work is on electrical engineering and multi-discipline engineering management, and my master's degree is in engineering management, with an emphasis on systems engineering and engineering economics. Any viewpoint I have is from an engineering/systems management perspective or an economics perspective, not a programmer perspective.

I follow multiple software Bitcoin experts on various topics, many of which disagree with each other, similarly to how I followed my various lead engineers when I was working in engineering management.

The U.S. Constitution is well-written but of course not perfect. It's a good document, especially after the amendments it has had. The most recent amendment was over 30 years ago, and it is minor enough that most people don't know what it is. The second most recent one was over 50 years ago, and that one is also pretty minor, imo, and most people don't know that one either. The Constitution, the Bill of Rights, and a then a handful of key amendments after that to fix key issues with race and gender voting and so forth, have been the foundational aspects of this whole Constitutional project.

In order to change the U.S. Constitution, you need both a supermajority in Congress and a supermajority among States. Good luck getting that. And that near-immutability is exactly why the Constitution is valuable. Even if it was better written and included all sorts of things I liked, if it were easier to change, I would consider it to be a *worse* foundation than it is now. The near-immutability is the critical part. A nearly-immutable good document, is a great document, if it serves as the foundation of something important.

When it comes to Bitcoin, the aspect that I view as being the most valuable is its near-immutability. We have a global open-source ledger foundation that gives us savings and payment/settlement technology. It makes hard trade-offs in order to remain reasonably decentralized. And yet, Bitcoin can settle more transactions per year than Fedwire does, which is the U.S. base settlement layer, which handles (not a typo) 1 quadrillion dollars worth of gross settlement volumes per year. Bitcoin does that function but is global, open-source, and has its own scarce units. Various layers can expand that scalability, (Lightning, sidechains, fedimints, custodial environments, etc). Certain softforks to the base layer may also add some new scalability options (covenants, drivechains, zero-knowledge proofs, etc). But those softforks present risks to the whole project, unless they have a supermajority of support and are considered to be of low technical+incentive risk.

When I was an engineering manager for my aviation facility, if I were to approve a major new change and help fund it, it would be because the supermajority of my senior technical leads supported it, and because they could convince me of it. Objective truth tends to be easy to share between rational people that listen to each other. In contrast, subjective things that are more contested of course tend to be harder. If I liked a new change but it didn't have a supermajority, I respected these divergent opinions and wanted to know why they saw it differently. Unless it was in an area where I was *specifically* the facility expert in (in my case, the electrical/control aspects within our organization's aviation simulators), I would never go with a minority opinion among my technical leads and override the majority of my technical leads.

One of the most common problems I encountered in my career was over-engineering. Not a single person knows every detail about how an aviation simulator works (which was my field of work). There are software experts, graphical design experts, mechanical experts, electronics experts, pilot experts, and then business experts that have to figure out what is valuable to clients and how to get the required stuff and how to make the whole thing economical and thus well-incentivized. Systems engineering, practically by definition, is the science of managing a project that is more complex than any one human mind can possibly understand. Any major project engineer/manager has to deal with this dilemma.

As it pertains to over-engineering, many people often have pet projects that they care about, or want to make really cool complex things, that are not economical or not robust. Endless changes can create endless complexity, which are hard to maintain, are less reliable, and so forth. The most beautiful engineering designs are often the most simple at the foundation. Complexity can exist in layers or silos built on or around that foundation, which reduces contagion risk to the simple-but-robust foundation.

In short, if you you can't convince a supermajority, then maybe your idea isn't right or needs more work. Maybe the problem is on your end. Especially if the supermajority that you need to convince are intelligent relevant people (in Bitcoin's case: software developers, node-runners, miners, capital allocators, etc).

And of course, foundations like the U.S. Constitution or the Bitcoin base layer are far more important than the engineering frameworks of some random aviation simulation facility, so the standards are higher.

So, how do I assess proposed softforks as someone who hasn't written code in a decade but tries to follow the designs and economics of various proposals where possible? I look towards technical leads, and look for a supermajority of serious stakeholders, and need the proposal to clearly make sense to me technically and economically.

I view Bitcoin as being valuable due to its near-immutability. That is the source of its monetary premium. And so as follows, from a project management perspective regarding what is among the most serious of all possible projects:

-The first rule of Bitcoin is you do not break Bitcoin.

-The second rule of Bitcoin is you do not break Bitcoin.

-The third rule of Bitcoin is you do not break Bitcoin.

-The fourth rule of Bitcoin is that, around the margins, you try to find conservative ways to improve Bitcoin that are clear enough to get a supermajority.

Therefore, my view on softforks is that I defer to the supermajority of experts I trust, while also needing it to make sense to me personally. I'm agnostic towards many softforks, since I don't have the detailed software expertise to be relevant between similar proposals. As proposed softworks gain momentum, I check to see if they make sense to me, and then look for a supermajority.

Bitcoin is valuable due to its near-immutability. If it can be changed by minority factions, then the relevance of the project over the long arc of time is limited. To the extent that it's going to be any sort of important base layer, that near-immutability, much like the U.S. Constitution, is critical. To that extent, any proposed change to Bitcoin is not just a software thing; it's an economics thing as well.

Therefore, if proponents of a given softfork try to find a way to push itself on the network without a supermajority of technical experts and economic actors, then whether or not I like it, I will oppose it. That's a way to turn me from neutral to opposed. Because that near-immutability is what I would fight for. I only support highly agreed-upon changes. Whatever small piece that my node, my voice, and my money can do, I err towards the near-immutability.

Very well said, thank you for that insight. This actually resonates with me. And in some ways, it’s as if the more people that get involved in something it drives up the potential for it to become unwieldy or chaotic and the original signal becoming lost.