The film data is way over ambitious. I don’t think blowing a 35mm negative up to 16x20 is “superb.”
How many different subs are you going to repost this to?
I have both. The way Bose handles bluetooth with multiple devices is so awful that I gave up on them and bought the Sony’s. They would probably be fine if you only intend to ever pair them to one device. However, for me, I just never figured out what they were trying to do. I’d turn them on and they’d wake up a sleeping iPad in another room, or closed laptop, and then refuse to connect to my phone (using the phone’s built in Bluetooth menu) until I opened the Bose App to reconfigure them. The last straw was on video calls for work-- they’d randomly re-connect with a random device.
The Sony’s just don’t do that. They don’t wake up random sleeping or idle devices, and if they do connect to the wrong device I can use the OS Bluetooth menus to manually connect them to a given device – rather than opening the app in my phone.
So cool, thanks. As a kid I spent so much time in DEBUG, stepping through DOS’s executables, and especially the Interrupt handlers. It’s so neat to see the actual source code-- way easier to read and follow. I didn’t know it was all written in assembly, from within Debug it sometimes seemed so messy and convoluted that I just assumed more was written in C.
+1-- I’m so impressed by the "reasonably large admin team"s’ thoughtfulness and transparency.
You’ve reposted this six times…
Thank you It’s easy to say but not so easy to believe. You help.
It’s not your fault. Tell someone. You’ll survive.
14 life sentences isn’t “life in jail” in the UK, where murdering 270 people isn’t too much for “compassionate release.”
Ask former coworkers to say how great you are on LinkedIn. :)
Social proof can help.
Hey, don’t be discouraged.
You are a treasure and rare. There are places for folks like you. I hope you can find one where the culture fits you and knows your value.
Until then. You can try to change the culture. But if that’s possible depends on more than I know for your context.
With small teams it’s easier. Demonstrate competence, gain trust of everyone around you, then sell a better tomorrow where … Stuff just works. Faster velocity, more features, fewer bugs, etc.
This is a very valued message in some places, and totally not in others.
I have a feeling that infrastructure/platform/core teams – those making tools for other engs – are probably more naturally aligned to quality and lower defect rates. That may be a direction for you if you aren’t sure where to start aiming towards.
Dang, sorry. Maybe your manager sucks and isn’t teeing you up for it or being clear about it? Or heck maybe your org just sucks.
Is this for interviewing or promotion?
At my org the formal definition is “[demonstrated] ability to lead projects at x scope.” This is how people leaders frame it.
But to individual contributors (engineering track) folks, I think we are looking for:
How to show this when interviewing vs getting promoted is different.
NASA has a paper on how to not poop for days. It’s on the Internet. Before space toilets there was only a space bag with finger scissor/scoop holes. It didn’t work, poop got everywhere. The paper goes into detail about fecal matter being everywhere after early multi-day missions.
So they figured it out. Their system works – I’ve also had my own reasons.
Any significant disability…
https://www.nytimes.com/2008/11/04/world/asia/04iht-doctor.1.17504311.html