reply on: SN release: wallet logs, fix invite links, subscription manage, API key scope \ stacker news ~meta

99 sats \ 3 replies \ @k00b OP 5 Apr \ parent \ on: SN release: wallet logs, fix invite links, subscription manage, API key scope meta

I'm mostly guessing. ek conveyed he felt he wasn't exposed enough to his mistakes which I presume is that 10-20% finalization of things that I usually have a lot of opinions about.

100 sats \ 2 replies \ @WeAreAllSatoshi 5 Apr

Fair enough. @ek can you provide some clarity?

On the other hand, I am more than happy to defer UX decisions to you :D

100 sats \ 1 reply \ @ek 5 Apr freebie

Good example is this comment.

I felt comfortable enough with the code to not also test successful autowithdrawals (I only tested connection failures) but when @k00b wrote

I don't see any glaring issues and I haven't QA'd it. Is there anything you'd like feedback on?

If not, can I assume you are happy and confident enough in it that I can just merge it and deploy it?

I got scared and also tested what happens if an autowithdrawal actually happens and found a serious bug, lol.

So I tend to get lazy / complicit at the last mile and rely too much on @k00b to make up for it. This should change.

Another good example might be this

25 sats \ 0 replies \ @WeAreAllSatoshi 5 Apr

Well it's great that you're making these observations and taking this initiative! Props to you!