Joe Witkowski

How to Defrag Your Dev Log Today we’re going to learn a different dev log summarization technique: defragmentation. The longer you continue your daily dev log practice, the more likely it is you’ll create complete knowledge bases for specific skills or tasks. These knowledge bases represent tremendous value to future you. When the time comes, you’ll be able to exploit them to your advantage. Unfortunately, when the time comes, you can’t find them. Because you’ve scattered them across dozens of entries spanning months of time. Not only that, but: · You’re not quite sure what to search for. · You don’t know if you saved the information or a link to it. · You don’t even know if you wrote down the one thing you need. · Don’t worry. I’m going to show you how to fix this problem for good. Here’s how, step by step: Step 1: Leverage tags and links throughout your notes. Apply basic metadata in the moment, enabling you to integrate scattered knowledge in the future. Use an editor that supports linking information via tags and wiki-style links. Both styles sort information into buckets, some broader (tags) and some narrower (links). Don’t overthink the labels. Just apply them to your daily entries when it feels right. Step 2: When you “get that feeling,” create a topic note. The beauty of wiki-style links is the target doesn’t have to exist. This means when you refer to people or things, you can with zero friction create a link their page. A page that doesn’t exist. As you notice it popping up everywhere, you “get that feeling” it’s time to integrate. Follow the link, letting your editor create the page for you. Start working through the backlinks, summarizing the information. Step 3: Periodically run a defragmentation. Integrate your tags regularly for best dev log performance. When you’re doing a lot of work within a broad topic area (e.g. a public cloud provider), you may not be sure what buckets you need. So apply a memorable tag (#cloud-provider) for later use. Periodically, walk through your tags. The ones with the most backlinks are candidates for topic notes of their own. Don’t worry about coming up with the perfect tags and links. Just get started. And as part of your weekly reviews, take the opportunity to try out steps two and three. The structure that emerges is the one you need!

1

It is so important to dedicate time for personal development throughout your working week. Today continues with Copilot training @MicrosoftLearn journey!

7

2 Comments

In this great conversation with Víctor Garcia, I explain how teaching others and creating content will skyrocket your software engineering career. I also tell you my story of becoming a published book author. https://lnkd.in/e9vdUc5V

24

1 Comment

My gut tells me that people would prioritize critical flaws before low/medium severity, but new research proves that idea is wrong! Check out this counterintuitive research that will help you manage risk more effectively. #riskmanagement #cybersecurity

1

Here's the new article that I wrote for www.xml.com, "String analysis with XSLT's analyze-string" : https://lnkd.in/gDp9Qipx Thanks to Lauren Wood for reviewing this article and publishing on www.xml.com.

5

4 Comments

🔌 **Unlocking Operational Efficiency: ADMS-EMS Integration Patterns** 🔌 As a Solution Architect specializing in utilities Grid Modernization, I've witnessed the transformative power of integrating Advanced Distribution Management Systems (ADMS) and Energy Management Systems (EMS). This integration isn't just about connecting two systems; it's about streamlining operations, enhancing grid resilience, and enabling a smarter, more efficient grid. ADMS-EMS integration enables utilities to achieve real-time visibility and control over their entire grid, from transmission to distribution. By integrating these systems, utilities can optimize grid operations, improve outage management, and enhance grid stability. There are several integration patterns for ADMS-EMS integration, including data synchronization, event-driven integration, and unified monitoring and control interfaces. Each pattern offers unique benefits and challenges, depending on the utility's specific needs and infrastructure. In my role, I've helped utilities design and implement ADMS-EMS integration solutions that align with their business goals and operational requirements. It's inspiring to see how these integrations can unlock new levels of operational efficiency and grid performance. Let's continue to explore and innovate with ADMS-EMS integration to build a smarter, more resilient grid for the future. #ADMS #EMS #Integration #GridModernization #Utilities

21

2 Comments

SSA's System has Millions of Lines of Code written in COBOL But Nobody is learning COBOL, Also Replacing the entire Codebases will cost Billions of Dollars! In 2018, SSA estimated that it'll cost $691 Million Dollars for replacing its COBOL systems. A comprehensive replacement of the SSA’s COBOL systems with a new programming language like Python could realistically cost between $1 billion to $5 billion. IRS’s ongoing codebase modernization efforts are expected to cost around $2.3 billion dollars. California's Employment Development Department once estimated that replacing its COBOL systems would cost around $500 million. So, replacing the Legacy Codebases isn't the solution. Here's the Solution: Tublian OS is an Ai Agent that will help Companies SAVE Millions of Dollars by Handling, Maintaining and Debugging LEGACY CODE bases effortlessly. Checkout more about Tublian on 🔗 www.tublian.com Follow Haris Ahmad Kaboo 👋 #cobol #legacycode #ibm #nasa #coding #python

56

2 Comments

I've become increasingly frustrated with the lack of helpful discourse about AI on LinkedIn. Here are some hot takes from someone (me) who's been working with GenAI on a daily basis for about a year. 1. The term "AI" is meaningless. The image I've enclosed is ONE way to think about AI. As compute, algorithms, and data storage/retrieval improves, the Reuleaux triangle in the middle gets bigger and more capabilities are labeled "AI." It won't be too long before all computing is "AI." 2. Consciousness, self-awareness, volition, and intelligence are separate phenomena. We don't really understand any of them, so anybody making predictions about the rise of the machines is just guessing. They haven't read enough sci-fi. 3. Neither the detractors nor the hypers are right about GenAI. But the hypers are closer. It's a transformational, enormously disruptive technology. But are the hypers DOING ANYTHING interesting with GenAI, or are they just ... hyping it? 4. Very few seem to understand how to maximize the capabilities of GenAI or how to mitigate its risks. Commercial/SaaS products I've seen are uninspiring. 5. The power in Generative AI is only unleashed by the plumbing. Chatbots are a toy unless you know how to prompt them, how to implement RAG, how to build agents, etc... It's a lot of work! Do you agree? Disagree? What do you think the zeitgeist is getting wrong about AI?

27

7 Comments

No matter what language you’re programming in, errors happen. One great thing about #Rust is that you can diagnose and act on them quickly – if you know which tools and mechanisms to use. Learn more on our Tech Blog. https://bit.ly/4grjdGc

2

This year's Biztalk replacement project is finally complete, we've replaced our legacy interfaces with shiny new ones. This made me think of the resiliency of the architecture and design of the original solution, and the 𝘱𝘦𝘰𝘱𝘭𝘦 who did it. The legacy services were designed in 2011, upgraded in 2013, and have only been updated 5-6 since then in the few projects that funded required changes in them. But the have performed flawlessly handling thousands of transactions a day with a 99.999% uptime and reliability score. These services have integrated several enterprise systems, platforms and workflow that have the same design patterns and legacy. They are 6-20 years old and have had minimal maintenance and support.  "You must have great infrastructure to support such a collection of legacy systems". No, we have great systems running on the fewest resources. There's no load-balancing for these 70 applications hosted on 3 unique servers. No problem. 𝟵𝟵.𝟵𝟵𝟵% 𝘂𝗽𝘁𝗶𝗺𝗲. No system events. No memory faults. No Code exceptions. No Data faults. No integration failures. All rock-solid applications still running the same base code that was designed long ago using the popular pattern and tools of the time. 𝗜'𝘃𝗲 𝘄𝗼𝗿𝗸𝗲𝗱 𝘄𝗶𝘁𝗵 𝘀𝗼𝗺𝗲 𝗲𝘅𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝗮𝗹 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗵𝗼 𝗵𝗮𝘃𝗲 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗱 𝘀𝗼𝗺𝗲 𝗳𝗮𝗻𝘁𝗮𝘀𝘁𝗶𝗰 𝘁𝗵𝗶𝗻𝗴𝘀. 𝗜 𝗵𝗼𝗽𝗲 𝘁𝗵𝗮𝘁 𝗶𝗳 𝘆𝗼𝘂 𝗿𝗲𝗮𝗱 𝘁𝗵𝗶𝘀, 𝘆𝗼𝘂 𝗮𝗿𝗲 𝗼𝗻𝗲 𝗼𝗳 𝘁𝗵𝗼𝘀𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝗮𝗻𝗱 𝗸𝗻𝗼𝘄 𝘁𝗵𝗮𝘁 𝗜 𝗮𝗽𝗽𝗿𝗲𝗰𝗶𝗮𝘁𝗲 𝘁𝗵𝗲 𝗮𝗺𝗮𝘇𝗶𝗻𝗴 𝘄𝗼𝗿𝗸 𝘆𝗼𝘂 𝗱𝗶𝗱.

36

23 Comments