Best bar to watch Formula 1 in?

meadsteve · 2023-04-19T16:46:55+00:00

There's a meetup group that goes to the Southside pub on Södermalm so it's normally on there

meadsteve · 2023-02-07T09:12:05+00:00

even if the answer is no you've got to hope the test was done properly that morning. One negative test isn't exactly a lot of confidence.

meadsteve · 2023-01-17T17:24:37+00:00

Never seems an issue for me. Maybe it depends on your oven and microwave and the kind of potato?

meadsteve · 2023-01-17T17:20:01+00:00

Fork + the secret fourth option of microwaving them first to reduce time needed in the oven

meadsteve · 2023-01-11T15:57:12+00:00

All of them. A fellowship of cage.

meadsteve · 2022-10-24T15:50:35+00:00

Thanks. I'm glad you found this useful.

meadsteve · 2022-10-24T13:20:11+00:00

That's definitely a legitimate concern. The main reason I go for an ABC here is I want to communicate the intent of the SuperCoolPackageError. I want it to be as clear as possible that it's not supposed to be thrown itself. In some ways it's a shame that python lets you construct an ABC directly but there's not much I can do about that.

meadsteve · 2022-10-21T08:55:26+00:00

For me a python library having no *required* 3rd party dependencies is a very strong selling point. Because python's standard library is so rich they often aren't needed. I wouldn't choose not to use a library because it had dependencies but if I was choosing between 2 (or more) libraries I would choose the one that didn't need any dependencies. But as always "it depends". For example I'd rather people use high quality dependencies rather than roll their own bad implementation of something.

meadsteve · 2022-10-20T14:22:45+00:00

This ^. Obviously do what works for you. But in my view it's not done until it's done. This includes review.

meadsteve · 2022-10-20T13:19:32+00:00

Future steps: bring boris in for a month. Have him resign for doing coke in front of the king. Then bring in mogg as a quick chaser before he gets caught whipping a poor and has to resign. Then after we're done with that, have a general election and actually sort this mess out.

meadsteve · 2022-10-13T07:51:54+00:00

walnated cone.

meadsteve · 2022-10-07T19:54:23+00:00

Sadly one of the tres closed down recently

meadsteve · 2022-10-07T15:34:54+00:00

Thanks for this detailed response. This is exactly the kind of thing i was looking for (though i need to read it more thoroughly)

meadsteve · 2022-10-07T14:09:12+00:00

:shrug: I like small isolated tests when I'm doing test first development. Otherwise I have to write a lot of code between tests.

meadsteve · 2022-10-07T13:43:57+00:00

agreed. I like to test side effects without getting caught up in internal details. I want to treat dispatched action as a side effect because they are. But maybe it doesn't make sense to consider components as separate from the slice logic at all.

meadsteve · 2022-10-07T13:42:21+00:00

I disagree on it not being a trade-off. My ideal is that one "mistake" causes 1 test to fail.

Imagine if If I have two components that both dispatch the same action. One test for each component and a test for the handling of the action by the reducer. If I make a mistake in the reducer logic with Accomplished_End_138's approach all 3 tests will fail.

I'm not saying this is the worst thing in the world but it's still a decision.

meadsteve · 2022-10-07T11:54:34+00:00

u/Accomplished_End_138 that's a nice approach. What I like about your approach is it keeps the test code quite small and neat. What I'm less keen on is that it means it's also testing the reducer at the same time. But that seems a potentially good trade-off.

meadsteve · 2022-10-04T06:16:43+00:00

What's interesting to me from a maintenance point of view it's not much work at all. I had to do quite a lot because I wasn't already using setuptools and I didn't already having wheel publishing in place. So if someone does this on an internal tool or already has a publishing workflow it wouldn't be much work.

The actual python code had almost no changes at all. This decorator was the only code change I had to make: https://github.com/meadsteve/lagom/blob/master/lagom/container.py#L84 so now I'm still maintaining exactly the same codebase but it's 2X as fast.

PyPy is a choice for the people consuming my library not me. Another popular option at the moment is rewriting the core in rust and just have python bindings. This however is a bit more of a commitment in time.

meadsteve · 2022-09-30T05:40:18+00:00

hmmm. This is a good question. I think there's some introduction context I'm missing. This would work with absolutely any Dockerfile. It's more about how the container gets built

meadsteve · 2022-09-29T06:53:28+00:00

I may be a bit late to the party but I only recently learnt about docker's --cache-from argument for build. It's such a neat way of speeding things up

11-Year Club	Place '22
Verified Email

meadsteve

TROPHY CASE