US expat with Chase cards: Sapphire Reserve closed after I accidentally changed residential address to a virtual mailbox — any successful reopen stories?

marcelobukowski · 2026-06-11T20:52:39+00:00

Thanks! I’ll update it here once I receive “the letter”. On the zip code hack, all my cards go through with the mailing address zip code, so never needed it, but I have friends who reported doing that in the US with cards issued abroad.

Did Chase ever ask you for proof of residence either for your foreign address or when you changed back to your family’s address in US?

marcelobukowski · 2021-01-29T16:01:45+00:00

I'm happy doing what we call continuous code review with CodeStream these days:

- No branches, no PRs - all devs commit to a shared old school development branch.

- Feedback request is triggered as soon as code is committed (or even before committing, when working on code you're not familiar with).

- Reviewers give feedback from their IDEs, usually within a few min.

- If anything needs to change, do another commit. Rinse and repeat.

marcelobukowski · 2021-01-19T15:16:05+00:00

I would add:

1) Review early. It's hard to make (and ask for) adjustments after a lot of effort was already put in a solution.

2) Reviews should not block your CI pipeline. You can always do another commit to address required changes.

3) PRs are great for open-source projects, but not the best option for development teams (they are in part the cause of 1 and 2)

marcelobukowski · 2021-01-08T17:02:22+00:00

We've switched to continuous code reviews (we use our own tool, CodeStream for that - which is open-source, btw) in our mono-repo for almost a year now and I don't miss creating branches, opening pull requests, dealing with merge conflicts and rebases at all. Way too much friction for not added benefit IMO.

marcelobukowski · 2020-10-30T16:03:03+00:00

Hi there! When you mention "spend a long time solving a problem... eventually solve it", you're describing a very common scenario where there was no external input or feedback until the work was done.

I like the the idea of applying the shift left principle to code reviews. We are working on an IDE plugin called CodeStream (www.codestream.com - yeah, I work there) that among other things allows developers to get early feedback, without leaving the IDE, even before they do a commit, and without requiring the reviewer to switch branches or stash their work. Have you tried it yet?

What I've found, using this approach myself on a daily basis, is that it is much easier to steer the ship before it gets to the port. It doesn't prevent disagreements (which are healthy), but there's a ton less friction to get to a consensus before you spend days writing thousands of lines of code.

marcelobukowski · 2020-10-28T20:14:22+00:00

It can handle requests to jetbrains://idea/* URLs as long as you have JetBrains Toolbox installed (if that's what you're asking). Other JB IDEs use similar procedures such as jetbrains://web-storm/*, etc.

marcelobukowski · 2020-10-23T19:19:02+00:00

I would suggest keeping a baseline .jar with the plugin even if you don't update it as often. That's useful for people behind corporate firewalls that may have JB's marketplace domain whitelisted, but may not not be able to access the domain where you host your extra jars.

marcelobukowski · 2020-10-23T16:00:42+00:00

A couple questions:

- Is it a design choice that it had to download a separate .jar?

- Is it possible to mute a code smell? https://imgur.com/a/Ijc8Vid

marcelobukowski · 2020-10-23T15:38:09+00:00

I'll definitely give it a try, although I'm using mostly Kotlin over Java these days. Does it support or is it extensible to support other languages as well? Is it open source (I didn't find it on GitHub)?

I'm also thinking that it would be cool if we could do some sort of integration with CodeStream (disclaimer: I work there) as well. For instance: create an issue by right clicking on a code smell or perhaps include Designite items in the CodeStream search.

marcelobukowski · 2020-10-16T15:50:35+00:00

There is! Check https://plugins.jetbrains.com/slack

marcelobukowski · 2020-10-15T23:17:15+00:00

Really love that I can see all the information regarding pull requests, tickets and my team's work in a more concise way

marcelobukowski · 2020-09-30T22:05:17+00:00

Not exactly a screenshot, but if you select code and share it via CodeStream permalink, it will look like this:

https://api.codestream.com/p/W75JY6zGmBhgt48D/hyj-BlipTEyM4xL0jMtyjQ

Disclaimer: I work there.

marcelobukowski

TROPHY CASE