Tangentially related: I'm tempted to buy call options ahead of Amazon's earnings in late April, because they will probably generate millions of extra profit from people that couldn't get through the steps to migrate off of IPv4.
Although looking at their latest earnings numbers [0], even $100M more will only marginally affect the net profit. Hm...
Given that AWS will start charging for IPv4 addresses starting Feb 1, I thought this guide would help people that need to migrate their EC2 instances to IPv6
Navvable | Founding Software Engineer | Full Time (Visa Ok) | San Francisco Bay Area (Hybrid)
Navvable is a venture-backed startup, building modern workflow SaaS for US immigration law firms. Immigration attorneys today are badly in need of better software, because their existing solutions require many time-consuming processes such as manual and duplicate data entry. Our goal is to become the single piece of software powering their entire practices, and streamline the day-to-day tasks to increase efficiency and improve client experience.
We are currently rounding out the founding team of engineers to develop our MVP. As a founding engineer, you will have the opportunity to build an impactful B2B SaaS product from the ground up, and along the way significantly influence both the engineering directions as well as the company culture.
Tech stack: TypeScript/React/Next.js/Go/Python (we are flexible with frontend, backend, or fullstack roles)
Navvable | Founding Software Engineer | Full Time (Visa Ok) | San Francisco Bay Area (Hybrid)
Navvable is a venture-backed startup, building modern workflow SaaS for US immigration law practices. Immigration attorneys today are badly in need of better software, because their existing solutions require many inefficient processes such as manual and duplicate data entry. As a founding engineer, you will work with the founders and prospective customers to develop our MVP, and along the way significantly influence both the engineering directions as well as the company culture.
Navvable | Founding Software Engineer | Full Time (Visa Ok) | San Francisco Bay Area (Hybrid)
Navvable is a venture-backed startup, building modern workflow SaaS for US immigration law practices. Immigration attorneys today are badly in need of better software, because their existing solutions require many inefficient processes such as manual and duplicate data entry. As a founding engineer, you will work with the founders and prospective customers to develop our MVP, and along the way significantly influence both the engineering directions as well as the company culture.
Tech stack: TypeScript/React for frontend, Python/Django (with type hints) for backend
Yes, I definitely am much descriptive for the config file on my personal computer. The configs I'm recommending here is more for ephemeral machines that you are using just to look at files (such as sshing into a VM that was created to run integration tests). For those cases, being able to quickly type something into the .vimrc and improve your experience is nice.
I once had to connect to machines regularly where I did not have a home directory. This happened so often that I wrote a wrapper to log in:
It would log into the remote machine using Expect, then it would send a command to the remote end that tested whether a home directory already existed. If so, it spawned a new shell in it. Otherwise it created a "home directory" in /tmp, pulled a tarball from a server, and extracted it into the "home directory". Then it spawned a new shell there.
Depending on how often it happens, you could also have a separate command that does the initial setup, and then call that as required.
I guess I don't see a lot of situations where I use systems so casually that I don't have config options set. Even when I was managing a bunch of systems I would push out the same config on them all.
One scenario I could see this fitting is when having to connect to some docker container and test a change on the fly.
That's a bit naughty but sometimes needed to prove something useful.
In that case you've got an effemeral file system, and probably had to install Vim in the first place, knowing that that when you close the container all will be forgotten.
Ofcourse in that situation you probably don't need to disable the Vim swap files, so that's one less thing to changet the defaults on.
I often use Busybox for that kind of thing as you're usually missing other useful OS stuff and its little Vi clone is usually enough.
