Anna Terets

Did you know that the average DevOps professional stays with a company for only 1.9 years? I posted some stats about the Test Automation candidate market in Finland a while ago, and quite a few people found that interesting. I thought I'd do a similar post about the DevOps market. 🤗 According to LinkedIn Talent Insights, the hiring demand for DevOps roles is... 💥 "Very High" in Helsinki, Tampere and Turku 🔥 "High" in Oulu ⚡️ "Moderate" in Jyväskylä ⭐️ "Low" in smaller cities such as Joensuu and Vaasa The number of people with DevOps skills has increased 29% over the past year, so this is definitely a growing market! Did you find any of these stats surprising? (These insights are about people located in Finland who mention "DevOps" on their LinkedIn profile) #recruiting #devops #finland #talentacquisition #linkedin

24

2 kommenttia

Join us at the TestBustersDay 2024. On day 1 - the Platform Day brought to you by webmate - Björn Scherer will talk about: "Test Engineering as DevOps Platform" RegisterFREE: https://lnkd.in/dr3Thmwg To shorten time-to-market, many IT organizations are extending their agile practices with DevOps methods to deliver software faster and more reliably. This shift places significantly higher demands on quality assurance, as making it continuous also requires a high degree of automation and stability. While DevOps teams maintain their autonomy in implementing and maintaining products and features, efficiency can suffer when multiple teams independently address similar challenges (CI/CD, infrastructure, monitoring, etc.). The establishment of platform teams has proven to be an effective way to promote standardization and reuse while reducing complexity. Why not take the same approach for quality assurance? What opportunities arise from integrating test engineering into a platform team, and where are the limits? What challenges does such a team face? This presentation offers a case study from an organization bold enough to take this step.

14

Society in general is starting to take bad software seriously. Is your company? Hint: Let's play "bad software practices bingo" and find out! [  ] Like a microwave oven, you let the clock decide if the work's done [  ] The general sentiment is that testing is a vanity metric... [  ] ...So someone other than the developer writes tests... [  ] ...Maybe [  ] You do PI planning and other fika activities at a rate and cost that would bankrupt a small nation [  ] You have several layers of IT roles with inspecific responsibilities [  ] You have a lot of people talking about work, not doing so much of it [  ] Your management does not understand IT, so you have to do "special" (yes, read it in THAT voice) slides for them [  ] You do "quick and dirty" more than once in a lifetime; actually, you do it on a very regular basis [  ] Once per year all teams get to cut down infrastructure spend with 5% because your procurement thinks they can wrench money from AWS' cold, inanimate hands [  ] You estimate stuff to someone who estimates stuff who sometimes nods in blank-eyed agreement [  ] You have no way of knowing if things break before customers/users complain [  ] No one can -actually- say what the hell their software does if [X] leaves [ ] When someone is fired, you get to do/listen to "KT" sessions because -nothing- is documented according to any meaningful practices [  ] No developer has ever spent more than a few hours on quality-enhancing activities like security, observability, or solving known technical debt (go ahead, ask them) [ ] "Design" and "architecture" are things that the team read about in university, and at work these are represented by men in Birkenstocks with oddly specific opinions which can all be safely discarded (like in Rock-Paper-Scissors, PM always wins against Architect) There are so many varieties! What score did you get?

28

2 kommenttia

Pair programming is a wonderful tool for creating a cohesive, strong development team. It is more than just a coding approach. Developers can decrease technical debt, build software of higher quality, and foster a culture of ongoing learning and development by cooperating. Strategies I have found useful when starting with peer programming: - Make one developer "Driver" and the other "Navigator", switching responsibilities periodically.  - Prior to beginning, establish clear goals. - Promote polite, honest dialogue wherein developers can exchange thoughts and criticism. Have you tried pair programming in your team? Share your experiences and tips in the comments! #PairProgramming #Agile #SoftwareDevelopment #Collaboration #CodeQuality #ContinuousLearning

79

4 kommenttia

DevOps is a way of working. Every company does it differently.

9

