A form letter, email, whatever would be better than what I experienced in my last job hunt. It was silence after silence. Was the rec closed/filled? Am I even in the running or was I rejected early on and now I am just waiting for no reason?
A lot of the companies used automated submission systems, which confirmed they received the resume, but they never sent out a notification that the position was filled/closed/rejected. Just a one line email would have been better than nothing. I feel even that common (and super automatable) courtesy has been lost.
I worked remotely as a consultant for 12 years, before going back to full-time in an office job. The main driving factor for going back was the lack of consistent social interaction. I started my remote career in San Francisco, where I had non-work activities that were very active in the local community for nearly a decade. I was going out regularly and had many close friends. Being in a walkable area with decent public transportation was perfect for ease of social interactions.
I later moved to a city in southern California, which was a more suburban environment. It wasn't walkable, you had to take a car everywhere and I didn't know anyone other than my partner when we first moved here. I now was in a situation where I had to re-establish my social connections without my previous activities (I had stopped being involved a few years before the move) and I also didn't have a work environment where I had also made many social connections over the years.
For the first 5+ years, this was fine, I was able to make a handful of new friends but many of them started moving because of cost of living and starting new families. At this point, I feel like it really started to become determinantal to my mental health. Honestly, it took a long time for me to even notice and admit it was affecting me, but eventually, it was pretty debilitating. This wasn't the only source, but it was a major factor to be sure.
That being said, after being back in the office for 2 years (they have pretty strong no work at home policy) I am ready to go back to remote work. I loved the benefits of remote work but I also now am much more aware of the importance of getting out and finding more social activities to balance this out. Also, I wouldn't go back as a consultant. Having a rotating cast of people you interact with made it much harder to form longer-term social bonds and also there was never dedicated time planned to meet in person at regular intervals, as a lot of remote-first companies do.
I love and really miss the flexibility of my schedule and if I can find an environment that supports stable interactions with people and I continue to re-engage in more social activities outside of work, I would jump back into remote work in a heartbeat.
I have seen a progressive failure with my USB-C and the Plugable TBT3 doc. I never had a problem with it for the first year but now I am having to reboot the laptop regularly because it no longer talks to the display port and plugging/unplugging stops working after a while.
Also, what is up with macbookpro's Bluetooth? Everyone at my office has the 13" and no one can use Bluetooth consistantly. Lost connections, no connections, etc.
Foresee Medical | San Diego, CA | Senior DevOps Engineer | ONSITE
ForeSee Medical is a tech start-up with a legacy management team focusing on improving the patient care landscape. ForeSee engineers develop the next-generation open platform, cognitive processing software solutions that place data in the hands of providers and care teams to empower them to positively influence health outcomes. We’re looking for engineers who bring fresh, progressive ideas and the spirit of innovation as we embark on our journey.
The Senior DevOps Engineer works side by side with engineering, platform, development and operations teams and will be primarily responsible for designing, implementing and automating build, release, deploy, monitoring and configuration activities. The Senior DevOps Engineer is responsible for bridging the gap between development, operations, and infrastructure.
The simple fact that Panasonic sees a (profitable) need for something like their Human Blinkers, it feels more like a cure for the symptom and not the cause.
Yup, AS3 was based completely on the ECMA draft at the time and was a spec implementation. Macromedia then later Adobe had representatives on the W3C board and due to politics, worry about compilation, the lack of "learning to code from reading source" and from what I recall concern for backward compatibility the draft was killed. Harmony was the next draft and it eventually evolved into ES5.