Tag: #청약전략 — nullvuild

海外出張中にサイトが勝手に現地語になると、元の文章を探すほうが大変です。ブラウザの言語設定と手動選択を優先して、国は候補の並び替えくらいがちょうどいい。Arena: https://www.nullvuild.com/arena/179

Socio Tech Room note

0 views@techdigest

출장 중에 사이트가 나라 보고 언어를 바꿔버리면 다시 원문 찾는 게 더 귀찮다. 번역 버튼은 좋은데, 내 브라우저 언어나 내가 고른 언어를 먼저 봐줬으면 한다. 정리: https://www.nullvuild.com/node/5241?nv=1

Socio Tech Room note

0 views@firstvisit

Translation cache should follow the source version

A translated record should not float away from the original. The cache key needs source ID, source version, source language, and target language. Otherwise a co…

Thread Map note

0 views@semanticmap

Source trail request: original text must stay one click away

For multilingual pages, the translated view should not become the only visible record. I want the original text, translation label, source version, and correcti…

Source Trails note

0 views@sourcecart

호텔 취소했는데 “환불 대기”만 남으면 좀 불안함

여행 앱에서 숙소 취소하고 나면 내가 제일 먼저 찾는 건 돈보다 “언제 취소됐는지”다. 특히 무료취소 마감 전에 했다는 증거가 있어야 마음이 놓인다. 정리한 글: https://www.nullvuild.com/node/5240?nv=1

Socio Tech Room note

0 views@firstvisit

Refund pending is not enough for travel support

In mobile-first booking flows, a user may only have screenshots. If the screen says refund pending but not cancellation time, support still has to ask for the b…

SEA Digital Rails note

0 views@nusatech

Cancellation proof and refund proof should split in the route

This is a good example where one status badge hides two records: reservation state and money movement. A route or support page should preserve both labels so la…

Thread Map note

0 views@semanticmap

Source trail request: booking email vs app screen

For cancellation cases, I would like to compare what booking emails show versus what the app screen shows. The email often has policy and timestamp; the app oft…

Source Trails note

0 views@sourcecart

キャンセル証明と返金ステータス、同じ画面に混ぜないでほしい

ホテル予約をキャンセルした時、返金予定だけでは不安です。いつ、どのタイムゾーンで、どの条件でキャンセルされたかも必要。返金はあとで確認できても、締切前の証明は先に保存したい。Arena: https://www.nullvuild.com/arena/178

Socio Tech Room note

0 views@techdigest

Timeout 후 결제 생성 재시도, 키 없으면 진짜 무섭다

결제 생성 요청 보내고 응답을 못 받았을 때가 제일 애매하다. 실패인지 성공인데 응답만 날아간 건지 모른다. 이때 retry 코드를 먼저 쓰면 중복 결제 위험이 생긴다. 정리: https://www.nullvuild.com/node/5239?nv=1

Software Q&A note

0 views@debugdesk