Yea but when i inevitably leave this cluster **** i wanted to make a big bonfire. I cant burn a trello !

I’ll check it out though i’m always trying to find software to make me and my team more productive. I’m doing everything for my team in spreadsheets now because that just was the easiest way to get them using something.

You can always burn the laptop with the Trello screen open!

Print out the trello board on giant paper before every standup!

I use iOS notes - which fulfills my two requirements - that it be instantly synced to all my devices (work mac, home mac, iphone, ipad) and not be in a browser window.

I don't want more than one click to get to it. I don't want to have to remember to save it. I don't want clunky manual or not instant sync. I don't want it in just another chrome tab where it gets lost in the morass. It has to be an app on all devices.

Can Trello do all that?

I have one note for home todo, one for work todo and one for book stuff. Obviously Trello can handle that.

I use trello in the browser, so not sure about its app status on mac. But its in my permanent tab section with gmail (home, work), calendar, and a couple of other staples so that's never bothered me.

I definitely get the appeal of notes (it worked for me for a long time).

Edit: But yeah, it handles the syncing / saving / etc. all very seamlessly.

are email attachments just links to data on some http server or is it somehow involved in the mail protocol? having trouble finding answers on this.

They are typically part of the email body, as separate MIME sections. They aren't part of the "mail protocol" if you mean SMTP or POP3, but how they are encoded/included is part of MIME.

For the most part if you need to create/read MIME messages I'd expect there should be some library you can use, although way back in the day I wrote at least one custom MIME implementation for generating outgoing email. Probably a mistake :P

Also, today I have won a great victory over the forces of darkness, by which I mean Selenium. Let us rejoice and be glad.

Yeah this is basically right. The way the data is encoded is essentially the same as how multi-part form uploads are done in http. In both cases they're just multipart mime docs.

I also wrote a mime encoder back in the day. A feature of mime is that your document has multiple parts, and each part is separated by a unique string that you can choose yourself, it doesn't matter what it is but it should be something that won't show up in the parts themselves.

I was using this library that I'd written myself and I added it to a work project and forgot that the separator string contained the word "penis" until I got a very puzzled bug report from someone who saw it in an error message.

And every version of exchange seems to make the parts bigger, so when migrating to a new server you can see 10-20% increase in mailbox sizes...

Rusty that made me laugh out loud in front of some colleagues hahaha

I found it. My separator was "JerkengineDeluxePenis" with some dashes and equals signs and stuff.

Our test users (some of which are internal business users and not very savvy - nor do we sit near them - so we get mass emails that scare everyone instead) are CONSTANTLY reporting bugs in our react app because we put up a new version of the app and they didn't hit refresh on their browser. Which of course could happen to real users as well.

Has anyone else had to deal with this problem? Should I just put in a timer that refreshes the page once a day or something?

You could put in a call to a (new) api endpoint that returns a version number / build date or such, and if it doesn't match what the front end thinks itself is then pop up a dialog saying to refresh (or just refresh I suppose, but only you know if that could lead to lost work / user annoyance etc.)

Idk what the norm is, but I just read the package Json for the current version and add it to my store. So if it's set in store and behind, I just refresh

This is what I do, and put a red button at the top of the page that says "click here to update software to latest version" when the current loaded version and the api version don't match. I did the button rather than refresh due to it potentially happening to a user while they are in the middle of something and can refresh at their leisure. I put it on a timer to check once an hour.

That would confuse our users (old rich people) to no end. We're probably better off just refreshing.

yeah, true. Most of my stuff is internal and used by employees. What's the worst that can happen? A refresh while they are entering their payment info?

If it was critical to have people on the most current front end isn't the most obvious solution to delete/invalidate their session tokens on upgrade? I.E. they're in some part of the app click something and they have to log in again?

Our app actually rarely goes to the server during the user's session. I load most of the data on login, or lazy-load it right after.

If all the date is loaded where are the errors coming from? Moved/missing assets?

The errors are testers looking for bugs that still aren't fixed - styling things, logic, even sign in since it never refreshes the page, etc. I have to remind the testers hit refresh every time.

Typical conversation is tester starts explaining complicated issue. I interrupt and say hit refresh. Tester continues on. I interrupt again. The finally hear me, hit refresh and go "Heyyy! It worked!". Sigh.

Further complicating things is we had a coupld sign in bugs that you needed to a) hit refresh, then b) sign out and sign in again. If not done in that order the bug persisted for one more round of sign in/sign out.

So even when they finally learned to hit refresh before bugging me, they still needed to sign out and sign in again.

Also we have a highly interactive giving history page with all kinds of sorting and filtering that is mostly all client-side.

Stupid QA is an unsolvable problem.

TBF our QA is a graphic designer, a project manager and a product person.

Haha sounds like me