AliasVortex

That's awesome! Wishing you both the best!

Lol, it actually kind of is: https://en.wikipedia.org/wiki/Max_Steel

Migrating my laptop to Ubuntu and literally just ran into this with Thunderbird- the profile is in the Snap directory instead of the parent home folder like the docs say.

Echoing the other comment, I loved my Pebble because it was a smartwatch that was a watch first and foremost and everything after that was added to make life easier (rather than to pile on selling points that someone might want but that nobody needs). For example, the thing had a week long battery life (irrc the first gen iWatch had something like less than a day), but even when it hit the bottom 10% of the tank, it turned off non-essentials (like Bluetooth, calendar, customizations, etc) and just kept going on a default watchface. The UI was simple, easy to navigate, and generally useful. Physical buttons meant that I never had to fight with a touchscreen to clear notifications or check my calendar.

Plus the whole thing was stupid customizable. On the software side, the community grew a fairly sizable market for watchfaces to show pretty much whatever suited your fancy (TimeStyle was always one of my favorites, but I was also fond of this Pokemon one). On the hardware side, the watch used a standard 20mm band so you could go as far as to match it to your outfit if you wanted (I had a nice metal band to go with my Steel so I could dress it up for college career fairs (and have my calendar send me a reminder when it was time to duck off to class)).

E3D makes pretty decent stuff and is based out of the UK- it's just annoying and expensive to get ahold of everywhere else (insert generic grumbles about Revo nozzles). Otherwise, I've had good luck with Phaetus nozzles, but I'm not sure that pricing/ availability looks like in the UK.

Lemon it's January.

Why do you print like you're running out of time?

Not the original poster, but it's on the British Museum's channel: https://youtube.com/watch?v=WZskjLq040I

Correct. ASL is fascinating because of how visual it is and just how much you can convey by taking the same sign moving it differently (for example you can describe a rough flight by making the sign for airplane and then bouncing it up and down).

I might also add that in addition to your facial expressions form grammar structures, body language (of which facial expressions are a part) also conveys tone/emphasis. For some concrete examples of how this provides context: the sign for thin becomes anorexic if you suck in your cheeks/ stomach while you make it. Similarly, fat can become obese if you puff out your cheeks and slouch a bit while you make it. Or on a more topical note, the sign for fire is made by wiggling your fingers in an upward motion in front of your chest (visual), the size of your sign sort of describes the size of the fire your talking about, small slow movements might describe the dying embers of a campfire, while larger (pushing towards of out of the area you normally sign in) more frantic movements would be used to describe a miles high inferno.

Well that might explain some things.

Not to throw shade at your company but that process is so backwards that it's no wonder the engineers are sparse on the details. I saw another comment likening software development to a crossword puzzle, which is a pretty good analogy. To further it, changing software once it's done is like trying to swap out a clue/ word once the rest of the puzzle is built. It's theoretically possible, but depending on how the puzzle is designed, it can range from an absurd amount of work to nearly impossible. Given the way you've described the state of things, your engineers are probably low on goodwill to boot.

I've worked on cobbled-together crunch-time hell-projects and the last thing I'd want after getting free would be a random BA coming to me about details that more than likely packed with the project PTSD and would very much like to forget. Doubly so if it's issues that I bought up early in the design/ development process (when they would have been comparatively easy to fix) and was dismissed by the powers that be. I can only speak for myself, but I can only take so much "that's not a priority", "we don't have time for that"/ "we'll see if that becomes a problem in the future and deal with it then" before I throw in the towel, stop keeping track of everything that's wrong, and just bin the entire project as dumper fire run by people who would rather check boxes than make things better.