BadBadJellyBean (u/BadBadJellyBean)

BadBadJellyBean commented on Read your code etsd.tech/posts/rtfc/... · Posted by u/noeclement

> Another related rule: never commit code to the main branch that hasn't been read by at least two humans.

Passive code reviews ("read by at least two humans") are fraught with error. IMHO, a better mantra is:

  Never allow a merge to the main branch that does
  not have some amount of documented test coverage,
  be it unit, functional, and/or integration specs.

BadBadJellyBean · 25 days ago

Of course that is true but with AI you can add documentation and tests. You can have absolut garbage with all green tests. We do human reviews on PRs but in the end it's your code that you have to stand behind.

BadBadJellyBean commented on Read your code etsd.tech/posts/rtfc/... · Posted by u/noeclement

BadBadJellyBean · a month ago

We have a simple rule: You commit it, you own it. If you vibe coded it that's okay. If it's garbage that's on you. Blaming the LLM doesn't count. So of course you have to read the code. You have to read it and understand it. Works well for us.

BadBadJellyBean commented on Valkey Turns One: Community fork of Redis gomomento.com/blog/valkey... · Posted by u/cebert

echelon · 3 months ago

Yes, making money is bad. Open source is only in service of the monopolies.

Only AWS and the hyperscalers deserve to make millions from Redis. Screw the Redis authors and maintainers.

Lesson to all DB startups: fair source your license. Put in anti-hyperscaler clauses into your licenses to preserve your ability to make money and be sustainable.

You can let your customers have unlimited access to your code, but stamp out the ability for AWS or Google to offer managed versions. They need to pay you.

Don't be Redis or Elasticsearch. For them it's too late. They went uber permissive and now their fate is sealed. They're hundred million dollar cash cows for the giants, and the main committers see none of that.

BadBadJellyBean · 3 months ago

I just don't like using a permissive open source license as a booster for your software and then changing it when others make money. Either start as a closed source/source available project or find another way to make money.

This whole "but we wanted to do a cloud offering, it's not fair that AWS/Azure/GCE make one with our software and everyone is using theirs" is just so stupid to me.

You wanted people to adopt your software. You used permissive licenses to convince people. People adopted your software probably because of the free nature of the software. Now you want to change that. Well that is just stupid.

I think that is especially true for Redis. Redis is a good software. Many integrated it but it is not irreplaceble. The idea of a KV store is not that novel.

BadBadJellyBean commented on Cargo-mutants:zombie: Inject bugs and see if your tests catch them github.com/sourcefrog/car... · Posted by u/todsacerdoti

matthewfcarlson · 5 months ago

I wonder if there’s something similar to run on a c codebase.

BadBadJellyBean · 5 months ago

There are a few. See: https://github.com/theofidry/awesome-mutation-testing

BadBadJellyBean commented on Why Go's Error Handling Is Awesome rauljordan.com/why-go-err... · Posted by u/chautumn

BadBadJellyBean · 6 months ago

I stronlgy dislike Go's error handling. It is incredibly annoying to add

  if err != nil {
      <do stuff>
  }

after nearly every function call and to have a error as a secondary return type. At least for me it is clunky and annoying and incredibly distracting. If there was at least some syntactic sugar around this I could probably live with it but like this I just don't like using Go.

BadBadJellyBean commented on Lake-harvested cocktail ice is an old business making a comeback in Norway vinepair.com/articles/lak... · Posted by u/ohjeez

BadBadJellyBean · 6 months ago

Yes. Let's haul tons of ice through the country that is potentially even dirty. Just so that some has more interesting ice in their drink.

BadBadJellyBean commented on I don't like Docker or Podman blog.liw.fi/posts/2025/do... · Posted by u/0x2a

BadBadJellyBean · 7 months ago

I always wonder what kind of setups people have where docker destroys their network config. I have used Docker on so many systems over so many years and several distros and not once have I encountered that. Same with people who say that systemd made their system implode and wayland makes their baby cry. What are these people doing?

BadBadJellyBean commented on TfL abandons plans for driverless tube trains ianvisits.co.uk/articles/... · Posted by u/edward

sofixa · 9 months ago

> Despite the claims that it would prevent strikes on the tube, the reality is that it wouldn’t, as driverless trains would still have staff on board

Why would they? Paris lines 1,4, 14 and soon 15 have zero staff onboard

BadBadJellyBean · 9 months ago

Same in Nuremberg. And they don't even have automated gates. It seems to work well.

BadBadJellyBean commented on PHP 8.4 php.net/releases/8.4/en.p... · Posted by u/theThree

jiehong · 9 months ago

Python’s packaging and dependencies system is lacking, but trying to get better. But too many choices not always compatible nor working perfectly right (should you use pip, poetry or pipenv? Well, you see…)

How’s php’s?

BadBadJellyBean · 9 months ago

> Python’s packaging and dependencies system is lacking

It is? I never had problems with poetry. Though I agree that there are mroe options than necessary.

BadBadJellyBean commented on How do you deploy in 10 seconds? paravoce.bearblog.dev/how... · Posted by u/mpweiher

hellcow · 10 months ago

I solved this a different way -- only very senior engineers were allowed to access/deploy to production. Senior engineers (by experience, not title!) had a much better understanding of the full system; they better understood the risks during a deploy and what to watch. They were doing the PR reviews as well.

Many ways to skin the cat. This is just one of them.

BadBadJellyBean · 10 months ago

Senior engineers made the mess. Because "I just need to fix this now. I'll commit it later". CI/CD gives you stronger guarantees. You can know which code is now in prod. That is so much harder to ensure when there is human intervention.