65 karma · joined April 13, 2013
Socials: - github.com/raman325 ---
[ my public key: https://keybase.io/raman; my proof: https://keybase.io/raman/sigs/YUDnkn3-2jJWO_zExUZCu0kXpCAtKwAbERwYb6NpkFc ]
1. Teenagers can build cool things too! We need more kids interested in STEM and females are underrepresented, so these "puff" pieces are great inspiration for the next kid who happens to come across it.
2. All that was needed for her solution was a cheap FLIR camera connected to an iPhone 6, meaning you don't have to be rich/VC funded to experiment with hardware solutions.
This is Smithsonian Magazine, not the Wall Street Journal. I say bring on more stories like this!
I wrote the operating procedures for performing a backhaul upgrade in preparation for the launch of LTE. The upgrade was being performed on our primary routers which all traffic traversed. The operation had been performed several times successfully, but after the last implementation before the issue, I was informed that a couple of the lines were wrong (they had extra arguments). I did a find and replace all, shot the document off to the next team, and went about my day. The technician who was doing the upgrade called me on the afternoon of the upgrade (it was a Sunday) and asked if any of the initial steps were disruptive as he wanted to get started on the prep work ahead of the maintenance window. I said no and he proceeded. Mind you, this was also during the World Cup so I was out at a bar with my friends and not paying attention to my phone. About two hours later I looked at my phone and had multiple missed calls and voicemails from him, so I immediately ran to the MTSO. Turns out my find and replace changed some commands - the end result was that instead of adding additional VLANs to in-use interfaces, it replaced all of them with the new ones, which weren't carrying any traffic.
The fix was simple, we had failover routers and at some point after he couldn't get in touch with me the technician reached out to one of my peers who quickly told him to failover. He should have known to do that but he was also panicking. I called my boss and told him what happened and that it was my fault (and I genuinely believed it was. I wrote the bad procedure AND I approved activities outside of the maintenance window), and he told me to be at the office with the technician first thing in the morning the next day.
I couldn't sleep that night, this was early on in my career and I thought it was over. But that meeting ended up being one of the most transformative moments of my career. My boss's boss, a director, quoted the FAA's ethos of how a good system should have checks and balances, and if a mistake happens, the system is at fault, not any individual. We walked through the play by play and identified multiple opportunities to both avoid the issue that arose and to resolve the issue more quickly. We came up with an action plan as to how to make sure our "system" was more mistake proof for next time, and that was that.
That meeting has always stuck with me, and I always remind myself of that conversation whenever things at work don't go as planned. There is almost always something in the system that can be improved to account for human error, which should be expected.
EDIT: The other comment has a better source
[0] https://appdaemon.readthedocs.io/en/latest/ [1] https://github.com/home-assistant/appdaemon [2] https://diyfuturism.com/index.php/2017/11/26/the-open-source... [3] https://nodered.org/
Contrast that with every Android OS based manufacturer: 1) The majority of them were companies that had been working with cellular providers for years already. They probably already had agreements in place with providers about how things would go (bloatware, extensive testing, etc.). 2) They were competing with each other for market share because the OS wasn't a differentiating factor (their bloatware/cosmetic overhauls were weak attempts to establish software differentiation). 3) Verizon made a big investment in Android with the Droid line, providing marketing, branding, etc. Any other manufacturers that were building Android phones had to compete with these devices and had to market on their own. Verizon had all of the cards.
It's slowly changing, but it boils down to: 1) Manufacturers trying to compete (they often add plenty of their own bloatware) 2) Verizon using a model they're familiar with from the feature phone era and manufacturers being used to the carriers having control
EDIT: edited for clarity
Verizon may slow down updates to consumer devices, but I always felt like it was for good reason.
EDIT: should note i am using iTerm on a Mac
The pessimist in me wonders if this is simply a brilliant strategy by Facebook to acquire the 4.5 billion people who aren't currently connected without having to compete with others. What's different between this and getting rid of net neutrality aside from side stepping the government entirely and doing it under the premise of helping the world become a better place?
The realist in me guesses that they probably see both sides and consider it a win/win scenario. I mean, wouldn't you?