Seems to me that very few people can check all three of those boxes.
111 karma · joined May 27, 2012
zentraal {at} gmail
@siebo on twitter and insta
Seems to me that very few people can check all three of those boxes.
btw, I love https://sysadmincasts.com and would love to see more sites like it.
I disagree with point #1 about working a "normal schedule". I think being able to adapt to work when the mood strikes (or doesn't) is one of the best things about being a digital nomad. Personally, I schedule my times in blocks which are different on different days, and adapt to the needs of clients, team, my current timezone offset, and personal schedule (classes, dinners, etc.). I also move things around as I go, to adjust to things like nice weather to go out, having a slow morning, or being inspired to do something. Note that while I am flexible, I'm also very disciplined about scheduling work time, averaging 75hr weeks.
I also disagree with #6. I've certainly experienced being happier in some countries (and cities) than others. I think one of the great things about being a DN, is experiencing daily life (not vacation life) in different countries, and learning where you are the happiest in different areas of your life. Then, unlike a vacationer, who sadly has to return home, a DN has the ability to extend their time in those places.
When I think of happiness, I also think of fulfillment which is more granular than just being "happy". There are different areas where you can experience fulfillment: family, friends, hobbies, work, lifestyle. Different locations provide these in differing ratios. In one place, you may be happy that you can be near family, while in that place, you miss surfing. One of the great things about being a DN, is that you don't have to chose only one of these. You can mix them in various intervals. Last year, I spent a lot of time with family and friends in a bunch of different countries, made two trips to Peru, two trips to Japan, and a bunch of time all over Europe and Mexico. I would say I'm happier for it, than if I had been in any one place, even if I spent the whole year in one of my favorite cities.
I thought I was going to agree with #3, but agreed less the more I read of his description. To me, it's much more about being around specific selected people that I care about: family, friends, clients, partners... Also beneficial are places where I connect with people based on shared interest. Meeting random people in cafes is nice sometimes, and the universe does throw interesting people into the mix, but for me it's about more than just, "having people around is always better".
Of everything here, #8 (Invest in yourself) is the strongest. The risk-adjusted return of informed and ongoing self-investment is phenomenal.
(source: Digital Nomad since '06. 10-20 countries/year while running multiple successful service and product businesses)
Being able to navigate this "command-line bullshittery" is one of the basic filters for people in the software development and CS research fields. Personally, I've hired people with CS degrees who could barely do basic operations in the shell. I'm often the person on a software team, who is coaching the less-skilled members on getting their environments and tools set up.
Rather than reduce these friction points, I think we need to encourage a culture where people learn to solve their own problems, or at least read the docs and try to do a bit more before thowing up their hands and asking for someone else to solve their problem.
Prepare well beforehand, with specific examples of things that are happening. Help the founders connect the dots about how this situation is putting your company at a disadvantage in terms of attracting talent and building your team. Good developers have lots of options, and will certainly view this sort of thing as a negative indication of your company culture. This will leave you with B-listers at best. For a small company, this is poison, as it creates a negative effect that quickly compounds.
At the same time that you raise this issue with the founders, have some potential solutions to offer. This could involve having a technical staff member review correspondence and web-postings from these folks. It could involve some ongoing coaching for these hiring coordinators. It could involve replacing them. A decent level of technical understanding and an attitude of wanting to improve should really be a baseline for anyone in this role. It's not an exaggeration to say that the amateur behavior of these folks could drive your company into the ground.
I'm also working with a Fortune 100 client to develop an intranet platform for them. It's an awesome project, and I wish I could say more than that, but we're under a rather restrictive NDA. We're working on producing a case study, and getting it approved by their legal department. We've done some other large intranet projects before (federal agencies and global NGOs) so this is another strong niche for us.
I often encourage developers to combine their technical skills with another domain-specific specialty to create a compelling value proposition. It's great to be a "Javascript developer" or "Python developer" but with that positioning, you are easily commoditized. By combining technical skills with a non-technical specialty you are much more resistant to commoditization.
Find a good doctor or naturopath and get professional support.
Absent of that you're just guessing.
I have two pieces of advice for you. The first is: Develop your sales and storytelling ability. The second is: Follow the money.
One of the challenges of selling yourself as a SysAdmin, is that when you do your job properly, things just work. This makes you almost invisible... Generally, people only "notice" SysAdmins, when something is broken: builds fail, a website slows down, a web service times out, mail starts bouncing, etc. To improve your trajectory, you need to relentlessly train your ability to show the key people in your organization your successes. (As a side benefit, having this information organized is also highly useful to you if you decide to shop for a new gig.) Think constantly about how to tell the stories of your work, aided by stats and ideally, quotes from colleagues. I recommend reading the Phoenix Project for a bit of insight about this. There's a character in that story (Brent) who is the go-to devOps pro, but most people in the organization don't realize how critical he is. This is a classical failure in self-marketing. The company would literally fall apart if he wasn't there, and yet he's working longer hours than anyone else and probably getting paid about the same as his much less competent colleagues.
You also need to follow the money. In every business, there are certain things that terrify senior management. Perhaps it's failing a SOX or audit or losing PCI compliance. Maybe it's a breach of customer or patient data. Perhaps it's having a key piece of infrastructure go offline. Move yourself as close as you can to those business-critical elements. One of my projects is maintaining a scheduling application for some very expensive medical imaging equipment for a federal agency. These machines price out in the millions of dollars, and are shared by more than 30 research groups. Having even one of them go offline represents a huge cost to the organization. When I interviewed with them, there was basically zero push-back about price or hourly rate. All they cared about was how reliably I could keep these machines online. If I pitch them on some ideas which will improve reliability or disaster response, they are, of course, very receptive. That is the kind of infrastructure you want to be close to. Figure out what keeps your CxO's up at night, and find ways to make those problems go away.
Depending on your organization, these two things will improve your trajectory to a point. You may start to reach a ceiling in terms of income, as they may have a mental block with paying a sysadmin above, say, $150k/yr. If you want to reach higher, you may need to make the jump to working for your self. At that point, you probably want to find a better term for what you do than "SysAdmin". Labels such as "Scalability Specialst", "BI Consultant", or "Critical Infrastructure First Responder" might help you with positioning in such a way to command more respect and income for your efforts.
Avoid passive, low-value channels like putting cards on bulletin boards. You need to go into an active sales process for securing high-value clients.
Looking at your site, I'm thinking the kind of clients you're going after probably don't care about the technologies you use. Instead, organize the content more around the business problems that you solve for your clients.
See if you can find a particular type of business/client is undeserved. Get one of them as a client, and write up a good case study or white paper. Then book appointments with as many of those types of businesses as you can, tell them the story of how you helped the first client, and how you can do the same for them. If they don't sign up with you on the first meeting, follow up consistently.
With an approach like this, you're coming in as an expert and you have much more altitude in the transaction than if you're being hired as a "Wordpress theme integrator" or somesuch.
You're in Chicago, you're not going to run out of leads. You need to start booking as many sales appointments as you possibly can. Put a lot of practice into how you tell your story. Practice answering common questions. Video yourself doing this, review including your voice, tempo, etc. Consider getting sales and/or speaking coaching.
Call design and communications agencies in your area to let them know you're available. Some agencies often bring in freelancers to supplement their teams when demand is high. (For these folks, your technology lists might be slightly more interesting.)
Invest continuously in building your own network, including people who are not your potential clients. Make sure they understand what you do well enough to recommend you within their network when appropriate. Consider offering a referral percentage to people with good networks who refer clients to you.
I recommend instead to think about what your ideal situation is, and then invest your energy in creating/achieving that. Make it something compelling enough that you'll put in the massive amount of effort to make it happen.
Hearing other peoples ideal work situations might be a source of ideas, but ultimately, it's up to you to decide what's important to you.
Personally, my list includes: high income, respectful clients, choice of languages and technologies, working on things that matter, getting paid to learn new technologies, smart colleagues, good process, autonomy, time freedom, location freedom, ability to bring in team members I select, low bureaucracy, low politics, and working with contacts high on the org chart.
As far as my physical work environment, I'm pretty flexible. I've worked from coworking spaces, cafes, Regus locations, hotels, 3/5/7-series BMWs, airplanes, restaurants, E/S-class Mercedes', dinner tables, beaches, boats, train stations, and occasionally even the offices of my clients. I do my best to pay attention to ergonomics and environmental quality. I carry an inflatable lumbar pillow and a yoga mat and like workspaces free of fluorescent lighting and chemical scents.
A couple tips to ensure your ongoing success in the market:
1) Continuously invest in your skills 2) Constantly improve your storytelling and communication skills 3) Network relentlessly. Make it habitual. Follow up. Care. 4) Be fanatical about taking care of your clients 5) Nourish your sense of curiosity about technology. Eliminate toxic projects or jobs which feel like they are burning you out. 6) Have a value proposition beyond "I can write code". Develop some domain/industry-specific expertise.
For each of the above, apply the 10X Rule. Execute at a level of 10 times the effort that you originally think you'll need.
If you're looking for an employee-style relationship: To work legally, you'll want to find a Dutch company to sponsor you so that you can get a work permit. Another option is to get hired in the states by a MNC and get transferred.
Personally, I elected create a corporation in California, hire myself, and get Dutch clients for our company. I travel enough that I can make due with the 90 day out of every 6-months visa-free Schengen option. Dutch companies tend to like to do business with other culturally Dutch companies. (Technology companies, however, are generally much more progressive in this regard.) If you go this route, definitely have a Dutch-language web presence and consider having a Dutch-speaking sales person as these will work wonders.
Also, if you're into cars, one very cool thing about NL and neighboring Germany is that you can rent proper german cars, like M3's and Porsche turbos. In NL the traffic can be a bit crowded and you have to watch out for the camera boxes (Gatso's). I recommend taking the ICE train over to Düsseldorf. They have a very nice selection of cars at the DÜS airport and the A3 is great for some autobahn therapy.
Let me know if there's anything or anyone I can help you get connected with in NL.
1) qualify the lead 2) quantify value 3) reduce risk
First, are you confident that the folks raising these price objections are qualified customers?
Assuming they are qualified customers, usually price objections come from either not building and quantifying value earlier in the sales process, or from the clients perception of risk.
Talk with them to discover the relevant numbers. E.g. how much time do employees or consultants spend on this task now? What is the average fully loaded salary or hourly rate? Or, how much are they spending on other products which will no longer be needed with your offering? Do the math for them, show them the savings.
The other factor to focus on is reducing risk. You could be showing them significant gains/savings, but they are discounting those based on their perceived risk premium, because they may not be confident in your ability to deliver those results. Think about ways you can attack that perceived risk. Can you offer a guarantee or warranty? Include interviews or case studies with other customers which illustrate their savings?
That said, if you don't mind the overhead, you can achieve a similar outcome running a virtual machine inside of OS X.
Seems like ping time is missing, which is critical to me. Also, would be great to have some measure of ping/speed/reliability over time, either via repeated automated testing or guest ratings.
I've often stayed at places which had decent speed, but unserviceable ping times, which is really a buzzkill for VoIP and online meetings.
Another issue is wifi that is fast, but unreliable. I've experienced a lot of that since moving to Brazil; Internet that just goes missing at intervals too regular to ignore.
Would be interesting if a widely-used service like speedtest.net would enable some tagging of IP addresses to pool results, so you could see the aggregated results for a given hotel over time.
You made something cool. Someone else saw the immense potential in you. Maybe you should do the same :)
If you make something truly useful, and market yourself well, you're going to make a lot of cash. That's a key form of recognition for your work. It's up to you how you manifest that into social proof or other rewards. Get yourself a nice car or two, eat at the restaurants you like, get a decent watch. Give it away. Date models. Whatever makes you happy.
Or don't. That's one of the best things about the type of work that we do. Apart from the absolute upper echelon or startup founders, VCs, etc. we're able to go about our lives unnoticed and unperturbed. If you're Apple employee #17, or founder of a $100k/mo SaaS startup, chances are you can go about your life largely undisturbed.
Anyhow, looking for recognition from others is a pretty empty thing. Having the resources to live the life you want... That's much more compelling to me. I'll pass on the cheering, free drinks, and groupies. Being able to jump a flight anywhere in the world tomorrow, huck an M5 around the Nordschleife, or lay around Punta del Este for weeks. I'll take freedom and lifestyle over attention and recognition.
I thought there would actually be some innovative techniques in this article.
Perhaps a better title would be, "A review of python debuggers".
To make you more marketable to potential clients, I'd recommend focusing on some skills that are complimentary to programming. That may include domain-specific knowledge of a particular type of client you want to work with (e.g. bioscience, healthcare, local government) or it may include things like usability, SEO, or lead-generation. Find the profit centers in your clients business and find a way to get as close to those as possible. Learn the language they use to describe their work and make sure you use the same vocabulary when speaking with them.
Work for clients in high cost-of-living countries. Spend your time in lower cost-of-living countries.
Instant lifestyle upgrade.
Aren't you a little old to still be using PHP? ;)