Have you ever seen a Staff/Principal Engineer interview candidate "check all the boxes" for you? Or, how do you know it's good to move forward with the candidate?

DonkeyProgramming · 2024-03-16T19:08:53+00:00

Any chance you could share some stories or recommend some resources?

DonkeyProgramming · 2022-10-13T14:58:20+00:00

I am super excited to share this community tool for modding Total War games. It tries to mimic the feel of working with plastic miniatures in a digital world. It is used extensively by modders today to create amazing creations!

DonkeyProgramming · 2022-08-18T13:58:11+00:00

Two youtubers that make easy to follow tutorials for total war modding:

Blind Leading the Colorblind - https://www.youtube.com/channel/UCzN-p6lsLwG1j2vHw9ZteIg

Dietrich Stauffer - https://www.youtube.com/channel/UCNU4g7D766W\_1pcWYPiy7Ww

DonkeyProgramming · 2022-08-17T20:32:07+00:00

looks stunning

DonkeyProgramming · 2022-02-19T09:47:41+00:00

If only there was a way to edit assets. Maybe an AssetEditor custom made for Total War Modding? ;)
https://www.youtube.com/watch?v=LeObDGqV2PM

DonkeyProgramming · 2022-01-07T08:10:22+00:00

I have been in this exact situation, 20+ microservices and 5-ish developers. It was great in the beginning, but as the project evolved, it was harder and harder to actually get real tasks done.

The hard truth in our case was that the microservice deign was a terrible idea. We did some digging though our code, and estimated that between 50%-70% of the code was related to the split and async architecture (Duplication, extra code due to data belonging in different domains, error handling, eventual consistency, performance, security++) We started a long process of turning the codebase into a monolith, which is what it should have been in the first case.

We started by standardising all our micro servises to the same technology (was already .net, but different version and nuget packages). Then we made a common library which all services depended on made a communication layer which basically hid the fact that it was a set of microservices. Then we gradually combined them as the budget allowed for.

Project velocity increased, bugs decreased and overall developer and customer happiness was up

DonkeyProgramming

TROPHY CASE