If you’re working with #Scala, you already know its power (unlimited, as Palpatine would say!). But how do you make sure your code is secure? If you want key strategies to enhance Scala security - I've got just the thing. No dark side powers required. 😉 ⬇ My latest article explore how to safeguard your Scala applications, with a focus on #Akka - a powerful toolkit for building concurrent, distributed, and fault-tolerant systems. Key takeaways: ➡ #TypeSafety: Scala’s static type system helps catch common errors during compilation, reducing runtime vulnerabilities. ➡ Immutable Data Structures: Enhance security by preventing accidental data modifications and reducing race conditions. ➡ #FunctionalProgramming: Scala promotes predictability and secure application behavior through pure functions and referential transparency. 🔐 Securing with Akka: ➡ #ActorModel: Isolates components, limiting shared-memory vulnerabilities. ➡ Supervision Hierarchy: Helps gracefully recover from errors. ➡ Remoting & Clustering: Secure communication with TLS/SSL. ➡ Akka Persistence: Ensures data durability and integrity. Even more on how you can boost your #cybersecurity with Scala and Akka here: https://lnkd.in/dEDc4X9K #softwaredevelopment #immutabledata #securecoding #dataprotection #codesecurity

13

Teamwork is the key to producing great software. But how does one build a great team? An insightful article explaining the three pillars of a healthy, collaborative team by “Team Geek - A Software Developer’s Guide to Working Well with Others”(https://lnkd.in/d5CmNi4v) and highlighting the importance of creating relationships to get things done as: “Relationships always outlast projects.” Humility “You are not the center of the universe. You’re neither omniscient nor infallible. You’re open to self-improvement.” Respect “You genuinely care about others you work with. You treat them as human beings, and appreciate their abilities and accomplishments.” Trust “You believe others are competent and will do the right thing, and you’re OK with letting them drive when appropriate.”

18

𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐜𝐢𝐞𝐬 𝐯𝐬 𝐏𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 I've worked in 𝐬𝐭𝐚𝐫𝐭-𝐮𝐩𝐬, IT 𝐜𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐜𝐢𝐞𝐬, from niche to mid-sized to Large, the IT dept of non-software companies, and software 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 companies. Let me share some 𝐩𝐫𝐨𝐬 and 𝐜𝐨𝐧𝐬 about working in the different ones. 𝐂𝐎𝐍𝐒𝐔𝐋𝐓𝐀𝐍𝐂𝐈𝐄𝐒 I'll be honest: consultancies have a strong hold over the tech sector in Norway, as there simply isn't many or any big software product companies to speak of. Only small/start-ups. So, a lot of the talent pool is working in consultancies. I eventually left my home country to work in a Software 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 company 🏡 💼 🛫 🌍 😁 𝐏𝐫𝐨𝐬: ➕ Work with experts & technology specialists ➕ Access to great training programs, technical and non-technical ➕ Exposure to many different industries! - Public and private sector. Retail, airports, energy, agriculture, government - etc! 𝐂𝐨𝐧𝐬: ➖ Tech > Problem-solving: You're sold as a <insert tech> dev. ➖ Process & Red tape - Pre-defined deliveries/contracts means things can be slow or difficult to change ➖ Little to no ownership of the product ➖ Certifications > Impact - Consultancies wants you to be easy to sell. Certs works as a proof of your skills. 𝐏𝐑𝐎𝐃𝐔𝐂𝐓 𝐒𝐭𝐚𝐫𝐭-𝐮𝐩𝐬 I had an internship in a start-up as a CS student. This experience was invaluable. I later worked as a software engineer in a start-up, and worked on some very cool projects. Had a lot of fun, learned a lot. 𝐏𝐫𝐨𝐬: ➕ Fast paced, not boring ➕ You can and must wear many hats ➕ Could be career making 𝐂𝐨𝐧𝐬: ➖ Little to no structure or process ➖ Potentially nowhere to grow ➖ A big risk that might not pay off. If you're in a start-up, make sure to get something out of it even if the start-up doesn't succeed. 𝐍𝐨𝐧-𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 I worked in television(!) As a Business Intelligence dev & analyst. Basically a data engineers & Data scientist. ➕ Can have big impact on the product/business ➕ Exposure to potentially interesting domain ➕ Help non-technical stakeholders ➖ Not solving for the core business, not prioritized ➖ Slow to adopt new tech. ➖ Lonely - No dev community. Things like Code quality, CI/CD, DevOps, DevEx... is up to you/your dept, or nonexistent. 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐩𝐫𝐨𝐝𝐮𝐜𝐭 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬 I might be biased here as I currently work in a Software product company, something I wanted for a long time. ➕ Have a big impact on the core business and or for customers ➕ Win by solving interesting & challenging industry problems in smart ways over use <insert tech> by all means. ➕ Ownership of product over time ➕ Career growth opportunities ➖ Working in a high performance environment can be stressful ➖ Bias for action or bust ➖ Learn how to deal with Ambiguity or have a bad time Please let me know what you think of this!!!

31

9 kommenttia

Did you know that 70% of software projects fail due to poor requirements management? Don't let miscommunication lead to project failure and financial losses. Take control of your software development process with Ellogy.ai. As a software developer, IT project manager, or CIO in the software development industry, you understand the importance of IT requirements gathering. It sets the foundation for a successful software project, ensuring that all stakeholders are on the same page and that the end product meets the users' needs. At Ellogy.ai, we specialize in automating software documentation and requirements management, streamlining the process, and saving you time and effort. Our AI-powered platform conducts user interviews and generates comprehensive software documentation, reducing manual effort and errors. With Ellogy.ai, you can access intuitive, collaborative, and secure software documentation. Our platform offers striking designs that go beyond basic textual specifications. We support UML-based software design and UI in HTML/CSS. Plus, we follow software design best practices, ensuring quality at every step. Ready to revolutionize how you gather, analyze, and communicate project requirements? Visit our website at ellogy.ai to learn more. Our transparent pricing plans make it accessible for startups, enterprises, and visionaries like you.

24

Let's talk about Trust. Recently I just finished my skipper courses, and you know what - it's so much a software development. You're - a cross-functional team of 2-8 people - with a delivery idea of moving the vessel from point A to point B. But yet, that's an extreme sport - and as with every extreme team activity - Trust is key to success. A team member has the Trust if - believe other members are doing their best in their work - believe other member's estimations/promises are true - believe other members will raise a flag once trouble appears > We can fail, but fail quickly and learn. But how do you build that in the team? The first thing you do - you become such a person. You always do your best. You try to keep your word and promises. You fail and talk about that openly. You are - the Trust deliveryman. > As a leader, you need to trust your team first to be trusted. So what do you think? - Do you have a Trust-specific task in your backlog? - How do you measure the Trust in your team? - Did you have an experience where a lack of Trust became a blocker? inspired by https://lnkd.in/dGQCPi9v #LifeIsASoftwareDevelopment

19

2 kommenttia

“We added another temperature sensor for this component test, can you put it in the GUI?” is a common exchange between test/operations engineers and control software engineers. Test engineers waste time waiting on a limited pool of developers, and software engineers fill their day with trivial changes instead of making large improvements. Synnax’s low-code tools were built with both of these groups in mind. Test engineers accelerate setup time by making changes themselves, and software engineers get those precious, uninterrupted hours to make quality progress. Here’s a time-lapse of me setting up a fully controllable, real-time mission control GUI in five minutes without any code:

78

3 kommenttia

+++ FOOLED BY FAULTY SOFTWARE +++ The impact of software testing on the infamous Post Office IT scandal in Great Britain! Dear Testbusters, Don't miss out on our upcoming TestBustersNight brought to you by Alpenhost, with James Christie on the infamous Post Office IT scandal in Great Britain! RegisterFREE: https://lnkd.in/eDyxgq9U Join us as James delves into the details of the scandal, discussing the flawed computer evidence from the Horizon accounting system, poorly managed development and testing, and the important lessons for testers worldwide. The Post Office IT scandal has been one of the biggest news stories in the UK this year. Hundreds of people were convicted and jailed on the basis of flawed computer evidence from the Horizon accounting system. James will explain how the original development and testing of Horizon were badly managed, and how a judge decided that the system was unreliable. The scandal has important lessons for testers, not only in the UK."

13

My first task as a software engineer was "keeping the lights on" in production. My job was to look out for unusual exceptions and root cause them. I would read exception emails, dig through logs, and communicate with senior engineers. In short, I was the support/on-call engineer. I wanted to make a good impression, and I pushed myself too hard. For the first three days, I hardly slept. On the fourth day, I lay in bed and didn't wake up for 12 hours. When I did, prod was down. 3 missed calls. 12 unread Slack messages. I quickly called my manager to apologize profusely. Me: Hi, I am sorry I wasn't available. __ messaged me. I am checking what the issue is right now. Manager: That's all right Gaurav. Are you okay? We couldn't reach you. Me: I am fine. I overslept. Give me 10 minutes, I am opening the logs. Manager: That's okay. __ has already resolved it. We figured your weren't feeling well. Me: Oh, that's great. Thanks. To be frank, I was a little disappointed. If a bug could be detected and resolved while I slept, wasn't I replaceable? Then I thought of the situation practically. Of course I was replaceable. A company couldn't afford to stop functioning because one engineer fell asleep. The show would go on, with or without me. But what would happen if two engineers were unavailable? What would happen if our emails stopped functioning? This is why Google has something called a "bus factor". The basic idea is that important projects shouldn't stop, even if a bus full of team members die. Morbid, yeah. But it gets the point across. Software systems have a similar concept called 'Single Point of Failure'. If your database collapses, a copy takes its place. But what happens when a monitoring system collapses? Who will report errors then? Both Facebook and Google realized this difficulty with building highly available systems. And they came up with similar solutions: In-Memory Time-Series Databases. Tomorrow at 9 AM IST, I will go through the first time-series database in our live lecture series: Facebook GorillaDB. Specifically, we will discuss its motivations and challenges. Get ready for some awesome deep dives. Cheers! #SystemDesign #TimeSeriesDatabase #LiveClass

436

16 kommenttia

Simple improvements are often the most effective! Our aim? Providing a top-notch Developer Experience. You can now expand the Qovery cloud shell ;) #qovery #product #shell

