engineering.yesware.comYesware Engineering and Product – Building stuff
engineering.yesware.com Profile
engineering.yesware.com
Maindomain:yesware.com
Title:Yesware Engineering and Product – Building stuff
Description:Skip to content Yesware Engineering and Product Building stuff Menu and widgets Yesware About Us Careers Search for: Recent Posts How To Transition From Being an In-Office to Remote Programmer How to
Discover engineering.yesware.com website stats, rating, details and status online.Use our online tools to find owner and admin contact info. Find out where is server located.Read and write reviews or vote to improve it ranking. Check alliedvsaxis duplicates with related css, domain relations, most used words, social networks references. Go to regular site
engineering.yesware.com Information
Website / Domain: |
engineering.yesware.com |
HomePage size: | 131.253 KB |
Page Load Time: | 0.349431 Seconds |
Website IP Address: |
23.185.0.1 |
Isp Server: |
- |
engineering.yesware.com Ip Information
Ip Country: |
- |
City Name: |
- |
Latitude: |
0 |
Longitude: |
0 |
engineering.yesware.com Keywords accounting
engineering.yesware.com Httpheader
Connection: keep-alive |
Content-Length: 39349 |
Cache-Control: public, max-age=600 |
Content-Encoding: gzip |
Content-Type: text/html; charset=UTF-8 |
Link: https://engineering.yesware.com/wp-json/; rel="https://api.w.org/" |
Server: nginx |
X-Pantheon-Styx-Hostname: styx-fe1-a-789d66bff9-pbj96 |
X-Styx-Req-Id: 291d0c1f-3e70-11ea-bff0-e2708acee5bb |
Date: Fri, 24 Jan 2020 06:10:03 GMT |
X-Served-By: cache-mdw17364-MDW, cache-sjc10044-SJC |
X-Cache: MISS, MISS |
X-Cache-Hits: 0, 0 |
X-Timer: S1579846203.494265,VS0,VE312 |
Vary: Accept-Encoding, Cookie, Cookie |
Age: 0 |
Accept-Ranges: bytes |
Via: 1.1 varnish |
engineering.yesware.com Meta Info
charset="utf-8"/ |
content="width=device-width" name="viewport"/ |
content="WordPress 4.5.2" name="generator" |
23.185.0.1 Domains
engineering.yesware.com Similar Website
Domain |
WebSite Title |
engineering.yesware.com | Yesware Engineering and Product – Building stuff |
app.yesware.com | Sign In - Yesware |
help.yesware.com | Yesware Help Center |
ihlapi.tumblr.com | Posts the Best Offers,Funny Stuff and Free Stuff |
idontgetthislifething.tumblr.com | Posts the Best Offers,Funny Stuff and Free Stuff |
in-wonderland-blame-the-nargles.tumblr.com | Posts the Best Offers,Funny Stuff and Free Stuff |
yesware.com | Yesware | Easiest to Use Sales Software |
ae.utexas.edu | Dept of Aerospace Engineering & Engineering Mechanics - Cockrell School of Engineering, The Universi |
api.listia.com | Give & Get Free Stuff - Listia.com Auctions for Free Stuff |
listia.com | Give & Get Free Stuff - Listia.com Auctions for Free Stuff |
freestufftimes.com | Free Stuff Times • Free stuff, samples, and everything free posted all day long! |
tsti.net | Astronautical Engineering | Space Systems Engineering | Systems Engineering Courses - TSTI |
allsingaporestuff.com | All Singapore Stuff – Real Singapore News – From Tuas to Changi, All Singapore Stuff brings you Real |
bme.cmu.edu | Biomedical Engineering - Biomedical Engineering - College of Engineering - Carnegie Mellon U |
cpe.virginia.edu | Computer Engineering Program | University of Virginia School of Engineering and Applied Science |
engineering.yesware.com Traffic Sources Chart
engineering.yesware.com Alexa Rank History Chart
engineering.yesware.com Html To Plain Text
Skip to content Yesware Engineering and Product Building stuff Menu and widgets Yesware About Us Careers Search for: Recent Posts How To Transition From Being an In-Office to Remote Programmer How to use Kafka Streams How Yesware uses analytics Automated UI Testing for Native Windows Applications Introducing YetiLogger Recent Comments Archives October 2018 October 2017 July 2016 June 2016 April 2016 March 2016 February 2016 January 2016 December 2015 Categories Uncategorized How To Transition From Being an In-Office to Remote Programmer Note: This article was originally posted to my personal Medium account, which you can find at https://medium.com/@jcquinlan.dev “person facing laptop inside room” by Muhammad Raufan Yusup on Unsplash My name is James, and I’m a Software Engineer at a company called Yesware , based in Boston. Yesware is the fourth job I’ve had in which I’m paid to write code, but it’s the third time now that I’ve transitioned from being an in-office employee to a remote one. Since I’ve handled this transition a few times now, in varying degrees of complexity/difficulty, I figured I probably have at least a few words for anyone else looking to begin working remotely. But first, a warning: survivorship bias guarantees that your mileage may vary with regard to anything I say here. Switching to a remote position has worked for me in the past, but that in no way means it will work for anyone else in the same ways. You don’t often see articles entitled “How I Completely Failed to Work Remotely and Botched My Dream Gig”, but I’m sure there are many cases of folks doing exactly that. That would actually probably be a more helpful article, so consider this an open invitation for someone to write it as a response. Also, I talk about my place of work in this article a fair bit, but I’d like to state clearly that I wasn’t asked to, or otherwise encouraged to at all. Any reference I make to my employer is included only because I see it as relevant or helpful to others, so as to get an idea of how a company might support its employees. Why Remote? This is a question I won’t dwell on too much because there are endless blogs, listicles, and books¹ written on the subject. Remote work is fantastic for some personality types as it affords much more freedom. Some folks just enjoy being able to move, to be able to go where their friends/family/bucket-lists take them. Being able to take your job where you want to go is, in my opinion, less stressful than having to factor in finding another one if you decide to leave. Simply put, it resolves any dichotomies between having a job you enjoy, and anything else you want to do. You can have your cake and eat it too². Why Not? Remote work can be much harder depending on a myriad of details related to one’s personality, the nature of their work, their company’s culture, etc. Are you the type of person who can self-regulate and ensure you’re allowing for extended periods of focus, wherever you are? Is the work you’re doing something that can be done without any coworkers immediately available? Is the company you work for willing to put in the extra effort to ensure you feel connected and valued? Do you have some misconception that remote work means doing any less work? Do you have a spouse or other close family member who this will affect? Is the Wifi going to be any good where you’ll be based? I’ll leave you to ruminate on those questions, but there are many reasons that being remote wouldn’t be a good fit. They each warrant honest discussion with yourself, those close to you, and your employer. How To Tell Your Company Eventually, you’ll need to broach the subject with your boss, and while there are various ways to do this, there is only one I recommend. The worst way I ever went about it featured me telling my boss that I was moving in two weeks, no ifs-ands-or-buts about it. I was essentially abruptly quitting, without really offering to discuss the matter. I knew I had to go, and I was ready to leave my job to make that happen, but I feel as though I had cornered my boss. After my spiel (“I grew up here, I’m ready to leave, I need to do this”, etc.), he told me to just work from Boston, and that there was no reason I couldn’t stay on the team while working elsewhere. This was incredibly surprising to me, and something I hadn’t considered. I ended up taking the offer. A few weeks later I was in Boston working the same job as before, and paying significantly more in rent. This method felt wrong for a few reasons. Namely, I didn’t bring the idea up as a conversation, and I went in defensively, expecting the worst. Also, I didn’t value my role in the job enough! I didn’t expect that I was valued enough by my company to warrant letting me move and stay on the team, and that was unfair to myself. By the next time I had to have the same conversation, I was already 9 months into my tenure at Yesware. I had an opportunity to move to Spain with a friend, but I valued my job an enormous amount. I was simply learning and growing too much to justify leaving³. Since I felt more comfortable at Yesware than any previous company I’ve worked at, I figured I’d just talk to my boss about the opportunity openly. I wrote him an email one morning stating plainly that I had an opportunity to move to Spain in the upcoming Fall, and I wanted to talk about if that would be possible while still working for Yesware. I dug up the original email, and the sentence that best captures its spirit was “I just want to open this dialogue to see what is and isn’t possible, without any expectations.” My boss and I immediately had a short 1-on-1 meeting to talk about the idea further, and we agreed that, while it was unlikely to happen, we could at least see what it would take to work. If there were no legal reasons we couldn’t do it, and the company felt confident that my work wouldn’t suffer, we felt as though it should be fine. Over the next few months, we discussed what it would take to demonstrate that I can handle remote work, and that our team can. We organized a month long experiment where our engineering team of ~6 people would be remote every day, and I used this as an opportunity to show that I can be perfectly productive (often times much more so) while at home. Eventually, once we had clarified everything with the Yesware legal team, I was made aware that I could work from Europe if I so chose. “brown concrete buildings” by Alasdair Elmes on Unsplash The most important thing I learned from this is that discussing big changes like this requires one to be honest, upfront, and realistic. By making sure Yesware knew I wouldn’t leave the company if they said no, I helped make the process easier for them to consider. We also put in the extra work to make sure it would go over smoothly by making sure the team would be comfortable with me being remote, and by proving that our productivity wasn’t jeopardized. What It Actually Takes To Work Remotely I’d like to take a moment to reiterate my warning message at the beginning of this article, in which I claim that just because this works for me, it doesn’t mean it will work for anyone else. You’ve been warned. The biggest struggles I expect one to encounter when starting to work remotely are, in no particular order, managing to keep a normal schedule, creating a space conducive to focusing, and feeling connected to your team. They are also 3 sides to the same geometrically-impossible coin. For me, managing to succeed in one of those areas makes succeeding in the others easier. Here are some ways I do that, and some ways that my team supports me: Stick to a routine. Pick a chunk (or chunks) of time every day to focus on work. While a remote schedule often means some degree of freedom when choosing when to work, we can get a lot out of maintaining some sort of normal hours. I tend to stick roughly to working hours EST (which is 3pm to 11pm for me in Spain), but I also know I’m most focused first thing ...
engineering.yesware.com Whois
"domain_name": [
"YESWARE.COM",
"yesware.com"
],
"registrar": "NAMECHEAP INC",
"whois_server": "whois.namecheap.com",
"referral_url": null,
"updated_date": [
"2018-08-31 19:20:14",
"2018-08-31 19:20:14.280000"
],
"creation_date": "2004-12-23 19:06:11",
"expiration_date": "2027-12-23 19:06:11",
"name_servers": [
"NS1.P10.DYNECT.NET",
"NS2.P10.DYNECT.NET",
"NS3.P10.DYNECT.NET",
"NS4.P10.DYNECT.NET",
"ns1.p10.dynect.net",
"ns3.p10.dynect.net",
"ns2.p10.dynect.net",
"ns4.p10.dynect.net"
],
"status": "clientTransferProhibited https://icann.org/epp#clientTransferProhibited",
"emails": [
"abuse@namecheap.com",
"cashman@yesware.com"
],
"dnssec": "unsigned",
"name": "Cashman Andrus",
"org": null,
"address": "109 Kingston St 5th floor",
"city": "Boston",
"state": "MA",
"zipcode": "02111",
"country": "US"