4140tm

I just found out about Lagom from this blog post and it's exactly what I have been looking for.

All other Python options I've seen feel too involved or leak too much into your code. Lagom seems to balance everything just right.

Thank you!

How do you know what testing/designing practices all "important" software projects use?

Do you expect it to be advertised?

A few years back I saw something similar where subreddits were presented like a tree, based on topics (and popularity, I think). Made it easy to drill down to interesting niche subreddits.

Haven't been able to find it since.

You are skipping a step there - it's red -> green -> refactor

As for "tactical programming instead of strategic design" - that's entirely up to the developer and how they approach the problem. if you are prone to neglecting the design you'll do it any way. If anything, (actually) practicing TDD would force you to come up with better design.

People in general are bad in dealing with nuance. And there is enough of it in these type of books for some to overheat.

It's not a huge investment to learn. At the same time it's very valuable. I would prepare for CKAD first and do CKA only if relevant.

The main reason for not working NGINX examples is because there are two NGINX ingress controllers - one by NGINX and one maintained by k8s. Real fun if one does not know this upfront. Ingress api version changes don't help much, of course

You don't need precise specs to practice TDD. If you have idea of the code you need to write, you can write the test for it beforehand - no matter how often someone might change their mind about the app.

Doing so would actually make your life a lot easier when it's time to alter functionality, because now you have well tested and testable code. Code that is written to be tested is usually a lot easier to reason about, to change and extend.

If you do it in concise manner and test behavior rather than implementation, what you previously thought of overhead will actually speed you up.

If no one knows whether the code is correct a generated test could easily do more harm than good.

If no one is able/willing to refactor the code into understandable and testable bits, there's not much left to guarantee the correctness of it.

> The domain is fintech

What you describe is the opposite of what I expect from (modern) fintech.

* no tests

* god method with no proper documentation/requirements

* no one actually understanding the function deciding how much money to send! Isn't this one of the core functionalities of fintech products?

Every year I go to the pharmacy and buy a flu vaccine. I can then get the shot in a way convenient for me.

Do you think there's any relation between the naming of whitelist/blacklist and skin color? I certainly don't. Colors and their associations exist beyond racial identity.

Also, what is the problem in calling the relationship between two processes (one fully controlling the other) master-slave? It's a perfectly suitable analogy and does not have anything to do with any one person's ethnicity or history. I'll go a step further and say that looking at this whole thing entirely in the context of the mistreatment of african americans is unfair to people all over the world who have a history of slavery - as other posters have noted, there are plenty examples of that for people of all races. This is not exclusive to one group of people and no one can claim ownership of the word.

I find it bizarre how many arguments on the topic are just of the type "microservices are the cure" / "microservices are cancer" - no reflection on specific domains and context.

It's very much like the case with unit tests.

What is a unit? How small is micro? These two questions on their own are subject of debates of religious proportions.

I'm not a huge fan of putting client-side rendering on everything, but I still feel it's unfair and shallow to put so much blame on it.

For an app getting more than a couple page views in a session, a SPA solution may provide significant savings on rendering and db queries. Combine that with resource caching and these effects extend to following sessions.

That is, of course, if the app was built with some consideration regarding overall performance. Unfortunately, not too many web developers (both FE and BE) seem to be overly concerned with efficiency.

it does, when you take into account the turnover of existing accurate test methods and their accessibility

Weird. I also use flake8 and the only mismatch between the two has been the default line length of black, which I changed to 79. All is good now.

I have hated every single formatter I've tried, other than Black. It seems to be the only one that's not just trying to put style into PEP8 compliance, but also keep it readable and maintainable.

I'm also curious about the issues you've had with it.

Up until recently I couldn't actually do much with google maps on my phone because I have restricted it from using microphone. An error would pop up on every simple address lookup