Janna Hilferty

I noticed that some people using my Log Grabber script weren't utilizing the results file provided as output. It was familiar to me, but many new users found it cluttered or skipped over it. Jamf Log Grabber now shows results in a much better formatted HTML file for easier viewing and more clear steps on what actions to take. Check out the before and after below. If you haven't tried Jamf Log Grabber for troubleshooting Jamf Pro enrolled MacOS devices, you can get the script here: https://lnkd.in/dYtZRNa7

16

I've seen a lot of bugs. (No, not another cicada post). Software here. Egregious, immediately noticeable bugs. The opposite - those that require 6 concurrent conditions and 6 hairs from your nextdoor neighbor and it still only triggers once a month. (Okay, 7 conditions, 6 hairs...don't split those hairs). A continuum of buggage. Those complicated ones, sans the hyperbole - those are your Zero day issues. Regression testing doesn't find them. A super wily code-reviewing look-at-it-all software QA professional (I know the best one)...might...but probably not. How do we even engineer testing all of the complicated conditions? The interrelationships at runtime? I don't see a lot of talk about "how could we have caught this?" in public for disclosed issues. Most of the fixes for Zero days (those security holes best known because they're patched with updates to software like Google Chrome browser, Apple's ioS, Microsoft Windows) are downplayed. You get "Hey, user, look at these new features you're getting, and in whispered voice, "and security updates." Not familiar with the term? Zero day means a security issue without a patch. When the patch arrives, there's a remedy for the problem. Users often don't APPLY the remedy until much later...its own problem...prolonging the risk of the Zero day issue. Back to my kinda silly example. That's a wicked hard problem to test for. A bunch of concurrent situations that then trigger the problem. But, when the problem's a known issue, it's not hard to re-trigger. And therefore exploit. So what do we do? Other than fixing/patching, and communicating? What else is there to add to this conversation? Sunday thoughts. Sunday thoughts.

13

7 Comments

Corporate IT has no place on the path to production. I see LOTS of portcos that hold onto shortcuts they took when they were small. Corp IT runs Jira, or email goes out through the corporate mail gateway. Call it technical debt if you like, and taking on technical debt makes sense when you're a startup. But when you've made it past that stage, it's time to pay it down. Corporate IT is incredibly valuable. I was the Director of IT before I decided to dedicate my career to production web operations. I knew my CDW rep very well. Corporate IT can handle: corporate email, Salesforce, Tableau, calendaring, Zoom, Dropbox, etc. Corporate IT cannot handle: production SMTP gateways, Jira, Confluence, GitLab, Launch Darkly, Datadog, Cloudbees, etc. I don't care in the slightest which actual vendors you use for these functions. I've seen corporate IT change SCMs to "save money" without any input from engineering and set the entire organization release schedules back by more than 8 months because it turns out that GitHub "runners" have security concerns. People have made changes to corporate email and suddenly customers no longer receive notifications, and no one in engineering knows why. Engineering (including Operations) is where the money is made in a software company, and they need to own the path to production. Think of it in terms of "chain of custody" considering the concern over supply chain attacks. In the chain of custody, we don't just let someone with completely different concerns handle evidence. Why would you? #devops #sre #engineering

63

11 Comments

If your product primarily handles CRUD operations (80-90%), you're better off using HTMX with a monolithic backend server-side rendering framework like Ruby on Rails, Django, Laravel, or CodeIgniter. However, if you're developing a highly interactive application, like a calendar app or a Google Sheets-like experience, frameworks like React, Vue, or Svelte would be the most sensible choice. #WebDevelopment #FullStackDevelopment #BackendDevelopment #HTMX #CRUDOperations #WebFrameworks #RubyOnRails #Django #SoftwareDevelopment #Programming #WebDesign #TechIndustry #DeveloperCommunity #FrontendDevelopment #BackendFrameworks #JavaScriptFrameworks #FrameworkComparison #TechStack #WebAppDevelopment #TechnologyTrends #DeveloperTips #CodingLife #SoftwareEngineering #WebDevTools #TechAdvice #Laravel #CodeIgniter #React #Vue #Svelte

2

With the Texas Data Privacy and Security Act (TDPSA) coming into effect on July 1, 2024 it's forcing companies to quickly pivot to become compliant. A lot of companies still struggle to identify their data since it's now everywhere. If you are struggling to identify and classify your sensitive data let Forcepoint help safeguard your data no matter where it's located. #datasecurity #DSPM #DLP #dataprotection

9

