I’m new to Disney Lorcana and built a tool to learn the game by brute force.InkStats lets you paste in two decks and have AI vs AI play hundreds of games. It then shows: Matchup win rates with confidence intervals Game length / play–draw split “Key cards” – how much a deck’s win rate changes when a specific card is seen or in the opener The bots are simple but consistent: a rules engine plus...
I wonder if Swift on the backend has picked up, or if it's a hobby / experiment. If you have any tale of Swift being used in production, would love to know more.
Vital provides a single API for all your wearables data. We standardise your healthcare data across various wearables sources and give you a cleaned and compliant API to use.
Apply here: https://vital-api.notion.site/Senior-Backend-Engineer-97c197...
I was reading today a small rant by GeePaw (https://twitter.com/GeePawHill/status/1558159024520151041) and made me think that I don't feel I ever a) did TDD the "right way" b) ever found a good resource on how to do it. For people that to it, what would you recommend to your younger self?
There's a lot of advise given on Twitter, Reddit and personal blogs. At face value, these seem reasonable things, but once tried out they don't work at all.
We are in the process of improving our documentation for our users. I am not experienced at all in the Python ecosystem, so I would like to get some idea/suggestions on how people are generating docs from python comments. The idea is to then put the output on a website, so people can access publicly.
Different people want different things. A lot of people want to code and to be left alone. A lot of other people don't. They want to feel they are progressing towards something. Good frameworks usually state: we consider you as a senior if you are doing X & Y consistently. This helps people aligning their actions/work with a level. The group of people that usually don't care about this things, might start doing so, when their title (e.g. "Software Engineer") lacks the "senior" keyword and they are applying for a senior role elsewhere. This might seem nitpicking, but you would be surprised how many people don't even pass the first screening because they don't have the "senior" prefix. In bigger companies monetary compensation is assigned according to the person's level. In smaller companies, not so much. Everyone has the same title, and people can have significantly different salaries. A good career framework makes it very clear to everyone that if you want to earn between X and Y you need to be at a particular level.
As for the framework itself, I am big fan of giving examples. Say for instance on IC3: "I’m able to navigate ambiguity and remain resilient through ups and downs". I would love if they assigned a somewhat real example: "I am able to complete tasks, even when the acceptance criteria is not 100% clear.". They did well with the separation of the different functions: QA, Software Eng, Security Eng & Reliability Eng. A lot of places bundle some of these together and leave people scratching their head.