Heh

Cloudflare has been pretty bad too lately. Its like the big companies are not even trying anymore. And if a real war broke out…their facilities are all centralized and VERY easy to target. Keeps me up at night sometimes since a vast majority of services at work are all on central servers.

In theory the internet self corrects. But in practice, if AWS/Cloudflare/MS/etc…goes down, a LOT of other services you dont even know about are effected. Last AWS issue took down Azure as well as people were scrambling to get servers back up and running (among other things).

Its not the best in my opinion. The graphics are not the best and the single player is pretty boring. But its free so give it a shot.

Source: https://mastodon.gamedev.place/@mcmartin/116327750192025016

How did you get the CI working in codeberg? last time I checked, you had to get permission to do so(?). I would love to switch when I have time.

I have a library that has over 2 Million downloads in pip. How do you switch from github to codeberg (or any other git)? I just dont want to break things for everyone :)

I like it.

Yeah I like it quite a bit.

Bash that can do the same job regardless of ci tools is underrated. I likevthat setup too because if your tesm eber needs to run a job/deploy/ect they can with the same exact processes the ci employs.

Im not sure about the CI solution they are recommending, but I do agree there are some sharp edges to GH Actions. Its not the greatest at logs and had hidden issues all over the place.

Looks like its not loading properly. Im seeing it on piefed without issues:

but on the original source:

Hope you enjoy!

I like both because, while they have definitive examples with code, they make the lessons the main part of the chapters. And they go over some VERY real world examples. They feel more “real” than theoretical books that I have seen. And as a software dev of 20 years, its the real examples that get me.

"Build APIs You Won’t Hate: Everyone and their dog wants an API, so you should probably learn how to build them "

Great book, if a bit dated on the coding examples. It goes over common issues with APIs that I have seen play out.

“Working Effectively with Legacy Code” - Excellent book that goes over what to do in plain english when you got stuck with legacy code.

It helps! Ive seen it with two jobs completely change the culture around code review.

• Instead of you/team lead being the bad guy, its now the code/process.
• Code becomes more stable and releases actually become more frequent.
• If something goes wrong, your VM/docker/box/etc… can just be re-spun up by the same process.
• Easier to onboard since the same build process is in the CI. And is constantly being used rather than relying on the README (that may not have been updated in a while).

Mind you its not perfect of course. You can still “Vibe” test and/or remove tests that dont work. And make the project more brittle. Or go overboard with lint rules (I actually had to break up a fight with that one). But its much better than the old process of merge and pray.

Make ci/cd part of the process. It stops a lot of people who push huge unmaintanable changes.

If it doesent pass the tests and cant build then it stops them from merging.

It would be fun to create a CURL converter. Just simple aliases or conversion tool.

I just looked it up, looks like there may be something like it here: https://github.com/christianhelle/curlgenerator

I like the look of this: https://www.createopenapi.com/

How interesting! Very nice visualization.

I still have one. Its good.

I mean you can …but its gonna be slop.

I remember some crazy stuff back when I had to work with a Java + ember.js project. Everything was like that.