SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-software engineer who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-software engineer who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-software engineer who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
As someone who has used Bevy in the past, that was my reading as well. It is an incredible tool, but some of the things mentioned in the article like the gnarly function signature and constant migrations are known issues that stop a lot of people from using it. That's not even to mention the strict ECS requirement if your game doesn't work well around it. Here is a good reddit thread I remember reading about some more difficulties other people had with Bevy:
SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-software engineer who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
So happy to read this because I don't see it mentioned often enough.
I have a ErgoDox EZ, and I still prefer using my Framework 13 (with Kanata![0]) because having my thumbs navigate the trackpad is so convenient even with a keyboard-driven setup.
SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-software engineer who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-SWE who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
>The City was among America’s premier trains, a luxury streamliner that could hit 110 miles per hour while white-jacketed waiters balanced trays of cocktails
I wonder how passengers back then would have imagined rail travel today, 75 years later (aside from the life-threatening storms, of course). The Overland Route is now freight-only, and the closest equivalent, the California Zephyr, takes about 52 hours to make the journey this train did in just 40!
More on topic, I was surprised to read:
> When the steam generators’ water tanks ran dry, heat disappeared, too.
Weren't there surrounded by frozen water? Is there any reason snow couldn't be used in an emergency to heat the train?
Good point, but I was more talking about distros designed for a smooth day-to-day experience. A user would probably want something like SquashFS (to save space on the SD card) and ZRAM (to conserve RAM) since all their files would be living there.
RAMFS is a genius idea. That solves most of the SD card health and speed issues without needing to get a whole hard drive. I know Puppy[0] and MX Linux[1] were made to run like that too.
SEEKING WORK | Boston, MA USA | REMOTE | Technical Copywriter
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-SWE who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
My solution for this was switching careers. I found that anyone hiring engineers wanted someone doing 40 hours a week at least, which makes sense since you have to have such a large mental model to build a system. Content and copy writing on the other hand is much more flexible because the unit of work is so much smaller. Any content marketing manager would love a real engineer to write for their blog once a week and help sell their product. Then just stack up different clients until you reach whatever weekly load you are comfortable with.
That's how I read it too? And while the documentation has lots of examples, I get a bit lost in that you start with some form of JSON file, which consumes either YAML or HTML files, who in turn can consume Markdown files. It doesn't seem (from my reading!) to have the level of abstraction I would expect from a SSG.
- $130k is a large amount, why would your contracts save such a huge payment until the end instead of spreading it out over the six months of the engagement?
- Is apsis really just doing nothing and waiting? I get the contract might not have a clause on late fees or whatever, but that doesn't stop them from paying a lawyer ~$200 to send a letter demanding payment. That should get any large company moving.
- How many contracts has apsis closed because this is a somewhat standard practice at large companies in the sense that they will take any float time they can get. I remember one company my dad worked with in construction would mail checks the slowest way possible just to get a week of float!
There is really too much here to summarize. It's a 150 page guide to technical writing, as in the writing of technical manuals, using a variety of board game rulebooks the author wrote as examples. I am only 15 pages in, but so far I have to say the boardgame approach with all its images makes this a much more fun read then any other guide I have seen for writing manuals. It is just about writing though. I don't think you'd gain much if you are just a general boardgame fan looking for a behind-the-scenes look at rulebook creation (if that is even something people look for??)
SEEKING WORK | Boston, MA USA | REMOTE | Technical Content Writer
Have a new product launching soon? Or some content you have been meaning to get to?
Hi, I'm Jeremy, an ex-SWE who writes about tech. After helping build a cloud storage unicorn, I got into teaching developers and found out that I'm pretty good at making complicated stuff make sense. Now I write technical content mainly for SaaS companies. Happy to also chat about open-source, cloud architecture, or where tech content is heading.
- Blog Writing: I turn complex tech topics into articles people actually want to read. Whether it's deep dives for your engineering audience or guides that won't scare off beginners.
- Topic Planning: Not sure what to write about? I look deep into what your users care about and map out content that'll actually help them while helping you grow.
- SEO That Makes Sense: No keyword stuffing here - just strategic writing that helps you show up when people Google their problems.
Feel free to reach out if you need anything written: [email protected]
Also message me if you want to discuss anything interesting about Rust, Linux, or other FOSS software!