I just saved a SaaS company $7,000/mo in Azure Costs. Steal my step-by-step process… Azure costs were outpacing their MRR. They were losing money on new customers. I spent the first 10 minutes saving them $3000/month. I automated it so they don’t have to spend on me either. Here’s a step-by-step guide I wrote on how to optimize your Azure spend. You’ll get a framework to Azure Savings so you can: 📍Find the Expensive Stuff 📍Analyze Costs Against Utilization 📍Reclaim Spend from Orphaned Resources 📍Identify High Spend with Cost Management Portal ☁️ 📍Optimize Service Configurations to Save $$$ Every Month 𝗪𝗵𝘆 𝘂𝘀𝗲 𝘁𝗵𝗶𝘀? “You can’t fix what you can’t measure.” Implement whats in this guide and I guarantee: → Your bottom line is directly, positively impacted by Azure savings …. one more time… → YOUR BOTTOM LINE IS DIRECTLY, POSITIVELY IMPACTED → Introduction to cross team operationalization via FinOps → Re-allocate saved budget toward better things → Understand which guardrails to implement in your dev/infra process If you aren’t thinking about Azure spend you’re losing and if you are thinking a lot about Azure spend this guide is for you! Comment “Not Today, Azure”, connect with me, and i'll DM you the guide.

12

4 Comments

The most frequent conversation I have with clients are the cuts in their budgets and the increase in demand. Cribl has been the tool to show up time and time again and help client's bottom line. See how nth degree can do this for you and your organization

6

🚀 Leet Code Day 3: Validating Parentheses 🚀 My initial approach: I started by creating a dictionary to map each closing bracket to its matching opening bracket and looped through each character in the string. However, without a way to track the nesting order of brackets, the approach only allowed immediate matching of open-close pairs but failed with nested structures. After a bit of research, I learned that using a stack is ideal for this type of problem! Here’s the key idea: 1️⃣ Push each opening bracket onto the stack. 2️⃣ When encountering a closing bracket, check if it matches the most recent opening bracket on top of the stack. If it does, pop the stack. If not, the string isn’t valid. 3️⃣ Finally, a balanced string means the stack should be empty! #learning #coding #python #datastructures #problemsolving #growth Here’s the code that implements this approach:

1

Going to Blackhat? Meet with John Harmon! He's one of the top voices for anything Security. Executives and security leaders can rely on his expertise.

1

Why claim something in a sales meeting that isn't true? Like no one will check or immediately try to use that feature? Why would they ask if they weren't interested in using that feature? Telling someone something that is not true and having them waste many hours doing config on something that doesn't work is not the way to keep customers, make them happy, and get good reviews... the opposite is likely to happen if the product does not do what you say it will do. Why do they do it? Where I have encountered it, it was mostly due to sales representatives getting bonuses on closed sales, not on successful projects or customer satisfaction. One of the best motivators to stop this kind of behavior is making sales bonuses contingent on the project finishing successfully- it encourages a lot more due diligence, which I think would be beneficial to all involved. Just my opinion.

9

2 Comments

What can you do if your team can’t afford the SSO (single sign-on) tax and doesn’t want to compromise security? I have some thoughts: 🤝 Negotiate for SSO during the buying process. 🔒Use an enterprise password manager (EPM), like 1Password, to secure every single sign-on. To read more on the SSO tax and what your teams need to know read our blog!

4

Watching all of the fallout from the CrowdStrike fiasco got me wondering. How seriously do they treat their QA process/department? When they were doing layoffs, how much of that process/department was impacted? Quality is an afterthought with most companies, a way to tick the box on an audit. Most don’t use their QA team as anything but functional scapegoats. Some companies have done away with QA and adopted ‘hybrid-engineering’ models which will likely blow up in their face someday, as devs don’t generally make good QA and vice-versa. I would be curious to hear from some QA people that were impacted by CrowdStrike layoffs how seriously they and their process were treated. I’m sure the blame will be put on developers and QA, but the real blame should be put on the C-Suite for putting their personal wallets and shareholders before the best interest of their customers and employees. Layoffs are a garbage saving measure.

14

2 Comments

