imroot
Started out as a kanban style of system where anyone could request that we re-order cleaning supplies at a Makerspace. Has evolved to tagging assets and maintaining those assets and I'm working on adding ESP32 based device control to enable/disable devices through those QR codes.
Kroger should have pulled a Wal-Mart and turned to their shrink-heavy stores in urban centers to online fulfillment only -- basically only their delivery drivers can retrieve items for an order, and everything's shopped by an associate (Look south of the MicroCenter in Dallas if you want to see what one looks like: it still has the Murphy USA in the parking lot and is basically an unbranded walmart building with 'driver' and 'associate' entrances -- and then deployed the robotics there: less retail space, more online/fulfillment capacity (have humans grab produce and custom sliced/packed items, robots pick the dry goods), and while you lose some cashier jobs, you'll probably have net improvement in terms of time waiting to be picked.
Grocer A: They built their cloud strategy with Azure in mind. Microsoft partnered up with them early on at the C-Level and grocer was given a metric fuck-ton of free services to help build and identify the proper cloud strategy for all of their 2500-ish stores.
Luxury Goods Retailer B: Moved from a Data Center to AWS, since that's where our corporate IT partner recommended we go to. C-level leadership tried to get some fake products removed from Amazon.com, Amazon.com said no, we were given the green light to spend "...whatever needed to be spent" to get us off of AWS and over to Google Cloud as quickly as possible.
It's been my experience that the Google Cloud sales reps will always usually reach out after money raising announcements and other acquisition events just to let you know that they're there and please spend money with them. It was never "Don't fund your competitor," it was always, "we're google, our tech works, they're not going to sunset google cloud, our support sucks, use our partner."
Just about every web server these days supports ACME -- some natively, some via scripts, and you can set up your own internal CA using something like step-ca that speaks ACME if you don't want your certs going out to the transparency log.
The last few companies I've worked at had no http behind the scenes -- everything, including service-to-service communications was handled via https. It's a hard requirement for just about everything financial, healthcare, and sensitive these days.
https://www.federalreserve.gov/paymentsystems/regii-about.ht...
In 2018, my mom had her left knee and right knee done at the same time...and they had her up walking the halls of the floor the next day and was back at home less than 72 hours after her surgery, and she's walking just fine these days without any assistance.
For some of our bugs given on h1, we openly say, "Hey, we need to see a POC in order to get this to be triaged." We do not provide test accounts for H1 users, so, if they exploit someone's instance, we'll not only take the amount that the customer paid off of their renewal price, we'll also pay the bounty hunter.
I hope your daughter is doing better and is adapting to a normal life post-transplant.
Large, global retailer with their tech center in the Midwest. Most of the long term goals were presented from Italy, most of my coworkers were there because they had been there for 10-20 years and were zombies waiting on their package so that the company could move their jobs to Dallas.
Ironically enough, when I relocated to Dallas, one of their recruiters reached out. I think it was one of the few times that I’ve ever been unprofessional and was laughing as I hung up the phone to a recruiter.
My job at the time gave me three days off before calling to ask me if I could come back to work, with my boss and HR on the line telling me that they also 'gave me the weekend' (since I was on-call when it happened). When I said that I needed more time away in order to deal with it, they fired me, then begged me to come back as a contractor a few months later.
I was so upset over the things that happened that I turned them down -- it wasn't what I wanted to do and it wasn't how I wanted to be treated: I'm much more selective about where I'm working at these days.
One of the (ham) radio clubs that I'm a member of does this as a benefit for the group, and it's something that's nice to have: I can give my wife a radio and not worry about what she may or may not say if we have to take two separate cars when we road trip.
I've been meaning to do the process myself, but, I haven't had the time (and honestly, I'd want someone else to do the paperwork for me so I'm more likely to pay someone else to do it) recently, but, this might be the thing that prompts me to go and do it.
73 de K4IMW/WQZQ315
Location: Dallas Texas/Miami Florida (Winter), Chicago Illinois (Summer)
Remote: Yes
Willing to relocate: Only to mild climates with mild winters.
Technologies: Terraform/Consul/Nomad/Vault/Ansible/Chef/Puppet/k8s/helm (DevOps), Information Security (CISSP, CKA, CKS, AWS Certified Security - Specialty)
Résumé/CV: ianwilson.org
Email: hi at the above domain
Have 25+ years of technology experience including 10+ years of FedRamp (Mixture of DevOps and Security), 8 years of Healthcare Information DevOps/Security, and 8 years of Endpoint/Cloud/Application security. Former technology consultant for a big 4, led large, geographically diverse technical teams and delivered global solutions for travel, QSR, and retail industries.Reach out; if I'm not a good fit, I know plenty of folks who are looking who I could refer you to.
-- 0: https://www.apple.com/newsroom/2021/09/apple-announces-first...
The Fraud and Trust VP seemed shocked when I mentioned to her that it wasn't a big deal for me, and that I had my personal accounts with a credit union.
It's been 4+ years. I've written the money off.
You can set up your access controllers for anti-passback, but, most folks don't, because companies don't want to pay the costs associated for an 'in' reader and and 'out' reader and implement that level of security.
While Prisoners have no expectations of privacy, most do not know that all of their calls are listened to, transcribed, and shared with prison officials. There is some speech-to-text sentiment analysis that will prioritize a call that has certain phrases spoken.
It's just...a mess.
When I was a public defender, I had prosecutors and jail staff hint to me about things that were said during the calls. A few years later, they had to drop the charges in a few cases because it was discovered and reported that the calls between attorneys and clients were being monitored and recorded.
It was well known in the wireless industry that ATT collected and kept the most data on all of the carriers: 7 years for text metadata, "7 years" for call history (I put that in quotations because it was rumored that ATT kept them indefinitely, but, there were technical limitations for restoring data that far back), and 7 years for the contents of the text messages themselves. Verizon was up there as well, but, I don't remember specifics.
The carrier that I worked with kept only 3 days content of the actual messages, 28 days for the text message metadata, and 28 days for the call records for their enforcement database, but, they could get calling records and sms envelope information for billing back 7 years, and at the time, we had to implement sharding at the database layer that maintained the warrant database due to the amount of traffic that we were receiving from the calling systems and the amount of queries/data that we were sending out, in near realtime, to law enforcement users who paid $10,000/month for access to that data.
AT&T wasn't storing this data out of the kindness of their heart, it was a (probably small) revenue stream for them.
Once at Singly, in 2010-ish. Was a contractor for about 4 months, they brought me on full time, and I spent about a year there, left to go to one of the big 4 consulting companies, spent 7 years there.
The second was at Greenhouse (the ATS) in 2021 -- was there until Jan of this year.
I've been using Softcover to publish my runbooks for years.
When you talk security to most dealerships, it's about protecting the assets that are on their floor plan -- the vehicles -- not necessarily anything else. Most places have tried to take steps that prevent their sales folks from walking out with their customer book, but, that's the extent of most of their information security needs.
--
Did some work for Lowe's Home improvement and their PXE booting thin clients in the early 2000's.
https://github.com/charmbracelet/vhs
I have a gitlab CI job to update my demo .gif's every time I update my application; always ensures that things are up-to-date and provides gif/video recording that I've ran specific commands (perfect for auditors!)
Edit to add:
Whenever I've had issues with one of their products, they literally walked me through disassembling and testing their products on the phone together -- and the staff there working the phones was knowledgeable, kind, and the type of folks you'd hear in the background at their tables/booths at hamvention and other radio-focused events. This isn't just a loss for everyone who uses MFJ, this is going to be felt amongst retailers as well as folks who are in that community. Their products were built well, tested to work, and rock solid: truly generational gear.
reject sixty two thousand four hundred and six records
into a modal with paste disabled and a red background.
You can't fix stupid, even if they're paying customers.