HN user

treebeard5440

38 karma

DevSecOps Software Engineer | go | python

Posts5
Comments45
View on HN

Way below what you’d make at FAANG is absolutely correct. Salaries are not competitive with top-tier tech companies. Not everyone wants to work at FAANG though. Depending on what you value though the lower salary can be offset by some of the other benefits. Work life balance tends to be really good - rarely do I ever go over 40 hours a week but if I do I get paid overtime even though I’m salaried. You can also usually arrange to work a flexible schedule like 4/10’s (10 hrs a day M-Th and every Friday off) or 9/80’s (9 hours a day, 8 on the working Friday and every other Friday off). 401K and medical benefits are also very good. Job security for engineers tends to be high - especially compared to FAANG with their recent series of layoffs. Even if FAANG is your ultimate goal, working for a few years at a defense contractor will not hurt your chances of future employment there.

My main focus is in Embedded Systems Software and it’s something I’m really passionate about.

Not entirely what you’re asking but if you decide to go the job route try applying at all of the major defense contractors (Boeing, Lockheed, Northrop, Raytheon, etc). I work for one and the embedded software skillset is highly desired and hard to hire for. You will likely have to be okay with relocation and working onsite in a classified environment at least part of the time but the job prospects should be much better than tech companies and the work very applicable to your focus

I agree with “does it work for me, then it’s a success” to a certain extent. I am really happy with my project, it does what I needed it to do, and my company allowed me to open-source it. If that was all that happened I would still consider my project a success. What has been really enjoyable for me, however, is working with contributors and seeing developers use the tool. So I feel like - for me at least - there has to be more than just building and releasing it.

Github Action to use the config-file-validator (https://github.com/Boeing/config-file-validator) to recursively scan the directory structure of a repo for config files and validate their syntax as part of a CI/CD pipeline.

This is useful as a quick quality gate in your CI pipeline to validate that a syntax error was not introduced in the latest commit. Currently XML, JSON, YAML, INI, and TOML are supported with CSV, HCL, and Plist coming in the next release.

Here's how to add it to your existing workflow: https://github.com/kehoecj/validate-configs-action/tree/main...