Game mods and Advent Of Code did it for me.
I did a small RimWorld mod and a parser for NoManSky internal format.
Creating both of them was a blast. I had fun doing programming stuff again.
Advent Of Code allowed me to try different languages in a small bursts of the different problems. Somehow I really like this format.
Assigning different vlans for devices should enable network separation. "Stuff" from different vlans should not talk to each other.
From my personal consumer experience I would say twitch streams and steam demo fest are my two main sources of new games to "put a pin". And on twitch I mostly watch small channels (below 200 viewers), with couple of exceptions.
I don't think that this is Angular specific. Long lived branches is a known problem in development world. So far I only encountered one solution/rule that worked (for me): long lived branches can only do nonbreaking changes. If you want to have a long lived branches and it will have a breaking change/feature, then you should first extract breaking behaviour to the develop branch and only then work in the long lived branch or feature.
This is obviously quite hard to do in some cases, but I didn't found anything else that works in such situations.
When your jvm vendor is IBM? I don't see other reasons. OpenJ9 had quite good polyglot vm Platform. I am not sure how well it is now compared to the Oracle GraalVM. As a Singular developer you don't really care about your jvm vendor. Maybe if you already have a lot of IBM specific tooling OpenJ9 will be a nice choice.
And also there is a lot of cases where you really don't need or want static typing. Static typing and type systems are great when they helping you but very bad when you are forced to fight them due to compiler problems or bad modeling.
In the end it is all an engineering problem: which amount of your budget you need to spend on proving programm correctness. Cost/benefit and all of that.
Static typing and unit tests don't make your codebases great, safe and supportable. Thinking and understanding your usecases, decomplecting problems and some future planning wins.
I am very very skeptic about this whole DORA org and approach and adoption. I have a greatest respect to the DevOps philosophy, but from DORA I only got a baseless/faceless metrics. Maybe it is also Google driving it that gives me additional rejection impulses. I am quite skeptic at what and how Google does and this colors my perception of all thing it produces.
Why can't there be a normal P2P project handling exchange of information and/or modern fiat in the same way (Something like Paypal, but transactions have no middleman)?
Firstly because money is a physical, cultural and social construct so it can't be changed on purely informational basis. Someone still need to share burden of proof and they want to be compensated for the labor. So until we get a StarTrek replicators (mean we remove need to spend money on basic need and survuval of whole human race) this is a state we are in.
In short blockchain and crypto don't solve any real world problem. It solves problem that it itself creates.
I can sell you amazing knife and it will fix the world hunger, but only if you can buy bread and sharpen the knife. This is crypto sell point in the nutshell.
Blockchain is little different as it solves the problem of provable chain of evidence, but it is not economically viable due costs needed to run it for organisations that require it. Any problem that blockchain can solve require that all information for this will be stored on blockchain. And physical object information is not stored on blockchain, so data input errors/malpractice is still the problem and this reduce blockchain effectiveness to the basically zero.
Dan Olson aka foldablehuman have an amazing series of video essays regarding all the crypto blockchain and web3 scam running around. I highly recommend them. It just a sea of information regarding current state of things with crypto/blockchain business.
If you are using BitBucket Cloud you can create pr rules to include people into Review based on files change. And then you can create a user for a bot to monitor those PRs using standard BB notification emails. Of course if there is not much PRs bot is Overkill and human will be enough.
You can always "just" create a static script that pulls repo check diff for files and email people if something is found. This way you don't link your solution to the git cloud offering.
@muhanga
@programming.dev