If you say BDD, do you mean Cucumber/Gherkin? I wanted to talk to someone doing this in real life since a long time ago.

1. No, but that‘s a good point as well. I didn‘t think of that yet. My point was that you cannot unthink the implementation. So you will write tests instead of executable specs. Using specs to lead the design of the implementation is way more powerful. Less confirmation bias involved.

3. Correct. But too agressive stubbing may leave your tests vulnerable to not detecting implementation changes. As well as too heavy mocks.

4. Then you’re disciplined.

An example:

a = 5

b = 2

expect(calc(a,b)).to equal(5 * 2)

I often fall into this trap, because I want the test to be very readable.

Some more thoughts specifically about writing them tests first:

- You might have written the wrong expectation because you’re post-rationalizing the implementation.

- Is coverage branch coverage or line coverage? How often is each line/branch covered?

- Do you properly mock/stub? Is your mock reimplementing the implementation? Is your stub skipping functional parts?

- Did you reimplement parts of the implementation in your tests? This sacrifices resiliency, let‘s say if the factory seed data changes, then all your tests suddenly behave unexpededly.

- Do you have too many tests? Since tests are part of your software design they may also hinder you. Especially if you‘re going up higher in the testing pyramid.

I like if someone takes the time to summarize discussions from social media and compiles them into readable prose.

There‘s a kids show called „papa troll“.

It’s me.

Daughter doesn‘t approve.

Oh man. This looks so forged. And I’m very sure it‘s not. Because genuinly forging is the system‘s job.

nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl I changed my mind about retweets. Yours are precious.

I‘d like if I‘d be able to allow only you to show me reposts.

Found some good old #brauzeugen stout hidden far back in the fridge. From #rapperswil to the #beerchain!

I like where this is going. A bit like early facebook. How you not degenerate into people finding out how to play this (and end up with later facebook)?

Are DIDs in general a good or a bad idea?

I miss Google Inbox

I actually stopped zapping when Apple made nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 stop easy zapping. I would start again if it was as easy as it was for that short timeframe.

I dreamed that nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft invited me to a job interview. He had a cruise ship made into a yacht. We had a chat and then he said I should make a code review of nos.lol 🤷‍♂️

Found a sportif #condor bike brother.

I rather think the dispenser is forced into a situation where it can react only. I think long-term central bank planning is a myth. It‘s reactive to economical threats, so it‘s only „flattening the curve“ and not causing the problem.

I don‘t think that fiat money is broken per-se. It‘s more that institutions and people are escaping it via debt and banks.

This was always the case, like for example renaissance aristocracy traded their privilege to draft military for inner city housing in Italian city states.

Today it‘s just easier to do those trades because digital is fast and global.

I also think SEO marketing bullshit

You lie them AIs down onto the couch and let them tell you about their dreams. But you do it often and with statistics.

When I hear „AI Expert“ I think „Machine Psychologist“.

This is a #Brauzeugen Golden Ale. A bit too hoppy-bitter (young?) for my ale taste, but still worthy of the Sunday afternoon #beerchain.