Heads up with modern git you can now just use git clone --recursive and it will clone all sub modules automatically.

Weird the keyboard didn’t work but glad the double tap did! It’s definitely clutch

The irony is they always seem to have 0 comments lol, so much for sparking discussion.

iOS dev here, especially when using Swift, supporting older OS’s greatly restricts which new Swift features you can use. Especially any OS lower than iOS 15.

Give the fact that the vast, and I mean like 95% or more, of iOS users update to the latest iOS version within months of release and over 99% of users are on at least the previous iOS version, it’s preferable to start a new app on the latest iOS version possible.

Unfortunately that means older (usually 5+ years) devices get left out, but with small volunteer dev teams or solo devs it makes practical sense.

Yeah the ssh-agent was something I didn’t know I wanted until they added it. Now it’s so nice not having to generate new ssh keys and update all my severs and VMs every time I set up a new machine, and if/when I need to rotate keys, I only have to update one.

I was an Ubuntu user for many years, mostly out of inertia. I used it on all my servers and used Ubuntu or Mint for desktop usage. Once they started pushing Snap hard, I finally switched to Debian on all my servers and it's been great. For my PC at home where I dual boot Windows 11 and Linux, I switched from Mint to Manjaro as I didn't want to use anything based on Ubuntu anymore and I wanted something with all the latest packages (and hardcore reliability/stability is less of a concern) so Debian was out, but Arch seemed like a pain to get set up. I have a feeling I'll end up moving from Manjaro to Arch eventually just like I did from Ubuntu to Debian, but for now it's working for my needs.

The second is exactly how I do it. Keeps everything separate so easy to move individual services to another host if needed. Easy to restart a single service without taking them all down. Keeps everything neat and organized (IMO).

The last time I updated my resume, I took a bit of a different approach to formatting it that I think worked really well. Instead of the standard sections, I wrote it in prose where I basically list each job and wrote a couple of short paragraphs describing what I worked on and things like if/when I was promoted (as in some companies I had multiple titles as I was promoted up). Having been on the hiring-people side more often than the getting-hired side, I find it much easier to read than a big list of bullet points and a (IMO useless) "list of technologies I know" section.

To answer your question of where I put it, yes I put it as another "job" in my experience section. So after my startup folded, I was working on one of my personal projects (an iOS app that's in the App Store that I previously worked on as my job as an indie developer and had picked back up). In this case I modernized it to properly support the latest iOS versions and devices and started porting it from Objective-C to Swift.

This worked out great as I had essentially no gap in my resume since I started working on it again right after I stopped working on the startup. So even though I wasn't getting paid, it showed I was working on something at least (and in this case, something on the appropriate level since I was rearchitecting the code).

Here's a part of that section as a reference:

I approached the project as a senior engineer cleaning up and modernizing code written years ago by a junior — who happened to be me. Within a few weeks I was able to fix all of the core issues preventing its use on iOS 14, modernize the UI, and remove all deprecated APIs (some going all the way back to iOS 3).

In addition, I've been working on a major re-engineering of the data model, porting the entire app from outdated Objective-C to modern Swift 5, and beginning to add new user facing features allowed by the new data model.

I also linked to the GitHub page so they could see the work I did.

As for your question about when a project crosses into resume territory, I would argue any non-trivial project is fine. Even if it's a new project you start from scratch, I think as long as it's the type of work your would be doing if you were hired (in my case I was doing architecture work, etc) or even if say I had started a non-trivial project in a new language I didn't know just to learn it (let's say I started a non-trivial Rust project or something) I think it would also be fine. And I don't think it matters if you've finished it, in progress work is fine as long as it's on Github so they can review it. It's really up to you, but I think the point is just to show you continued to work at your "level" and/or continued to learn it's fine.

This is all just my opinion both from having used it successfully in my own resume and from having been part of the hiring process of many developers, but I can at least say I didn't get any negative feedback about it and I did get the job. This was with a full 6 month "gap" after ending my last position.

My Github username is the same as this username so you can see my projects there if you want (the one I'm referencing here is called iSub), and I'm happy to DM you my resume if you want to see it as it contains personal information I'd rather not share publicly like my phone number (though I guess I could redact it and just post a link, this profile isn't exactly meant to be private or I would have used a different username).

Hope that helps!

I’m genuinely interested in reading this blog post but looks like you forgot to link it

Oh my home NAS I started this way and it worked great. I only bought an HBA card because I needed more ports. Your mobo probably exposes your SATA controller as a PCI-E device that can be used via pass through in a VM. In my case I booted Proxmox off of NVME drive and passed my SATA controller to a Debian VM where I just use simple NFS and Samba for sharing and SnapRAID for drive parity (but TrueNas should work just as well).

I had zero issues with it and when I upgraded to an HBA card I just switched the drives to those ports and switched the PCIE device I was passing through and everything just worked (helps I always mount using partition UUIDs).

Sweet I’m gonna check this out! So far I’ve been doing everything from ssh terminals on my phone/laptop using some bash aliases/functions I wrote to simplify some stuff like downloading whole channels based on a json config file, downloading videos using my preferred flags, etc. I was planning to eventually build something around it, but if this meets my needs or I can modify it to do so, it would save a bunch of time.

Sorry I wasn’t trying to be a dick, I re-read my comment and realize I kind of was haha. Honestly I think for your use case, AGPL makes the most sense. You get the openness you’re looking for while also protecting your business more than MIT by preventing other companies from taking your code and hosting their own version without every contributing back their modifications.