FizzBuzzEnterpris VS holochain

> I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)

You can write that kind of crap in any language, including C++.

There’s a difference between complexity that’s inherent to the problem, and complexity that’s added by developers who have drunk architectural cool aid.

This is an example where all of the complexity is caused by rigid adherence to the most popular architectural patterns of about 10 years ago.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It looks completely ridiculous to modern eyes, but during peak OOP it was just how you should do it.

If you like simplicity then your fizz buzz implementation would be a few lines.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... isn't too far removed from some of what I've seen in big tech, especially architecture-wise. Certainly less costly absurdity.

What you need is Fizzbuzz, Enterprise Edition

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It's been a decade since I used C# but the corporate design pattern culture of that language back then turned me off of it forever.

Everything looked like this: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Maybe it's better now but the Java/C# practice of shoveling largely empty classes around with an IDE isn't something I'd point to as a good example.

```

With your example I had to think for about 1-2 min before it made sense. If the codebase is full of clever stuff then I have to spend hours understanding all of the clever things before I can make changes. If everything is simple then it's easy to change.

If you want to see where overengineering leads you then take a look at this project. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It is satire but I have absolutely worked in places that write code like that.

Good programmers know that it's 10x times harder to read code than write it, so they deliberately keep it simple so that they can read it later.

I did something similar a 4 or so years back. I wrote something in a month (+ a couple of working with stakeholders to make sure it did what it should). I did it in a legacy tech stack that the architects didn't like, on the side of the main activity, as the deadline was coming close and some hireing processes were slow.

A team of around devs 5 (some coming and going) having been trying to solve the same problem since, but they're still not being close to finished.

In other words, the productivity is in the order 50x to 100x slower than when I did it. Rather, the main reason was that I knew how to write code like that, while they were set up to fail.

Basically, some architect was making all sorts of unnecessary demands for how to wite the code, and the programers were not familiar with much of the tech stack that was introduced.

Also, coding standards were really verbose, easily 10x-30x what I wrote, in lines of code. The current state of what they have look suspiciously like FizzBuzzEnterpriseEdition:

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

TLDR; Incompetent tech leadership prone to cargo-culting, can slow down productivity to virtually zero. In some cases, productivity can go up by ~100x if ignoring their demands.

I swear I've worked with people who if they were shown FizzBuzzEnterpriseEdition wouldn't be able to see the joke as that's how they naturally write all code.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Reminds me of FizzBuzzEnterpriseEdition . https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

You never know when you might need to change the implementation of how the "Fuzz" string is returned, so you need a FuzzStringReturner.

And you never know when you might need multiple different ways of returning "Fuzz", so you need a FuzzStringReturnerFactory.

And that barely scratches the surface of what you need.

It’s been in the works for a few years, and recently reached its beta-rc stage. There’s a quick scaffolding tool, a Typescript client, Rust client (being updated), integration with Nix, Rust and Typescript testing suites, a Tauri-based launcher, an Electron template, etc. It can even be deployed in a cloud instance if you wish. There’s a pretty passionate community on Discord. The Open Source Initiative even approved the Cryptographic Autonomy License specifically for Holochain apps.

Holochain is a framework for building Peer-to-Peer apps. Everyone can make their own app which utilizes Holochain. Holochain is build by the Holochain Foundation as an Open Source project, i.e. the source code is openly available on Github and you can use and modify it as you wish. Other than providing and developing the framework, the Holochain Foundation will have no control over any part of the app you build. The Foundation also cannot control which apps are built using Holochain. It does not have any governance power in this regard.

I have been thinking about architectural models for making our application distributed, such as Holochain and Gun.eco.

I'm curious about future potential synergies between Holochain ( https://github.com/holochain/holochain ) and the Cosmos ecosystem, considering the consensus engine (under development : https://github.com/cosmos/cosmos-rust/tree/main/cosmrs ), the Interchain Blockchain Protocol ( https://github.com/informalsystems/ibc-rs ) and the smart contacts module (https://github.com/CosmWasm/cosmwasm ) exist in Rust.

are running encrypted app code for them so that they can take part in the app/network, without having the required technical chops (the holofuel currency measures processing power). the FAQ does a good job of explaining it a bit more: https://holo.host/faq/

i'm not super interested in the whole holo thing (they sold holofuel hosting credits). i am glad they did it because it meant the team could ramp up development.

about the marx and engels thing. i am most excited about the potential for http://valueflo.ws on top of holochain [3], because it will allow us to move away from today's Enterprise Resource Planning (ERP) software, into a new paradigm of Network Resource Planning (ERP) software, that i hope will have a big impact on supply chains of the next economy (socialist).

[1] https://github.com/holochain/holochain

[2] https://www.indiegogo.com/projects/holo-take-back-the-intern...

[3] https://github.com/holo-rea/holo-rea

Harmony One & Holochain

Hey y'all. I've been bouncing ideas around in my skull for how to implement a peer-to-peer / distributed / decentralized / serverless game backend, mostly for the lulz, the what-if's, and the is-it-even-possible's. It would run over a p2p distributed database, peer validation, encryption/signing, based on Holochain, and would include a form of distributed ECS for managing "server" logic.

> It would force the global north to actually build what it's consuming instead of extracting rents from intellectual property. That won't happen.

Oh fuck yes it will happen! Come join us at:

https://futureeconomiesreadinggroup.github.io

http://valueflo.ws

http://holochain.org

...and a bunch of other DWeb projects (many are listed/named in my comment history).