12

🙋Enhancing Performance with Alpine.js x-defer in Hyvä Theme The Hyvä theme, known for its focus on performance, can be further optimized with Alpine.js, particularly using the 𝙭-𝙙𝙚𝙛𝙚𝙧 directive. Here’s how it can benefit your Magento store: 💡 𝗪𝗵𝗮𝘁 𝗶𝘀 𝘅-𝗱𝗲𝗳𝗲𝗿? 👉 Delays the execution of 𝗔𝗹𝗽𝗶𝗻𝗲.𝗷𝘀 logic until the page has fully loaded. 🔧 𝗞𝗲𝘆 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝗶𝗻 𝗛𝘆𝘃𝗮 𝗧𝗵𝗲𝗺𝗲 ⚡ Faster Load Times: Reduces initial page load by deferring non-essential JavaScript execution. ⏳ Improved User Experience: Ensures a quicker time to first meaningful paint (FMP) while maintaining functionality. 🧑‍💻 Optimized Rendering: Defers JavaScript logic without affecting core page interactions, enhancing overall performance. 𝙀𝙭𝙖𝙢𝙥𝙡𝙚 𝙤𝙛 𝙭–𝙙𝙚𝙛𝙚𝙧 𝙬𝙞𝙩𝙝 𝙖 𝙋𝙧𝙤𝙙𝙪𝙘𝙩 𝙎𝙡𝙞𝙙𝙚𝙧 <𝘥𝘪𝘷 𝘹-𝘥𝘢𝘵𝘢="𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘚𝘭𝘪𝘥𝘦𝘳()" 𝘹-𝘥𝘦𝘧𝘦𝘳> <𝘥𝘪𝘷 𝘤𝘭𝘢𝘴𝘴="𝘴𝘭𝘪𝘥𝘦𝘳"> <𝘵𝘦𝘮𝘱𝘭𝘢𝘵𝘦 𝘹-𝘧𝘰𝘳="𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘪𝘯 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴" :𝘬𝘦𝘺="𝘱𝘳𝘰𝘥𝘶𝘤𝘵.𝘪𝘥"> <𝘥𝘪𝘷 𝘤𝘭𝘢𝘴𝘴="𝘱𝘳𝘰𝘥𝘶𝘤𝘵"> <𝘪𝘮𝘨 :𝘴𝘳𝘤="𝘱𝘳𝘰𝘥𝘶𝘤𝘵.𝘪𝘮𝘢𝘨𝘦" :𝘢𝘭𝘵="𝘱𝘳𝘰𝘥𝘶𝘤𝘵.𝘯𝘢𝘮𝘦"> <𝘩3 𝘹-𝘵𝘦𝘹𝘵="𝘱𝘳𝘰𝘥𝘶𝘤𝘵.𝘯𝘢𝘮𝘦"></𝘩3> <𝘱 𝘹-𝘵𝘦𝘹𝘵="𝘱𝘳𝘰𝘥𝘶𝘤𝘵.𝘱𝘳𝘪𝘤𝘦"></𝘱> </𝘥𝘪𝘷> </𝘵𝘦𝘮𝘱𝘭𝘢𝘵𝘦> </𝘥𝘪𝘷> <𝘴𝘤𝘳𝘪𝘱𝘵> 𝘧𝘶𝘯𝘤𝘵𝘪𝘰𝘯 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘚𝘭𝘪𝘥𝘦𝘳() { 𝘳𝘦𝘵𝘶𝘳𝘯 { 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴: [], 𝘪𝘯𝘪𝘵() { // 𝘍𝘦𝘵𝘤𝘩 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘥𝘢𝘵𝘢 𝘰𝘳 𝘪𝘯𝘪𝘵𝘪𝘢𝘭𝘪𝘻𝘦 𝘪𝘵 𝘩𝘦𝘳𝘦 𝘵𝘩𝘪𝘴.𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴 = [ { 𝘪𝘥: 1, 𝘯𝘢𝘮𝘦: '𝘗𝘳𝘰𝘥𝘶𝘤𝘵 1', 𝘱𝘳𝘪𝘤𝘦: '$100', 𝘪𝘮𝘢𝘨𝘦: '𝘪𝘮𝘢𝘨𝘦1.𝘫𝘱𝘨' }, { 𝘪𝘥: 2, 𝘯𝘢𝘮𝘦: '𝘗𝘳𝘰𝘥𝘶𝘤𝘵 2', 𝘱𝘳𝘪𝘤𝘦: '$150', 𝘪𝘮𝘢𝘨𝘦: '𝘪𝘮𝘢𝘨𝘦2.𝘫𝘱𝘨' }, { 𝘪𝘥: 3, 𝘯𝘢𝘮𝘦: '𝘗𝘳𝘰𝘥𝘶𝘤𝘵 3', 𝘱𝘳𝘪𝘤𝘦: '$200', 𝘪𝘮𝘢𝘨𝘦: '𝘪𝘮𝘢𝘨𝘦3.𝘫𝘱𝘨' }, ]; }, }; } </𝘴𝘤𝘳𝘪𝘱𝘵> </𝘥𝘪𝘷> 🤔 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀 • The product slider logic is deferred using x-defer, ensuring the slider doesn’t load until the page is fully rendered. • Product data is dynamically fetched or initialized inside the Alpine.js component. • Non-critical functionality like sliders will not block the initial rendering of the homepage, improving overall performance. By leveraging x-defer for dynamic features like product sliders, you can maintain a high-performance Magento store while delivering rich functionality to users. 👉 Learn more about x-defer in Hyvä Theme: https://lnkd.in/dzuuPe9v #Hyvä #Magento2 #AlpineJS #WebPerformance #eCommerce #HyväTheme #PerformanceOptimization #MagentoDevelopment #WebPerformance #TechTips #Magento #Hyva #SpeedMatters #xDefer #webdevelopment #magento #performance #hyva #hyvatheme #AdobeCommerce #NavigateCommerce

24

In February, I jumped into the Team Lead role at Urent and here, being a Team Lead means handling *everything.* My zone of responsibility? Architecture for our backend, leading the team, supporting everyone’s technical and career growth, performance, keeping up with product, deadlines… Basically, if it’s within my team’s scope, it’s on me. Sometimes, I even end up brainstorming product ideas! When I started, my team was around 8-9 people. Since then, a couple of folks moved on, even more joined, and now we’re at 12. But finally, next week, we’re splitting into two teams, so I’ll be down to six people and about 70% of my current responsibilities. Yay for manageable chaos! Our scope is massive – so much so that, during interviews, trying to explain everything we do usually ends with the other person either falling asleep or getting totally lost. But, hey, if nothing else, it keeps life exciting. One thing I’ve definitely learned: people management and team growth are by far the hardest parts. The rest? Doable, with enough coffee. And this job has given me a new life lesson – accepting that not everything is within my control. Sometimes things go south, but the trick is to stay calm and keep problem-solving. Speaking of people management… I'm seriously considering a degree in psychology at this point. My psychologist has been a lifesaver, teaching me how to stay emotionally afloat and navigate all the different personalities in my team. Honestly, I’m convinced every manager needs a psychologist 😅 – maybe everyone does, but that’s another debate. And who knows? Maybe I’ll start sharing some of our funny work fails and the creative ways we got out of them. There have been plenty!

14

1 kommentti

I heard a story yesterday from a new friend about an unsuccessful software development project that lasted for 1.5 years. It is over 1.2M USD in total budget spent to date and still needs to be finished. How do I know it's not successful? The phrase that he said: "They will probably deliver it this Autumn, but it will be a very raw product that no one needs" So, what went wrong? First of all, the contractor's choice. They selected a large software development agency with offices in 10 countries, and that seemed trustworthy. What you can expect in this case? - You will get your product done with a good quality - You will pay 30-50% more than for small consultancies - You will have a chance to meet someone in person somewhere in your country - Your product will be finished (but you obviously need to pay for every hour worked). What's the downside except the price? One main thing: Your product will be your responsibility only. Was your idea bad? Well, you paid 1.5M to validate it; no one really cares if something built will never be used. In 2V Modules, we have a different approach, which I'm a big fan of. If we start working on something, we dive deep to understand what this product is for, what pains we are addressing, who the ICP is, and whether it was validated or not. Even if it's an "internal" product, there are still multiple ways of building it. It's not only about the business analysis stage, it's about finding the right solutions. So I think small teams are often a better fit because they actually CARE what they are building, not only HOW it is built.

11

2 kommenttia

About 6 months ago, my role changed. As a result, coding is no longer a part of my day job. This has been challenging for me because I have come to identify myself as a coder. Unfortunately, this just hasn't been true for the past several months.   I want to get back into the habit of coding, and this is my challenge to do it. For the next few weeks, I am going to post a few of the code repositories I worked on in my last role. My hope is that this will create a habit of talking about and interacting with code, which will hopefully inspire me to write new code.   This first project I'm sharing is the last project I worked on in my previous role. It is a script that uses the Meraki APIs to pull the allowed clients lists from Meraki networks and then generates an Excel spreadsheet report from the results with columns for the MAC address of the client, IP address of the client, the date and time the client last connected, whether the client is currently online or offline, and the name of the network the client is connected to. I wrote this script because a Meraki customer requested a way to quickly generate reports that showed the last time a client from the network allow list connected to the network so that they could remove clients from the list with extended periods of inactivity. While creating this script, I learned that Meraki only saves the data of clients who have connected to the network in the last month. This makes it difficult to keep track of clients who have not connected to the network in an extended amount of time. I also learned that some of the libraries I used in this script needed to be updated to newer versions in order to work with Python 3.12 😅. If I were to add new features to this project, I would look for a way to keep track of clients for longer than the 31 day limit that currently exists. To do this, I think I would need to create a database that stores the activity of the clients periodically so that I am not completely reliant on the Meraki dashboard APIs and their limitations. You can find the source code of the project on my GitHub here (https://lnkd.in/eU7E9Nen). Feel free to download it and test it yourself if you're a Meraki user. Let me know what you think and what you would like from the script!

50

1 kommentti