As a practicioner programmer why is it difficult to go back from using sophisticated technologies like blockchain smartcontracts to crafting sql queries and managing cloud primitives ?

Switching from sophisticated technologies like blockchain smart contracts to more traditional systems such as SQL queries and cloud services can be challenging for several reasons:

1. **Complexity and Paradigm Shift**: Blockchain and smart contracts often involve a different programming paradigm compared to traditional SQL and cloud services. Blockchain requires understanding decentralized logic and cryptographic principles, while SQL is more about relational data management and CRUD operations. The shift from a decentralized, consensus-driven model to a more centralized one can be disorienting.

2. **State Management**: In blockchain, especially with smart contracts, the state management is handled in a distributed manner with each node maintaining a copy of the state. In contrast, traditional databases use centralized state management. Transitioning between these can be challenging as the concepts of state and transactions differ significantly.

3. **Security Concerns**: Blockchain provides a high level of security through its decentralized nature and consensus mechanisms. Traditional systems rely on different security models, including access control and encryption. Adjusting to these different models can be difficult for someone used to the security guarantees of blockchain.

4. **Development Tools and Environment**: The development environment for blockchain and smart contracts is often specialized with its own set of tools and languages (e.g., Solidity for Ethereum). Traditional SQL and cloud services use different tools and environments, which can feel less integrated or more cumbersome by comparison.

5. **Performance and Scalability**: Blockchain systems, especially those involving smart contracts, have different performance and scalability considerations compared to traditional databases and cloud services. For example, blockchain transactions can be slower and more costly, while SQL databases and cloud services often require different optimization techniques.

6. **Mindset and Methodologies**: Working with blockchain often involves thinking in terms of immutability, decentralization, and consensus, while traditional databases focus more on data integrity, transactions, and scalability. Adapting to these different methodologies can be a mental shift.

Overall, the difficulty comes from adjusting to different paradigms, tools, and methodologies, as well as managing the transition in mindset required for effective use of traditional systems after working with advanced technologies like blockchain.

#programmer #tooktoomuch #blockchain #crypto

Haven’t seen any client doing this but:

An option to show repost X times and don’t show it anymore, or hide it behind a “would you like to see the same mf post again?”, would be nice.

It gets kinda annoying to see the timeline full of the same reposts, or idk. Maybe 1K+ following is not enough now 😂

I kinda liked this guy but this is straight up retarded. This is way beyond the average level of stupidity. Focusing your persona around being white is at the same as focusing your persona around the concept of being black. He is falling on the same level as BLM.

I’ll zap the first person who knows who this is

Let the rituals begin

I feel like a total fucking dork wearing a mask out in public right now, but it does help with my allergies, so I will risk looking like a dork If it means I don't have to slam my body with pharmaceuticals every day.

We need a system that does not depend on ICANN and the TLD/gTLD domain sale system.

Why does someone get to "own" .com or .org per se? IP addresses are cumbersome, sure, but still...

Can we establish a competing system? Like make a *.nos / *.nostr / *.str / *.otherthings that uses one's relays as a DNS? We could then distribute the records and set up proxies, etc. in a way that is verifiable.

Devices ship with IP addresses, default DNSs, and trusted domain names. We can build that into clients.

Can we not keep doing this, it’s getting old.

How many open source projects have you dug into to verify the internal cryptography does what the project says? Do you always build from source code and install your own compiled binaries on your devices, or do you download and install precompiled software like everyone else?

Soy