Dave Slusher

Some people think metadata is "industry stuff." Nah. Metadata is "getting paid stuff." It's "knowing what you own stuff." It's "responding to opportunities stuff." The industry didn't invent metadata. They just take it seriously. You should too.

4

With spec driven devlopment, and the LLM development frameworks, claude code, cursor, open claw, autoresearch, etc. I believe that in a year most programming will be close to declarative, as in I speak my vision and the Agents bring it to reality. The question will then be can you express your vision such that the Agents can execute it properly. In the end we all become managers for better or worse.

15

𝐈𝐦𝐩𝐞𝐫𝐬𝐨𝐧𝐚𝐭𝐞 𝐔𝐬𝐞𝐫𝐬 𝐢𝐧 𝐭𝐡𝐞 𝐀𝐮𝐭𝐡𝐨𝐫 𝐄𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭 Working in AEM and need to test permissions or troubleshoot issues from a specific user's perspective? AEM lets you 𝐢𝐦𝐩𝐞𝐫𝐬𝐨𝐧𝐚𝐭𝐞 𝐮𝐬𝐞𝐫𝐬 right in the 𝐀𝐮𝐭𝐡𝐨𝐫 environment, so you can step into their shoes without needing their login. Impersonation is super helpful when you want to: - Validate what a user can (or can’t) access - Test the user experience without touching real credentials - Debug content visibility or UI issues - Even work on behalf of another user, like publishing or editing as them Here’s how to do it: 1) Go to 𝐓𝐨𝐨𝐥𝐬 > 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 > 𝐔𝐬𝐞𝐫𝐬 2) Find the user you want to impersonate 3) Click their 𝐔𝐬𝐞𝐫 𝐈𝐃, then click "𝐈𝐦𝐩𝐞𝐫𝐬𝐨𝐧𝐚𝐭𝐞" 4) You’re now acting as that user — just make sure to 𝐬𝐭𝐨𝐩 𝐢𝐦𝐩𝐞𝐫𝐬𝐨𝐧𝐚𝐭𝐢𝐧𝐠 once you're done! 𝐖𝐡𝐞𝐭𝐡𝐞𝐫 𝐨𝐫 𝐧𝐨𝐭 𝐲𝐨𝐮 𝐡𝐚𝐯𝐞 𝐀𝐝𝐦𝐢𝐧 𝐚𝐜𝐜𝐞𝐬𝐬, 𝐲𝐨𝐮 𝐦𝐢𝐠𝐡𝐭 𝐬𝐭𝐢𝐥𝐥 𝐛𝐞 𝐚𝐛𝐥𝐞 𝐭𝐨 𝐮𝐬𝐞 𝐭𝐡𝐢𝐬 𝐟𝐞𝐚𝐭𝐮𝐫𝐞 — 𝐝𝐞𝐩𝐞𝐧𝐝𝐢𝐧𝐠 𝐨𝐧 𝐲𝐨𝐮𝐫 𝐬𝐞𝐭𝐮𝐩. More details and step-by-step screenshots here https://lnkd.in/gFZXJAMc #AEM #AEMaaCS #AEM65 #DigitalExperience #DevTips #BrainStation23

8

uncannyuse now has schema pages for Reality Composer Pro components—showing the exact USDA block RCP writes, field-by-field with types and sparse-authoring behavior, plus annotated fixture examples. 20 components covered so far. https://lnkd.in/dpsT2A-8

9

I often use tools like Coveralls to track test coverage, but their authentication systems can sometimes get in the way. To simplify things, I built a workflow with GitHub Actions that generates a coverage dashboard directly in GitHub Pages, no extra logins required. I’ve now set this up for a couple of my CPAN modules, and it’s working well. Here’s an example for CGI::Info, https://lnkd.in/ec6etnAQ

1

I made an Android app last night. In an hour. It included vibration effects and sound effects that required external audio files. I haven't written code in forever. I used ChatGPT. Not only did it write all of the code and necessary config. files, it also taught me how to package it for Git distribution. And how to open it in Android Studio. And it found public domain audio files for me. And recommended numerous product enhancements. And told me how to get it listed in Google Play. Is the code perfect? No, I'm certain a human dev could clean it up and improve the documentation. But the door is open and barriers are down. Opportunities are there for people that didn't exist before. And if you're a developer? You should really think about using the available tools to move faster and take out the grunt work or risk getting left behind.

54

56 Comments

The best feedback I’ve ever received on a doc was: “I didn’t need to ask for help.” That’s the power of clarity in technical communication. #technicaldocumentation #technicalwriting

1

I'm cooking something. Not sure it it will work. Really like the "Spine Walker" hallucinated name. Objective Create a Ruby script (e.g., bin/generate_feature_specs) that automatically generates "Feature Specification" Markdown files for a massive Rails/React monolith. These files will serve as a Semantic Index (Structural RAG) to allow LLMs to accurately navigate the codebase without loading the entire context. Core Philosophy We will use the "Spine Walker" strategy. Because the Rails backend is scattered (MVC pattern) but the React frontend is often grouped by feature (e.g., app/javascript/late_fee_policies), we will use the app/javascript directory structure as the "Spine" to identify features, and then use an LLM to "bridge" those features to their corresponding backend models and controllers. Additionally, we treat the top-level application code (views, controllers, lib, top-level JS) as a special feature called app that captures orchestration and features not organized into React apps.

4

2 Comments