I don't think leaving tweets up is much of a good idea since they will be fed into grok. Additionally, they made it clear in the TOS that they will sue users for breaking the TOS, so imo it's best to get out of there sooner than later.
I am currently working with RMM and MDM platforms to automate device provisioning. I am passionate about problem-solving and enjoy finding innovative ways to automate processes. I would love to continue working in this space or in a related field where I can leverage my skills.
The first thing I searched for was my favorite graffiti[0]. I always see it while walking the dog. It brought up a lot of false positives like 'mart' and 'part' if they were at an angle or partially obscured.
I also tried searching for Blob Dylan since there always seems to be a bunch of those around, and it only brought up 2–3 results[1].
I'm wanting to transition to an engineering role, but I believe I am missing some of the skills needed for it. I am currently a Senior Windows Systems Administrator. My interests with work are currently around device management and automation, but would love to work in just about any field. I love to learn and am quick to pick up new skills.
Location: New York City
Remote: Yes
Willing to relocate: Maybe
Technologies: Python, PowerShell, Docker, Linux, Git, OSQuery, Kaseya, Jamf, Jumpcloud
Résumé/CV: LinkedIn - https://www.linkedin.com/in/jacob-nichols
Hobbies: Writing, 3D Printing, Electronics
Email: j4ke@omg.lol
I'm a little bit confused about this. I was under the impression that images were dead.[0] What is the advantage of building images and having to deploy them locally either via usb or pxe?
I'm assuming this is for user's machines, but wouldn't it make more sense to use a config management tool?
I'd have to agree. Immutable is great for headless server scenarios but I'd imagine it would be a huge headache as a daily driver for end-user desktop scenarios.
Immutable systems like this are great in a lot of educational setups where a lot of different students work at potentially many different workstations while always needing access to the same tools and in general having a "unified" experience.
Wow, that reminds me of the soundwagon[0]. I always wanted one, but they are known as 'record/vinyl killers' as they essentially destory the record as it plays.
I have a script I run using Alfred on macOS that creates a daily template page with some default sections for a few different brain dumps. I have a to-do list that gets updated based on the previous items. It removes any completed tasks from previous days and carries over tasks that weren't completed.
I have a section for some daily writing where I try to do some stream-of-consciousness.
Another section is for meeting and calls where I tend to write what people are saying to cement it better in my mind.
I will also use these daily pages to create bigger notes.
Example: [[Raspberry_Pi]] is an overall header, so I may open it up and either add general notes to it, or go to the projects section and add another link to something like [[pico-projects]] or something like that.
Adding certain tags to these pages will automatically move them to different folders depending on how they are tagged. Daily, projects, pi, etc. will move items to their respective folders.
Basically my daily pages are places where I dump stuff I don't care to look for again and use specific pages to track everything else I care about and will revisit as needed.
