pull down to refresh

Become a Bitcoin developer!
Work in public with smart people on interesting problems, contributing to bringing about the native currency of the internet. Be under constant scrutiny, be held to the highest engineering standards, be subject to grueling lawsuits, earn below industry average, take six months to years to deploy any non-trivial features, explain frequently why the thing you are working on is not easily solved by the first idea everyone has, be called an idiot or traitor whenever you don’t cater to the latest narrative of Bitcoin Twitter, be attacked when you share your informed opinion on a controversial topic, also be attacked when you do not weigh in on a controversial topic, be accused of conspiring to add backdoors if you dare to discuss an idea with a few colleagues before sharing it in the public, spend 5–10 hours a week on manic allegations and brigading by "collaborators" and random people from the internet.
Apply today! /s
Your efforts are greatly appreciated Murch. The public scrutiny you expose yourself to and the selfless dedication in spite of it doesn't go unnoticed. Don't let the bastards get you down.
reply
You forgot to mention the worst part of all, writing code in C++.
reply
Ah drats, so true.
reply
C++ is not the problem. The problem is time and deep understanding of what happens inside.
reply
31 sats \ 0 replies \ @joda 28 Feb
Literally the language I started on, cried tears over, and the reason I almost entirely abandoned coding.
reply
reply
The White House is the last group I would turn to for language advice. Any White House, ever, since Nixon bashed COBOL.
reply
Political simpletons yell at something they have no capacity to understand. These were the dumb asses who played football and stayed out binge drinking offering technical advise.
This would be like me trying to advise the whitehouse how to best steal from the US citizens; then use those spoils to build machines fit for bombing people 4000 miles away - just because they wanted to trade their oil for silver.
reply
I feel like this is referencing that ridiculous article posted by bitcoin magazine a couple days ago. Talk about fearmongering. There's paranoia, and then there's.. whatever that article is.
The sound of ignorance is the prevailing noise on both sides of the pro/anti bitcoin fence. Unfortunately, hot-heads tend to be louder than the cool ones who would provide better feedback.
I for one have been very fortunate to be able to build on the work of the core devs over my career. The steadfast reliability of core is an incredibly fertile soil for other projects to sprout from. It's thankless work most of the time, so let me say: Thank you, and that goes for any other core devs who are reading this too.
In the event i or other stackers want to donate BTC to support the work of the core devs, what is the best way to do so in a responsible and transparent way?
reply
What a pitch!
reply
1323 sats \ 0 replies \ @Murch OP 28 Feb
Doesn’t help anyone to hide what they’re signing up for. 0:-) It can be a bit of a wild ride at times. It’s also the most unique and the best job I’ve ever had.
reply
479 sats \ 2 replies \ @Car 28 Feb
This is why at PlebLab we always do our best to showcase the amount of work and talent that build these technologies.
Totally down for a call with Chaincode to help with this.
reply
Thanks Car :)
reply
241 sats \ 0 replies \ @k00b 28 Feb
explain frequently why the thing you are working on is not easily solved by the first idea everyone has, be called an idiot or traitor whenever you don’t cater to the latest narrative
If it helps, this applies to anyone doing visible, meaningful work in the world. The automatic, vocal, criticizing, and ineffectual sub-group is one of the most self-sabotaging behaviors of human groups. The trait probably serves a purpose in some important corner case or circumstance humans can find themselves in, but most of the time we are just shooting each other in the feet.
reply
I can agree with @Murch on one point, we’re lacking reviewers experts on Bitcoin Core. Especially in the most sensible subsystems and working on the long-term interesting problems.
be accused of conspiring to add backdoors if you dare to discuss an idea with a few colleagues before sharing it in the public, spend 5–10 hours a week on manic allegations and brigading by "collaborators" and random people from the internet.
I’ll take the allegations of being a maniac (cf. wiktionary) as a compliment. This is true you have to be obsessed by a wide variety of topics (cryptography, math, networking, distributed systems) if you wish to be a high-performant security researcher or reviewers in the ream of Bitcoin Core.
And additionally, you have to be for sure a little be paranoid. Only the paranoid survive. the title of a great book by Andy Grove, former Intel CEO on crisis and inflection points management.
In my opinion, there is certainly a threshold of internal complacency or laziness where some patchset changes in Bitcoin Core becomes a backdoor of their own. Especially when the PR authors and reviewers are refusing to engage in a technical conversation on the flaws of said patchet changes.
On idea discussions among few colleagues, I cannot remember there were permissioned communication channels to discuss Taproot changes e.g True, there was a low-noise IRC channel where the changes were discussed, though “anyone” was able to join in knowledge of the IRC channel. In my regards, such Delving Bitcoin WG constitutes a “permissioned channel” as a) you might not be aware of the existence until disclosure and b) you have to ask permission to a moderator to join.
I stay at Murch’s availability if he wish to discuss on the topics where we’re diverging during a public podcast, with a neutral host, in a constructive and patient fashion. Taking time to listen to each other viewpoints.
All that said - Thanks Murch for your work on Bitcoin Core.
reply
reply
It really is the same energy. I love it!
reply
Sounds like the dream job
reply
Work in public with smart people on interesting problems, contributing to bringing about the native currency of the internet.
can't think of anything cooler than this, but the only thing I lack is coding skills, so I'm writing tips and tricks on how to use Bitcoin atm.
reply
296 sats \ 1 reply \ @Murch OP 28 Feb
And that is awesome!
reply
and absorbing from the cool devs day by day, who knows what's going to happen:)
reply
I appreciate you, Murch. Thank you and all bitcoin devs for your work and your fortitude. 🫂🧡
reply
42 sats \ 0 replies \ @joda 28 Feb
Don't forget you are immediately and permanently on government watch lists.
On the plus side, you may get approached for a "government" job or "other offer" that is more lucrative.
reply
31 sats \ 0 replies \ @OT 28 Feb
Its a tough job but someone has to do it.
reply
Holy shit! This checks every box on my "dream job" list!
reply
There is a kind of Copernican revolution happening here. For centuries, the Earth was the center of the universe. This aligned with the authority of the time, the Church. Empirical experience confirmed this. Our language continues to adhere to this notion: we clearly see the sun "rise" and "set".
For centuries money was issued by the State or the kingdom. The faces of great leaders printed on the money itself remind us of its provenance. Taxes collected to build great projects like highways and dams, and used to fund the military ostensibly to protect us, continue to inform us who are our true masters.
Satoshi has successfully decoupled money from the State. Copernicus showed us through careful observation that the Earth was not the center, but that we revolve around the sun. Both of these shifts in perspective greatly upset the balance of power. A universal truth about power is that the powerful want to retain their power. Threats that undermine this power will be punished. Even 60 years after Copernicus' death, Galileo was put under house arrest for the remainder of his life for proclaiming that Copernicus was right.
Those who develop Bitcoin core are the brave Galileo's who stand up to power because they see the truth and embrace it despite the danger.
reply
0 sats \ 1 reply \ @anon 16 Mar
Following up on this: How would you recommend digging into the technical details? Learning c++ first and reading through the whole project?
reply
Understanding C++ definitely makes it a lot easier to start to contribute, but reading the whole project would probably be difficult and not that useful. I find that the people who found an issue in Bitcoin Core that they were motivated to solve due to their own interest tended to succeed most often. They tend to be looking at a narrow area of the codebase and their goal allows them to feel that they are progressing in the limited area they have set themselves.
reply
🧡
reply
Stay strong 💪. The grind is never easy.
reply
0 sats \ 0 replies \ @gd 28 Feb
I'm in.
reply
be called an idiot or traitor whenever you don’t cater to the latest narrative of Bitcoin Twitter, be attacked when you share your informed opinion on a controversial topic, also be attacked when you do not weigh in on a controversial topic, be accused of conspiring to add backdoors if you dare to discuss an idea with a few colleagues before...
Although it might not feel like it, all this is just Bitcoin Twitter's way of showing love ❤️
reply
we really need another client implementation, I have utmost respect and eternal gratitude for the core team, but it's a lot of responsibility, (single) point of failure, attack vector and stress on people when on 98% of network depending on it. maybe with etf inflows some new team with new client ideas emerge
reply
Appreciate everything you do and everyone else who contributes.
So true! The unfathomed and unimaginable limits that you cross shall always gain you some trouble. But what matters in the end are your efforts for a positive change. Who didn't have to face the rampant scrutiny? Even the best with knowledge and selflessness in entire human history had to pay the price for their innovative approaches.
stackers have outlawed this. turn on wild west mode in your /settings to see outlawed content.