We just had a RIF at Impartner Software. To those of my colleagues who were affected, I'm so sorry. If I haven't reached out to you already, I may not know that you were affected, so please reach out to me. I'm good for any of the items in my list below, as well as resume help if you could use it. For everyone else, resharing one of my previous posts about how you can help those searching for a new job: 1. Like, comment on, and/or reshare any posts they've made about being open to new work. Any of these actions will further the reach of their initial post, as your network will now see those, too. 2. Endorse their skills. On the skill section of their profile, click the endorse button for any skills you can personally attest to. This lets people looking at their profile see not only that this person claims to have the skill, but that others will vouch for them having that skill as well. 3. Write them a recommendation. For anyone you worked closely with, it's easy to write up a recommendation that they can accept and display on their profile page. LinkedIn recommendations aren't expected to be long...usually just a few lines/paragraph long....so you can do this in just a few minutes. Do this by going to their profile and selecting either More > Recommend from the top of the screen or by selecting Recommend [Name] directly from the Recommendations section at the bottom. 4. Let people leverage your network. With getting a new job, it's often about who you know. LinkedIn makes it easy for people applying to a new job to find out who they know that already works at that employer, or who used to work there, or who knows someone who works there, etc. Let your network know that you are willing to make introductions if there is someone they want to connect to--and then of course, follow through, if they do make that request. 5. Connect to all the people you know. This one is a bit indirect and benefits you too, but by connecting to all the people you know on LinkedIn, this helps you in later job searches, but also helps your laid-off coworkers now in knowing who you might be able to help connect them to. 6. Pass on their information to recruiters. If a recruiter reaches out to you about a position you're not interested in, but one of your former coworkers might be, respond and redirect them to that person. What did I miss? Add your thoughts, comments, or other suggestions in the comments. #jobsearch #layoffs #techjobs #linkedin

57

8 Comments

I’ve been a bit sick lately, but I hope to start releasing my next ZIO video course later this week. Until then, here’s a little blog post about logging in ZIO, including creating your own custom log format to get the output to look the way you want it: https://lnkd.in/e_6rB4ej The output from the code looks like this: timestamp | INFO | zio-fiber-249876708 | Basic log message| timestamp | INFO | zio-fiber-249876708 | Info level message | timestamp | WARN | zio-fiber-249876708 | Warning level message | timestamp | ERROR | zio-fiber-249876708 | Error level message | (The ‘timestamp’ field shows the actual date and time, but it’s long, so I omit it here.) #scala #functionalprogramming

16

There are also a couple of 'tap' examples at the end of the blog post, if you want to see how to use them in logging.

6

Every time 10x engineers come up I think of the times I was briefly considered a 10x engineer by management. There are times I have come through and apparently pulled a big, complex solution out of thin air. I say "apparently" because that's what they thought. They didn't see the weeks of preparation and teamwork that went into a sudden, surprising outcome for them. They started expecting miracles every other day or week. This leads to burnout on the developer's part. Managers tend to think that the developer is holding back after this. They refuse to acknowledge the silent work and painstaking little habits that lead to large success. This situation never ends well. If you want 10x engineers it's likely you would not know what to look for, nor would you be able to handle them if you happened to stumble into one.

3

Y'all, I had a short conversation with a developer looking fr work who is deciding whether or not to put up a photo on LinkedIn and social media in general because he's worried people will judge him because he "looks" religious. Folks, this is 2024. We know ignorance is rampant in the world today, especially on college campuses and places where people are supposedly taught critical thinking skills. Hiring managers and HR/recruitment teams, from one hiring manager to another: If you're more concerned about what's on a candidate's head than what's under it, then they're not going to want to work for you anyhow. If you're more concerned about how a candidate presents themselves, or who they love, then how they do their job, and how dedicated and talented they are- check yourself. #loveislove #pridemonth #a11y #dei #inclusive #hiring (Photo credit: Nili Auerbach)

111

18 Comments

Anyone running a service business, bookmark this template. The undisputed high-converting service business homepage formula.

1

You might not have heard from me much lately – I've been deep in development on a BIG demo project to show off some skills, and its finally ready..ish. DECIBEL TRIBE! [decibeltribe.com](https://decibeltribe.com) What is Decibel Tribe? It's as a social media platform (twitter clone), but with a twist for music industry folks: - Musician Profiles: Tailored profiles where musicians can add the instruments they play, and professionals can showcase their music industry skills. - Connect and Collaborate: A search functionality lets you easily find musicians and professionals across different specialties. - Event & Calendar System: Create and manage public or private events with a custom-built calendar, making it easy to organize jam sessions, gigs, or music industry meetups. - Groups Feature: Join or create groups to build a community within your music niche. Built With Love for Code and Music Decibel Tribe is built on a fun tech stack: - React & TypeScript for a smooth, scalable front-end experience. - Vitest for detailed unit and integration testing. - Cypress to cover end-to-end testing (currently in progress). - Next.js and Vercel for seamless development and deployment. It's been a blast to build a platform that merges my interest in software engineering and testing, with the music community. Coming Soon: Open Source 🎉 While Decibel Tribe isn't open source yet, I'm working towards making that happen. So stay tuned if you're a web dev and want to contribute to get some good stats on your resume! Please feel free to check out the demo site at [decibeltribe.com](https://decibeltribe.com) 🤘 #React #TypeScript #Nextjs #Vercel #Vitest #Cypress #MusicIndustry #SocialNetwork #WebDevelopment #OpenSource #SoftwareEngineering

8

1 Comment